Issue metadata
Sign in to add a comment
|
chrome://system/ is not accessible with cvox2 |
||||||||||||||||||||||
Issue descriptionMode: force_next Version: 52.0.2743.32 Reproduction Steps: 1. chrome://system/ 2. search+arrow ot other cvox2 commands to interact with page 3. Try to expand sections Observed: Like task manager, chrome://system/ isn't accessible Expected: chrome://system/ to be accessible with cvox2
,
Jun 13 2016
Interesting. I'm actually able to use Next to navigate this page. The highlight ring isn't well aligned, but I'm able to navigate. Can you give this a try again and let me know if it's still not working for you? I'm on 53.0.2764 Note: when I use Next to expand a section, I get no spoken feedback saying that the content is expanded. David, adding some sort of alert might be helpful for expanding / collapsing content.
,
Jun 13 2016
Did we audit this page in the past? The state announcement of that expand collapse button should have been an item on the audit.
,
Jun 13 2016
As a workaround, I use this System CHrome extension, which is a lot more accessible with CHromeVox Next: https://chrome.google.com/webstore/detail/system/ocjnemjmlhjkeilmaidemofakmpclcbi?utm_source=chrome-app-launcher-info-dialog
,
Jun 30 2016
,
Aug 22 2016
in M53 I am able to navigate all parts of chrome://system with ChromeVox Next. Please reopen if there's still something missing!
,
Aug 22 2016
1. THEre are some expand all/collapse all and expand widgets, but it's not clear what they're associated to. Might it be possible to use aria-labelledby or aria-describedby to provide more context? 2. GIven the system info is using a layout table, its' a bit difficult to traverse using linear-nav. WOUld it be possible to set role="presentation" on the table, so it's more cvox2-friendly? Other than the 2 above, chrome://system is a lot more accessible than previously. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Jun 12 2016