-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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#9196 #1319
Accessibility#9196 #1319
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to use useEffect to resolve the first No result search but it doesn't seem to work this way. The issue is fixed as your suggested change but there is still one caveat failing on the first No result search
the code looks better and indeed the first No result is still ongoing but for Chromevox only.
Did you have a chance to try this with a different screenreader other than chromevox?
It works ok using VoiceOver (cmd+F5 on MacOS). I didn't test this on JAWS, NVDA, etc but I take the implementation seems correct (and Chromevox is the one failing).
I have tested on NVDA and it shows the No results on the first try. It is also working ok using VoiceOver. Only chromevox is the one failing. |
@wraithgar FYI this PR got approved from @leobalter. Can you please merge it to prod? |
What/Why
No results
on providing invalid inputChanges
src/components/search.js
Before
After
No results
on providing invalid inputReferences