Open Bug 1854513 Opened 10 months ago Updated 6 months ago

[meta] Investigate elements that are failing Tier 2 a11y_checks for Core: Document Object Model

Categories

(Core :: DOM: Core & HTML, task, P3)

task

Tracking

()

REOPENED

People

(Reporter: ayeddi, Assigned: ayeddi)

References

Details

(Keywords: access, meta)

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, the failing tests were failed-if by the bug 1854512.

This task is to track the investigation into the reasons each of these tests failed and to be able to backtrack these tests once they're resolved.

Individual bugs to block the following bugs

  1. (all) this meta bug
  2. (Node is not accessible via accessibility API / Node is not focusable via the accessibility API / Node is enabled but disabled via the accessibility API) Bug 1848394 (a11y_checks_focusable)

Tests affected:

FAIL	dom/tests/browser/browser_bug1008941_dismissGeolocationHanger.js	Node is not accessible via accessibility API	nav-bar	toolbar	browser-toolbar
FAIL	dom/tests/browser/browser_focus_steal_from_chrome_during_mousedown.js	Node is not accessible via accessibility API		browser	

Jobs affected:

  1. test-linux1804-64-qr/opt-mochitest-browser-chrome-swr-a11y-checks-${1-7} (Try run)

Some Tier 2 accessibility checks for click events fired on controls that should be keyboard accessible and have valid labels were failing for this component. They were captured by testing/mochitest/tests/SimpleTest/AccessibilityUtils.js via bug 1692110. These failing tests should be temporarily skipped in the directory's browser.ini file while we investigate these failures. For all 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.

Depends on: 1872727
Depends on: 1872731

all the a11y_checks test failures were resolved, thus I am closing this meta bug

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED

One more a11y_checks failure is left to be investigated:

Result	Path	Error	El ID	El tagName	El className	Stack trace
FAIL	dom/midi/tests/browser_midi_permission_gated.js	Node is not focusable via the accessibility API		button	popup-notification-primary-button primary panel-footer-button	"
chrome://mochikit/content/browser-test.js:test_ok:1583
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:a11yFail:342
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:assertFocusable:385
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:assertCanBeClicked:668
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:runIfA11YChecks/this.AccessibilityUtils:638
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:handleEvent:741
chrome://mochitests/content/browser/dom/midi/tests/browser_midi_permission_gated.js:testRequestMIDIAccess:293
chrome://mochikit/content/browser-test.js:handleTask:1134
chrome://mochikit/content/browser-test.js:_runTaskBasedTest:1206
chrome://mochikit/content/browser-test.js:Tester_execTest:1348
chrome://mochikit/content/browser-test.js:nextTest/<:1123
chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/<:1058
"
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
You need to log in before you can comment on or make changes to this bug.