-
Notifications
You must be signed in to change notification settings - Fork 12
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
Regions with labelledBy are being announced incorrectly #102
Comments
@BenKeyFSI This is still happening in JAWS 2020.2004.66, see https://cdpn.io/TPG/debug/8bb3fad8b16b3fd9bed8265d50c7f804 |
is this actually an issue, or just how JAWS immediately navigates into landmark regions and begins announcing the first element within? for instance, if the first element within the provided example were a paragraph with text "hello", JAWS would navigate to the region by use of the R key, announce "hello" as that is where the virtual cursor is placed, and then announce "This week's poll, region". |
@scottaohara I had the same question so I created the codepen included in my last comment. Have you checked it out? |
just responding here to our offline convo, but yes. checked both the original example and new pen out. |
I would say: It is a bug:
|
Please also see nvaccess/nvda#7823 (comment) regarding redundant heading and region announcements. NVDA was reading the region label and then the (identical) heading label, but it isn't any more. |
Summary
http://mars.dequecloud.com/demo/RegionExample.htm#ex1
See this example page.
Press R to navigate through the page regions
Expected result
Actual result
Example
Additional Information
The markup shows a div with a role="region", and a labelledBy referring to an h3 tag. I think the labelledBy is being confused and announcing the entire h3 tag instead of just the contents.
Also, when I use Ins+F3 to view a list of regions, the region labels say:
JAWS version and build number
JAWS 2018.1807.8 ILM
Operating System and version
Seen on Windows 7 professional SP1, and Windows 10
Browser and version:
Firefox 56.0, and Firefox 61.0.2 (on win7);
Firefox 61 on Win10 (not sure of the minor version)
The text was updated successfully, but these errors were encountered: