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
Accessibility issues with the Select component #39199
Comments
You may look for issues: |
For first part, we may do not provide |
Hey, thanks for answering. For point 1: I don't see why not add a For point 2: not sure i understand it right, but you mean adding Thanks again! |
|
@zombieJ Hi, it is also possible to fix the https://w3c.github.io/aria/#aria-setsize |
What problem does this feature solve?
There are a few problems with accessibility of the Select component.
[role="listbox"]
is added in the DOM after user interacts with the component. This triggers an error for accessibility assessment tools. I know you've indicated this in the documentation ("Select only create a11y auxiliary node when operating on."), but it would be best to have an optional prop to allow to render the list from the start[role="listbox"]
node there is only the current option and the adjacent ones. This is confusing to screen reader users because they don't get an idea of how long the list isWhat does the proposed API look like?
<Select forceRender ... />
to get the option list in the DOM without interacting with it.[role='listbox']
with all the options.The text was updated successfully, but these errors were encountered: