-
-
Notifications
You must be signed in to change notification settings - Fork 617
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
Stop treating visibility as none #15821
Comments
I think this is a duplicate of #13897 You can see the discussion there, particularly in #13897 (comment) for more information |
I think the situation is different. In my case, I would like it to be visible to screen readers when visibility: hidden; is used, as it is visible to users but not to screen readers. I don't know if this would be the best option, but it was the only one I found. |
@DalisonCPU I cannot reproduce your issue. Take for example this:
NVDA reports the visually hidden text. |
If an element has visibility: hidden then all its contents are also visually hidden, only the blank space of the container is preserved. Screen readers must hide the content as well, this is the expected behavior. If developers want that content to be read by the screen reader then they should use other techniques like the CSS visually-hidden classes. |
Ah thanks @ramoncorominas for this hint, I was indeed missing the difference between visibility:hidden and visually-hidden. Good point. |
Is your feature request related to a problem? Please describe.
In some situations, developers choose to customize form fields, such as checkboxes. When doing this, we can use display: none; or visibility: hidden;. However, NVDA ignores the field in question. For this reason, I would like NVDA to only ignore fields with display: none; and not those with visibility: hidden;.
Describe the solution you'd like
Add to elements with visibility: hidden; in CSS properties are not ignored by NVDA.
Describe alternatives you've considered
There are solutions, but if you don't know or have advanced knowledge or don't know some CSS properties, you won't find them easily.
Additional context
I believe this implementation could help the community with the development of more accessible websites.
The text was updated successfully, but these errors were encountered: