-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
[WEB]: Accessibility focus border doesn't follow when navigating through interactive elements with tab key #52106
Comments
Could you please provide a small code snippet that reproduces this issue? /cc @nturgut |
Which flutter channel are you running the app? Can you also provide a flutter doctor output? |
The same issue could also be reproduces on Gallery App the local project a11y_web_demo.zip flutter doctor output:
|
Thanks for filing the issue. I was able to create it. I'll have a look soon. |
It looks like the problem is we don't inform the browser when Flutter's focus node has changed. We need to figure out a way to notify the browser and screen reader that focus has changed. |
@838 I have a question to assess the priority of the issue. When using screen readers, we navigate using the screen reader shortcuts. Why is it necessary for tab key to be used when screen reader is on? Is it common usage for tab key to be used instead of "VoiceOver Control key+left right arrows keys"? |
The main reason to navigate by the tab key is to reduce the navigation steps by only navigating through the interactive elements like links and buttons instead of navigating through every element on the page. As an example, let's say we have a page with a list of books and each book with data(title, author, last played, etc) and a play button. Usually, the tab key is used to only jump through the play buttons. Although every ScreanReaders have their own nice features for faster navigation, still the tab key is very common and widely used especially for users who are new and are not aware of the power of the ScreenReaders. |
@838 thanks for the comments. @mariamhas Heads up, looks like this use case (using tab key when screen-reader is on) is not working. |
Looks like this issue is not a blocker for Narrotor, therefore I'm re-reducing the priority back to P4. |
Comment so far, thanks to @mdebbar suggestion, I tried utilizing the focus flag received with the semantics updates. As expected
I also tested it with a simple jsfiddle page. Looks like screenreader does not focus on an item such as |
I'm looking into this now. This affects NVDA (and reportedly JAWS too, although I don't have JAWS yet to check). |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Screen Reader does not follow the focus when navigating through interactive elements with tab-key.
The text was updated successfully, but these errors were encountered: