Open Bug 1854637 Opened 7 months ago Updated 1 month ago

[meta] Investigate elements that are failing Tier 2 a11y_checks for Settings UI

Categories

(Firefox :: Settings UI, task, P3)

task

Tracking

()

People

(Reporter: ayeddi, Assigned: ayeddi)

References

(Depends on 1 open bug)

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 1854636.

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. (Interactive elements must be labeled / Node is enabled but disabled via the accessibility API) bug 1854227 (a11y_checks_labeled)
  3. (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	browser/components/preferences/tests/browser_application_xml_handle_internally.js	Interactive elements must be labeled		menulist	actionsMenu
FAIL	browser/components/preferences/tests/browser_applications_selection.js	Node is not accessible via accessibility API	typeColumn	treecol	
FAIL	browser/components/preferences/tests/browser_applications_selection.js	Node is not accessible via accessibility API	actionColumn	treecol	
FAIL	browser/components/preferences/tests/browser_cookies_exceptions.js	Node is not accessible via accessibility API	siteCol	treecol	
FAIL	browser/components/preferences/tests/browser_engines.js	Node is not accessible via accessibility API	engineChildren	treechildren	
FAIL	browser/components/preferences/tests/browser_filetype_dialog.js	Interactive elements must be labeled		menulist	actionsMenu
FAIL	browser/components/preferences/tests/browser_localSearchShortcuts.js	Node is not accessible via accessibility API	engineChildren	treechildren	
FAIL	browser/components/preferences/tests/browser_pdf_disabled.js	Interactive elements must be labeled		menulist	actionsMenu
FAIL	browser/components/preferences/tests/browser_permissions_dialog.js	Node is not accessible via accessibility API	statusCol	treecol	
FAIL	browser/components/preferences/tests/browser_permissions_dialog.js	Node is not accessible via accessibility API	siteCol	treecol	
FAIL	browser/components/preferences/tests/browser_searchDefaultEngine.js	Interactive elements must be labeled	defaultEngine	menulist	
FAIL	browser/components/preferences/tests/browser_searchDefaultEngine.js	Interactive elements must be labeled	defaultPrivateEngine	menulist	
FAIL	browser/components/preferences/tests/browser_subdialogs.js	Node is not accessible via accessibility API		label	dialogTitle
FAIL	browser/components/preferences/tests/browser_subdialogs.js	Node is not accessible via accessibility API	dialogTemplate	vbox	dialogOverlay dialogOverlay-171
FAIL	browser/components/preferences/tests/siteData/browser_siteData_multi_select.js	Node is not accessible via accessibility API	hostCol	treecol	
FAIL	browser/components/preferences/tests/siteData/browser_siteData3.js	Node is not accessible via accessibility API	usageCol	treecol	
FAIL	browser/components/preferences/tests/siteData/browser_siteData3.js	Node is not accessible via accessibility API	hostCol	treecol	
FAIL	browser/components/preferences/tests/siteData/browser_siteData3.js	Node is not accessible via accessibility API	cookiesCol	treecol	

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: 1848397
Depends on: 1869942
Depends on: 1872739
Depends on: 1872743
Depends on: 1886268
You need to log in before you can comment on or make changes to this bug.