Heading elements not read properly by Jaws
Reported by
aaron.na...@pearson.com,
Aug 31 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. On a machine with Jaws 17 open the attached page 2. Have Jaws read the content What is the expected behavior? Content should read something like this: "Heading Level 1, Heading 1, Heading Level 2, Heading 2, Heading Level 3, Heading 3, Heading Level 4, Heading 4" What went wrong? What is does read is this: "Heading Level 2, Heading 1, Heading Level 2, Heading 2, Heading Level 2, Heading 3, Heading Level 2, Heading 4" It is identifying all of the heading levels as level 2. Did this work before? N/A Chrome version: 52.0.2743.116 Channel: stable OS Version: Windows 10 Flash Version: If I add role="header" and aria-level="X" to the markup it will read the heading levels properly. That shouldn't be necessary for this, though. The behavior is the same in Windows 7 and 10.
,
Dec 2 2016
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36 Confirmed. You can also use http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_headers . Open JAWS, press INS + F6, and look at the headers list. They'll all appear as heading level 2. Using other browsers will display the actual H level.
,
Dec 11 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 Deleted