A11y: chrome://accessibility it is difficult for screen reader users to understand where one section begins and ends |
||||
Issue descriptionChrome: 68.0.3416.0 (Official Build) canary (64-bit) (cohort: Clang-64) NVDA: 2018.1.1 JAWS: 2018 Steps to repro: # Open two or three tabs with any content # With JAWS or NVDA on, visit chrome://accessibility # Press 'h' several times until screen reader announces 'pages' # Use down arrow to read through the page title, URL, and options and then again to the next page title Expected: Screen reader users should be able to differentiate where one page and it's options starts and ends Actual: If there is a long list of pages, it is easy to get confused as to which action buttons apply to each page
,
Jul 27
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/964aa17d0daa5edbc647ac8e9d5acfd8b05aad20 commit 964aa17d0daa5edbc647ac8e9d5acfd8b05aad20 Author: James Wallace-Lee <jamwalla@chromium.org> Date: Fri Jul 27 21:47:01 2018 chrome://accessibility: add headings to navigate pages and windows Add <h4> to page and window titles for easier navigation. Bug: 839042 Change-Id: Ic20f90cd9379fd8c6df8122691b5819c97248338 Reviewed-on: https://chromium-review.googlesource.com/1153576 Commit-Queue: James Wallace-Lee <jamwalla@chromium.org> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#578816} [modify] https://crrev.com/964aa17d0daa5edbc647ac8e9d5acfd8b05aad20/chrome/browser/resources/accessibility/accessibility.js
,
Jul 30
Able to reproduce the issue on Windows 10 on reported version 68.0.3416.0. Verified the fix on Windows, as per comment#0 on latest chrome version #70.0.3507.0. Observed that screen reader users are be able to differentiate where one page and it's options starts and ends Hence, the fix is working as expected. Adding the verified labels. Thanks...!!
,
Aug 10
,
Aug 24
Google Chrome 70.0.3524.2 (Official Build) dev (64-bit) Firmware Version Google_Lulu.6301.136.57 Page titles are now H3s and ChromeVox can navigate them as expected. Marking bug ad verified. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dsexton@chromium.org
, May 2 2018