Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

Autocomplete is not Accessable (Tested on NVDA) #1473

Closed
mohammedzamakhan opened this issue Feb 11, 2015 · 8 comments
Closed

Autocomplete is not Accessable (Tested on NVDA) #1473

mohammedzamakhan opened this issue Feb 11, 2015 · 8 comments
Assignees
Labels
a11y This issue is related to accessibility type: bug
Milestone

Comments

@mohammedzamakhan
Copy link

I have tested Autocomplete with NVDA and it reads "blank" instead of the list items when you use arrows to scroll through the list

@robertmesserle robertmesserle added type: bug a11y This issue is related to accessibility labels Feb 11, 2015
@robertmesserle robertmesserle added this to the 0.8.0-rc1 milestone Feb 11, 2015
@robertmesserle robertmesserle self-assigned this Feb 11, 2015
marcysutton pushed a commit that referenced this issue Feb 13, 2015
WIP: needs to announce match count change when user re-filters list by deleting a character.

Closes #1473
marcysutton pushed a commit that referenced this issue Feb 13, 2015
WIP: needs to announce match count change when user re-filters list by deleting a character.

Closes #1473
@marcysutton
Copy link
Contributor

@zamamohammed we worked on a fix and just pushed it to master in a787e22. Can you try again?

@mohammedzamakhan
Copy link
Author

@marcysutton I am still hearing the 'blank'

Please listen to the recording:
https://www.dropbox.com/s/q9ezng1yocskjqg/Autocomplete.swf?dl=0

@marcysutton
Copy link
Contributor

I see what you're saying. It's really slow to announce "There is one match available" or the selection on arrow down in Firefox/NVDA despite having aria-live="assertive" on the text to be announced. Sometimes it doesn't read at all. It's great in VoiceOver, but not so good in JAWS and NVDA (which have higher usage). I'll see if I can make it better.

@robertmesserle we might need to change how we append text to <aria-status>....I think appends and detaches too fast for the virtual buffer in JAWS and NVDA.

@mohammedzamakhan
Copy link
Author

Most of the custom dropdown plugins in the Community (Chosen, Select2 etc) also has the same issue with it, the only implementation I liked is of Jquery UI (http://jqueryui.com/selectmenu/)

@marcysutton
Copy link
Contributor

Good to know. I think we can get it working by improving our implementation. The inspiration for our autocomplete was actually Twitter's Typeahead/draft tweet functionality.

@robertmesserle robertmesserle modified the milestones: 0.9.0, 0.8.0 Feb 19, 2015
@robertmesserle
Copy link
Contributor

@marcysutton I believe you were looking into this, assigned to you.

@mohammedzamakhan
Copy link
Author

@marcysutton when can I test this on material.angular.org ?

@marcysutton
Copy link
Contributor

@zamamohammed it is up on the docs site now! Just not out in a release yet.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
a11y This issue is related to accessibility type: bug
Projects
None yet
Development

No branches or pull requests

3 participants