-
Notifications
You must be signed in to change notification settings - Fork 13
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
Jaws 2019 not reading live child elements in Chrome #222
Comments
The problem occurs not only with live regions (such as status, log, alert, dialog, timer, marquee, alertdialog), but also with other ARIA roles, e.g. article, banner, img, term. The problem occurs only in Edge (Chromium) and Chrome, not in IE and Firefox. As long as the bug is not fixed by Freedom Scientific, there are 5 possible solutions:
|
@zakeckert, please provide the |
I am unable to do that as I have changed jobs and no longer have access to JAWS to properly update the plinkr to accurately reflect the issue. |
Tested with JAWS 2024 and Chrome 119 on Windows 11, could not reproduce using test case |
Summary
When keyboard focus is on a container element, child elements that are have role="status" or role="alert" won't be read. Non-live elements will be read. This does not happen in Firefox.
Steps to reproduce:
Expected result
All text would be read in each of the elements
Actual result
Text in the green outlined elements is read in its entirety
Text in the red outlined element is not read in its entirety
Example
https://plnkr.co/edit/klCRt1ZNLZVd7WGxXz7M?p=preview
JAWS version and build number
2019.1903.47
Operating System and version
Windows 10
Edition: Windows 10 Enterprise
Version: 1903
OS build: 18362.53
Browser and version:
Google Chrome Version 75.0.3770.142 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered: