1855492 - Investigate panel-item that is failing Tier 2 a11y_checks for Profile Migration

Status: NEW

(Firefox :: Migration, task, P3)

Description

[Anna Yeddi [:ayeddi] ❌ OOO, back June 27]

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 the existent test that would fail once the a11y-checks are enabled in the CI, the failing test was failed-if by the bug 1855491.

This task is to track the investigation into the reasons this test failed and to be able to backtrack this test once it's resolved.

If separate bugs are needed, they are to block the following bugs:

1. (all) this 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)

Test affected:

Result	Path	Error	Element ID	Element tagName	Element className
FAIL	browser/components/migration/tests/browser/browser_do_migration.js	Node is not accessible via accessibility API		panel-item

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 test failure is resolved and its associated bug is closed, remove the fail-if condition for a11y_checks from the appropriate file/section to ensure better test coverage and to avoid regressions in a11y of this component.

Comment 1

[Anna Yeddi [:ayeddi] ❌ OOO, back June 27]

New test results (Try):

PASS	browser/components/migration/tests/browser/browser_do_migration.js	We expect at least one assertion to fail because this test file is marked as fail-if in the manifest			
FAIL	browser/components/migration/tests/browser/browser_file_migration.js	Node is not accessible via accessibility API		panel-item	

Comment 2

[Anna Yeddi [:ayeddi] ❌ OOO, back June 27]

New test that is failing on Try but it looks like they're passing on Autoland:

FAIL	browser/components/migration/tests/browser/browser_permissions.js	Node is not accessible via accessibility API		panel-item		"
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:assertCanBeClicked:659
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:runIfA11YChecks/this.AccessibilityUtils:638
chrome://mochikit/content/tests/SimpleTest/AccessibilityUtils.js:handleEvent:741
chrome://mochitests/content/browser/browser/components/migration/tests/browser/head.js:selectResourceTypesAndStartMigration:344
chrome://mochitests/content/browser/browser/components/migration/tests/browser/browser_permissions.js:test_permissions/<:118
chrome://mochitests/content/browser/browser/components/migration/tests/browser/head.js:withMigrationWizardDialog:72
chrome://mochitests/content/browser/browser/components/migration/tests/browser/browser_permissions.js:test_permissions:68
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"

It was introduced by bug 1818237