* Use a screen reader to interact with the autosuggest. The expected behavior is that once you start typing, you receive instructions saying that the down arrow will give autocomplete options. When you select an option with the arrow keys, it should announce the suggestion and its field class. Enter will accept a suggestion. Note that there is a bug with Safari + VoiceOver that is affecting this; hopefully other browser+screen reader combos work.
* Use a mouse and keyboard together to interact with the autosuggest.
* Run the test suite: cd $EVERGREEN_REPO/Open-ILS/web/opac/deps && npm i && npm run test
* Run the linter: cd $EVERGREEN_REPO/Open-ILS/web/opac/deps && npm i && npm run lint
Here is a branch with a new autosuggest: user/sandbergja /lp1187993- accessible- autocomplete
Here is the link: https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ sandbergja/ lp1187993- accessible- autocomplete
Here are a few ideas for doing qa on this:
* Use a screen reader to interact with the autosuggest. The expected behavior is that once you start typing, you receive instructions saying that the down arrow will give autocomplete options. When you select an option with the arrow keys, it should announce the suggestion and its field class. Enter will accept a suggestion. Note that there is a bug with Safari + VoiceOver that is affecting this; hopefully other browser+screen reader combos work.
* Use a mouse and keyboard together to interact with the autosuggest.
* Run the test suite: cd $EVERGREEN_ REPO/Open- ILS/web/ opac/deps && npm i && npm run test
* Run the linter: cd $EVERGREEN_ REPO/Open- ILS/web/ opac/deps && npm i && npm run lint
Looking forward to hearing what you think!