[meta] Temporarily disable some a11y_checks for components with separate bugs filed
Categories
(Testing :: General, task)
Tracking
(Not tracked)
People
(Reporter: ayeddi, Assigned: ayeddi)
References
(Depends on 1 open bug)
Details
(Keywords: access, meta)
Attachments
(1 obsolete file)
Do not perform accessibility checks on files that fire click events on controls that should be keyboard accessible too (captured by testing/mochitest/tests/SimpleTest/AccessibilityUtils.js
via bug 1692110) for which there are individual bugs filed.
When the bug is resolved, remove the skip-if
condition for a11y_checks
for appropriate files to ensure better test coverage and avoid regressions in a11y.
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Comment 1•7 months ago
|
||
We are working on enabling Tier 2 a11y-checks to ensure our products have basic accessibility built-in (bug 1692110) and before that, we need to prepare the existing code base. While we triage and investigate existent tests that would fail once the a11y-checks are enabled in the CI, we are going to expect to be failing these tests altogether and then handle each one of them individually.
This task is to expect failing of these tests with fail-if
condition of the failing tests while we continue investigation into the reasons these tests failed and to be able to backtrack these tests once they're resolved.
Related bugs:
- Fail-if tests: meta bug 1848402
- Explore capturing click events for a11y_checks: bug 1692110
Depends on D190523
Comment 2•7 months ago
|
||
Comment on attachment 9357530 [details]
Bug 1848402 - Temporarily fail-if some Tier 2 a11y_checks failing on Autoland. r=Jamie
Revision D190524 was moved to bug 1858041. Setting attachment 9357530 [details] to obsolete.
Assignee | ||
Updated•2 months ago
|
Description
•