Issue metadata
Sign in to add a comment
|
[A11y Assessment - NTP One Google bar] apps submenu order can't be changed with AT software |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 64.0.3251.0 (Official Build) canary (64-bit) (cohort: 64-Bit) Windows 10 Enterprise Version 1607 Build 14393.1770 NVDA 2017.3 JAWS 2018.1710.42 private preview release ZoomText Private Beta - 11.7.11.410 # Chrome NTP with no additional AT software # Navigate to the Google Bar > Apps menu using keyboard, press space to collapse # Navigate through the list using tab or up/down arrow keys, press space Expected: space will open the link Actual: space adds small arrows around the icon, puts you into a mode to move the link around within the sub menu # Launch AT software and Chrome NTP # Navigate to the Google Bar > Apps menu, press space to collapse Expected: way to access the same feature as non-screen reader users Actual: space doesn't have the same functionality so reordering not available
,
Nov 7 2017
,
Nov 29 2017
,
Dec 14 2017
,
Dec 15 2017
Unassigning myself to give a dev a chance to make a comment on what to do with this.
,
Dec 15 2017
I think this first needs feedback from an a11y expert, since I have no idea what to do here. The One Google Bar uses the Space key to trigger reordering via the keyboard, and it seems like ZoomText intercepts Space? If so, I don't know what we can do about it. We could use another key I guess, but that feels like a poor workaround.
,
Dec 15 2017
,
Dec 15 2017
This is outside the scope of the Chrome team. Some ideas: * Give it a role of grid, make each item a cell. That's important because the arrow keys rearrange the apps two-dimensionally, even though the left and right arrows do wrap. It also has the side effect that it will put JAWS and NVDA in focus mode and pass more keystrokes through to the app. If the user is in browse mode, keys like Space are intercepted by the screen reader. * Add some accessible text, maybe in the description, to teach the keyboard behavior. Enter to open, Space to start rearranging. * When the user is rearranging, give good feedback.
,
Dec 15 2017
Setting to p2 since this was found during our assessment
,
Dec 18 2017
Updated internally at b/70808687 Changing to pri 3 now that it is filed internally.
,
Jul 10
,
Aug 8
,
Sep 12
,
Nov 14
,
Jan 8
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by treib@chromium.org
, Nov 3 2017Components: UI>Browser>NewTabPage