Replies: 2 comments 1 reply
-
|
We agree and are re-opening #13897 to investigate if this still solves a real world problem |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks @seanbudd; not sure why my search didn't turn up this issue. I'm happy to close this in favour of #13897. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
It was previously closed, which might have been the problem |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
NVDA's browse mode currently ignores any controls with a width and height of 0. Unfortunately, I'm noticing a trend of using this type of control to add an accessible interactive element without the need to "fake" it using ARIA.
Another common method for making invisible screen-reader-only controls is to use CSS to position them off-screen. In recent Firefox builds, this also sometimes causes them to render with a width and height of 0, creating the same problem.
I'm not clear on exactly when this does or does not happen in Firefox, but you can see this in action in a few places, such as this personality test where the answer radio buttons are positioned off-screen. They are visible in browse mode when using Chrome or Edge, but not when using Firefox.
I searched through past issues and very quickly found that this has been a recurring problem:
While I recognize that incorrect use of HTML is at the root of the issue, NVDA's behaviour of ignoring these controls is unique to NVDA, not well-known, and the cause for a lot of confusion. Web developers will test with other screen readers and conclude their accessibility hack is working, and then NVDA users will come along and be unable to find the control at all.
Questions:
Beta Was this translation helpful? Give feedback.
All reactions