Issue metadata
Sign in to add a comment
|
[A11y assessment] Back, forward, refresh buttons not always read |
||||||||||||||||||||||
Issue descriptionChrome 63.0.3219.0 (Official Build) canary (64-bit) (cohort: 64-Bit) Windows 10 Enterprise Version 10.0.14393 Build 14393.1593 NVDA 2017.3 JAWS 2018 Beta What steps will reproduce the problem? # Launch browser and JAWS # Go to several pages to enable the back button # Put focus into the omnibar (F6) # Shift + tab to navigate backwards to buttons # Shift to navigate forwards through buttons back to Omnibar What is the expected result? All button labels spoken all the time What happens instead? Button labels sometime read, sometimes not. Chrome + JAWS reads "Reload Button Reload this page To activate press spacebar." then just says Tab as it moves backwards. When I tab back to the reload button, it doesn't say anything and just says Tab. Chrome + NVDA acts as expected. Related to https://bugs.chromium.org/p/chromium/issues/detail?id=766867
,
Sep 19 2017
Reproing in JAWS 18.0.4104 I can produce the same behavior with JAWS 18.
,
Sep 20 2017
,
Oct 17 2017
,
Oct 27 2017
This also applies to other areas of the UI such as Customize and Control Menu items that are not applicable at certain times. For example, if one tab is open, the Bookmarks > "Bookmark open pages..." text is grayed out and not in the tab order.
,
Dec 14 2017
,
Dec 21 2017
,
Dec 22 2017
Issue 792706 has been merged into this issue.
,
Dec 22 2017
https://chromium-review.googlesource.com/c/chromium/src/+/842475
,
Jan 19 2018
Removing the a11y-testers label since I agree with the dupe.
,
Jan 23 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5a82fc5c7cda26056d495448b176a59fd0031e36 commit 5a82fc5c7cda26056d495448b176a59fd0031e36 Author: Dominic Mazzoni <dmazzoni@chromium.org> Date: Tue Jan 23 21:53:40 2018 Remove button_drop_down accessibility role It's not necessary, as a role of "button" with the "has pop up" state is fully supported and sufficient. The button_drop_down role wasn't even being mapped correctly on Windows, leading to inconsistent feedback with some screen readers. Bug: 766856 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Ib7f631a759ab44ffc3307204bcc74a9471afc22a Reviewed-on: https://chromium-review.googlesource.com/842475 Reviewed-by: David Tseng <dtseng@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Michael Giuffrida <michaelpg@chromium.org> Reviewed-by: Scott Violet <sky@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#531363} [modify] https://crrev.com/5a82fc5c7cda26056d495448b176a59fd0031e36/chrome/browser/resources/chromeos/chromevox/cvox2/background/automation_predicate.js [modify] https://crrev.com/5a82fc5c7cda26056d495448b176a59fd0031e36/chrome/browser/ui/views/toolbar/toolbar_button.cc [modify] https://crrev.com/5a82fc5c7cda26056d495448b176a59fd0031e36/chrome/common/extensions/api/automation.idl [modify] https://crrev.com/5a82fc5c7cda26056d495448b176a59fd0031e36/content/app/strings/content_strings.grd [modify] https://crrev.com/5a82fc5c7cda26056d495448b176a59fd0031e36/content/browser/accessibility/browser_accessibility_android.cc [modify] https://crrev.com/5a82fc5c7cda26056d495448b176a59fd0031e36/third_party/closure_compiler/externs/automation.js [modify] https://crrev.com/5a82fc5c7cda26056d495448b176a59fd0031e36/ui/accessibility/ax_enums.idl [modify] https://crrev.com/5a82fc5c7cda26056d495448b176a59fd0031e36/ui/accessibility/platform/ax_platform_node_win.cc
,
Jan 24 2018
Verified the fix on Windows-10 Chrome version #66.0.3330.0 as per the comment #0. Attaching screen cast for reference. Observed that JAWS in combination with chrome when launched, spoke all the actions performed. Hence, the fix is working as expected. Adding the verified labels. Thanks...!!
,
Feb 12 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Sep 19 2017