A11y: chrome://settings -> ,"Headings appear visually as headings however not marked up as such |
||||||
Issue description72.0.3590.0 (Official Build) dev (64-bit) (cohort: Dev) Firmware Version: Google_Cave.7820.384.0 72.0.3595.0 (Official Build) canary (64-bit) (cohort: Clang-64) ChromeVox Steps to repro: # With ChromeVox ON, goto chrome://settings page # Goto any of the page with various sub headings for ex: Advanced>Privacy and security section page # Check any Headings for example: Safe Browsing and Help improve Safe Browsing Expected: Headings should be read aloud Actual: Nothing is read aloud, so the headings are skipped, which does not make sense as if there is a heading, its to give a brief intro to the screen reader user, else the user wont have any introduction to the section he is in. Focus is completely skipped for these headings even when reading line by line. Repeat the above using JAWS screen reader: The results are not the same as above. All the headings are being read aloud sequentially.
,
Nov 8
Chrome: 72.0.3602.2 (Official Build) dev (64-bit) (cohort: Dev) I can confirm this. Headings are styled as headings, but not marked up as such. Headings should be <h3> because they are under an <h2>
,
Nov 14
,
Nov 14
,
Nov 14
,
Nov 14
Two issues here: 1. marking these labels up as headings. This is really a UX question. In theory, you could argue all labels be marked up as headings. The argument against this is that these headings really only contain one conceptual item inside (a button usually). 2. ChromeVox specific. ChromeVox skips these static text nodes because they are marked up as labels for their associated buttons. This is a screen reader feature sometimes found in ones other than ChromeVox (e.g. VO has a skip labels for controls option). In the latest builds of Chrome, it appears that someone has again changed this. The usability question for this one is you end up with tons of duplicated content like "safe browsing" "description text" "safe browsering button" etc. This effectively doubles the number of items one has to navigate through on the page.
,
Nov 14
I'm closing this bug as wontfix because David T has confirmed that this functionality is working as intended (number 2 in his comment.) As for the markup of the labels/headers/whatever it should be called (number 1 in his comment), that is indeed a UX question that is not relevant to the behavior described so it will not block me from closing this bug as works as intended. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by leberly@chromium.org
, Nov 7Status: Available (was: Untriaged)