Audit is added here: https://crrev.com/c/707304. CL is ready to land, bot flaked should land as soon as bot is green. Currently adding more robust checks since that CL enables the audit w/o any mock data.
Ran quick audit manually with chromevox on chromeos, found these issues:
Side nav reports "Menu with 0 items" with chromevox
Debug button "Update" doesn't provide context for a11y
Extension image unlabeled
Extension enabled button unlabeled
Details: back button unlabeled
Details: extension image unlabeled
Details: "On" Toggle unlabeled
Details: Allow in incognito button not focusable w/ chromevox
Details: Collect errors toggle button not focusable w/ chromevox
Details: Extension options button unlabeled
Details: Remove extension button double labeled
Details: "source" label ambiguous
Image overlay warning not read by a11y tools
Developer mode toggle "pressed/unpressed" should be "enabled/disabled", same for extension enabled button
Update on the issues above w/ issues for more involved fixes as well as CLs for easier ones.
Side nav reports "Menu with 0 items" with chromevox - No longer reproducible
Debug button "Update" doesn't provide context for a11y - Issue 779264
Extension image unlabeled - https://crrev.com/c/738635
Details: extension image unlabeled (labelled by above CL)
Extension enabled button unlabeled - https://crrev.com/c/739956
Details: "On" Toggle unlabeled - https://crrev.com/c/740823
Details: back button unlabeled - https://crrev.com/c/742144
Details: Extension options button unlabeled (labelled by above CL)
Details: Allow in incognito button not focusable w/ chromevox - Issue 779268
Details: Collect errors toggle button not focusable w/ chromevox (bug covers both toggles)
Details: Remove extension button double labeled - Issue 779269
Details: "source" label ambiguous - Issue 779270
Image overlay warning not read by a11y tools - Issue 779274
Developer mode toggle "pressed/unpressed" should be "enabled/disabled", same for extension enabled button - Won't fix: 'enabled/disabled' could be confusing for a control that itself can be enabled/disabled. This is to avoid getting into a state where we read the toggle is 'enabled, disabled' because the extension is enabled but cannot be disabled so we've disabled the toggle... let's avoid this.
I am un-marking this issue as a Dev blocker, since it seems that there has been enough progress. The remaining known issues are already captured by bugs attached here, with the most severe one issue 779268 .
Comment 1 by scottchen@chromium.org
, Sep 27 2017