Issue metadata
Sign in to add a comment
|
Accessibility improvements to MV links |
||||||||||||||||||||||||
Issue descriptionFrom lpalmaro@: "To try this out, turn VoiceOVer on (Command F5) then press Ctrl Option Right until you get to the icons. From here, you get to the "frame zero" which I thought had been fixed -- this needs to say something more descriptive of what the area actually is. for example, recently visited sites, or something like that. From there, you need to press Ctrl Option Shift Down to get into the area, and then you can move on pressint Ctrl Option Right to go through the icons. That said, you hear that they are links, but not that they are groups (thus indicating that you can press Ctrl Option Shift Down to interact, and then get to the remove X button for each icon). Therefore, you don't know that you can access this remove button for each of the icons with a screen reader on, on Mac, as you can't get there by just pressing Ctrl Option Right and moving item by item. When you press tab, you can get through and the X buttons visually appear, but not when using a screen reader. IF you know to press Ctrl Option Shift Down to interact with the link, then press Ctrl Option Right you access the link name and then if you press it again, you access the X button, but it doesn't visually appear -- it's just the Voiceover outline around white space. What can we do to make this more discoverable to our screen reader users on Mac? Can we make each of these icons groups so a user would know to interact with it to get to more options, OR can we make the close buttons in the linear order and associate the labels for the close buttons to the link names so the user know what they are removing? And can we make it so that when you access this X button with screen reader navigation (e.g. Ctrl Option Right on Mac, or Search + Right on Chrome OS with ChromeVox), it visually appears, just as it does when you tab to it?"
,
Jun 22 2018
,
Jul 3
https://crbug.com/696272#c28 seems to be related to this, but it's unclear to me if it's exactly the same. Please review issue 696272 as well when looking at this bug - if it's the same, dupe #c28 into this bug (the title of issue 696272 no longer describes the remaining bug).
,
Jul 10
,
Aug 9
Fixed in latest Canary |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by twelling...@chromium.org
, Jun 19 2018