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

Component is not compatible with JAWS screen reader #40

Closed
johannesh2 opened this issue Aug 7, 2018 · 1 comment
Closed

Component is not compatible with JAWS screen reader #40

johannesh2 opened this issue Aug 7, 2018 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@johannesh2
Copy link
Contributor

Results from #12

JAWS on Win 7 (both with IE 11 and Chrome)
3.1. when the page loads: in Chrome JAWS does not announce the cookie consent popup, but in IE11 that works OK.
3.2. when the focus is moved to the first focusable element in the popup (the 'learn more' link): JAWS does not read the title nor the content of the dialog. Thus, in Chrome the consent dialog text is never read out loud.

@johannesh2 johannesh2 added the bug Something isn't working label Aug 7, 2018
@alexberazouski alexberazouski self-assigned this Aug 16, 2018
@alvarezguille alvarezguille added this to the Sprint 7 milestone Aug 16, 2018
@alexberazouski
Copy link

We changed before the banner role to alert which made NVDA to announce cookie consent message in IE11 and chrome.
As for JAWS: it started to announce message in chrome, but becomes silent in IE11.

One of the approach is to make the banner focusable and set focus on it. But to my mind it could break some other app logic.

Reading the link Learn more and message works fine if the user focuses on it now (with the role=alert)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants