1849028 - Investigate failed Tier 2 a11y_checks for DevTools after the larger a11y improvement work is completed

Status: NEW

(DevTools :: General, task, P3)

Description

[Anna Yeddi [:ayeddi]]

To Do:

1. Remove the fail-if conditions that were set in Bug #1849021
2. re-run the a11y-checks jobs
3. investigate the updated results.

Jobs affected:

1. test-linux1804-64-qr/opt-mochitest-devtools-chrome-a11y-checks-1 (Try run)
2. test-linux1804-64-qr/opt-mochitest-devtools-chrome-a11y-checks-2 (Try run)
3. test-linux1804-64-qr/opt-mochitest-devtools-chrome-a11y-checks-3 (Try run)
4. test-linux1804-64-qr/opt-mochitest-devtools-chrome-a11y-checks-4 (Try run)
5. test-linux1804-64-qr/opt-mochitest-devtools-chrome-a11y-checks-5 (Try run)

---

Some Tier 2 accessibility checks for click events fired on controls that should be keyboard accessible were failing for this component. They were captured by testing/mochitest/tests/SimpleTest/AccessibilityUtils.js via bug 1692110. These failing tests were temporarily skipped in the directory's browser.ini file. After the ongoing accessibility improvements work is completed, we'll need to re-run a11y-checks, investigate new failures, and for confirmed bugs individual defects should be filed.

When the individual test failures are resolved and the individual bugs are closed, remove the fail-if condition for a11y_checks from the appropriate files/sections to ensure better test coverage and to avoid regressions in a11y of these components.

Comment 1

[Mathew Hodson]

browser_net_header-docs.js test should be fixed by bug 1894758