-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix details element in firefox nvda #773
Fix details element in firefox nvda #773
Conversation
This fixes an issue with Firefox / NVDA not announcing the open state of the element. Fixes #754 See also alphagov/govuk-frontend@f5cfa5f
@mcheung-nhs or @chrimesdev - do either of you have any apple devices you could check in voiceover for me please? I am due to get an NHS testing iPad soon but probably not for another month yet... Thanks! |
Hi @andymantell - I can check on an iPad, iPhone and Mac. |
Thanks @mcheung-nhs, that would be very helpful if you could. |
@mcheung-nhs - do you have Dragon too? I can't get Dragon to open the details in Firefox. But I can get it to open it on the current version before my "fix". Can you see if the same happens for you? I fear I may have caused a regression for Firefox / Dragon... |
@andymantell - Yes I can check in Dragon as well |
I enquired about this on the X-Gov Slack as the same issue exists in govuk-frontend. @selfthinker very helpfully directed me to https://www.nuance.com/products/help/dragon15/dragon-for-pc/enx/dmpe_sub/Content/Web/about_firefox.htm which indicates that Dragon does not support Firefox any more. Therefore the fact that the details element does not work in Firefox/Dragon is not something that we need to fix at this point in time. |
I've tested on VoiceOver and the fix seems to have caused no issues. |
Thanks @mcheung-nhs |
Thanks @andymantell and @mcheung-nhs, looking to do a frontend library release week. Probably on Wednesday, so this will be included. |
Description
In order to fix #754, I have stopped polyfilling the details component in browsers that have native support since this is no longer necessary and as evidenced by #754 is actually making the situation worse for screen readers. Removing the polyfil causes Firefox to behave correctly now
Checklist
Assistive tech tested