-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
feat(typeahead): add accessibility attributes #582
Comments
We would really benefit from an accessible typeahead component, too. Is there anything you can say about the likelihood this will be implemented a) at all and b) if so, within what timespan? |
Hi, Can it be mentioned, till when the accessibility (ARIA) attributes will be added in the typeahead so it's items can be read on the screen reader |
@valorkin - Do we have any update on this as we need to add ARIA attributes for Accessibility with typeahead so that items can be read on the screen reader. |
Hello, is there any update on when this will be added? Thanks |
@valorkin It is still an issue :(. Thanks! |
I send a pull request with modifications #5547 |
* Add id to typeahead-container * Add attribute aria activeDescendant * Add aria-aria-owns and aria-aria-expanded * Add role="option" and role="listbox" * Add id to typeahead child * Add aria-autocomplete * Add role='listBox' * Add comment * Delete unused property * Use rendered to set attribute id * fix(typeahead): fix typeahead position, according to new position service changes Co-authored-by: Samuel Renier <[email protected]> Co-authored-by: Dmitriy Danilov <[email protected]> Co-authored-by: dmitry-zhemchugov <[email protected]>
Since bootstrap components will have a big user base, It is a good time to think of accessibility on all of the components. In particular, this typeahead widget is not currently accessible. When results are show, there is no indication how many results are there and how to navigate the results.
With screen reader turned on, please look at this example: http://www.bu.edu/webteam/clrux/accessibility/autocomplete/autocomplete.html.
Also, current implementation doesn't seem to allow overriding the "result" template. I have no way to adding some aria attributes to enable accessibility.
The text was updated successfully, but these errors were encountered: