Skip to content
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

[Low] Screen readers' Focus mode is still active when the preview link is activated #78

Open
daniel-montalvo opened this issue Apr 16, 2020 · 2 comments
Assignees
Labels
in - accessibility There is a problem with a feature or page that gets in the way of access by some or all users. type - browser/AT support A feature or page does not work in a certain browser or assistive technology.
Milestone

Comments

@daniel-montalvo
Copy link

When I press the preview link, focus mode is still active both in NVDA and JAWS. This prevents use of the arrow keys to review text. I need to disable focus mode manually. It would be ideal to explore if there are some inherited ARIA roles or properties that are causing this behavior in the functionality that sets focus to the container of each of the SCs previews.

@daniel-montalvo daniel-montalvo changed the title [Low] Focus mode is still active when the preview link is activated [Low] Screen readers' Focus mode is still active when the preview link is activated Apr 16, 2020
@hidde hidde added in - accessibility There is a problem with a feature or page that gets in the way of access by some or all users. type - new feature / functionality New feature or request labels Apr 20, 2020
@hidde
Copy link
Member

hidde commented May 25, 2020

@daniel-montalvo Thanks for the reporting and guidance, have spent some time researching this today.

Does this happen any time you go to a new page, or just when you press a preview link?

The preview is in a table, have you ever seen that trigger focus mode?


For reference: in a Level Access article they say the application and dialog roles in ARIA can cause this. Léonie Watson's post also names tab/tablist roles. I have verified we don't use those.

@hidde hidde added this to the Version 0.4 milestone May 27, 2020
@hidde hidde added type - bug Something is broken. type - browser/AT support A feature or page does not work in a certain browser or assistive technology. and removed type - new feature / functionality New feature or request type - bug Something is broken. labels May 28, 2020
@hidde hidde self-assigned this May 28, 2020
@hidde
Copy link
Member

hidde commented Jun 12, 2020

This issue is currently on hold, because we are awaiting an update in the third party router library we use that improves how fragment ID links are handled.

@hidde hidde modified the milestones: Version 0.4, Version 0.5 Jun 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in - accessibility There is a problem with a feature or page that gets in the way of access by some or all users. type - browser/AT support A feature or page does not work in a certain browser or assistive technology.
Projects
None yet
Development

No branches or pull requests

2 participants