1873255 - Update 5 mochitests that click on an addon-name-container instead of its containing link to pass a11y-checks

Status: RESOLVED FIXED

(Toolkit :: Add-ons Manager, task, P3)

Description

[Anna Yeddi [:ayeddi]]

There are following tests in toolkit/mozapps/extensions/test/browser/ that fail a11y_checks when they send a click on the clickable but not accessible container .addon-name-container in:

1. browser_globalwarnings.js#11,
2. browser_html_detail_view.js#346,405,
3. browser_html_updates.js#31
4. browser_gmpProvider.js#52
5. switchToDetailView() in head.js#1696 in browser_html_pending_updates.js

• while there is a fully accessible link element that is included in each card and thus should be an expected target for the Details View activation to test behavior for all users is functioning.

We could update this test to query the link element and send a click to it to simulate and confirm the card is accessible for users of keyboards and assistive technology as well as mouse/touch users, and to allow the a11y-checks to pass. In this case, we need to update the fail-if notations of the test manifest accordingly.

Comment 1

[Anna Yeddi [:ayeddi]]

Attachment: Bug 1873255 - Update 6 mochitests that click on an addon-name-container instead of its containing link to pass a11y-checks. r=rpl!

There are following tests in toolkit/mozapps/extensions/test/browser/ that fail a11y_checks when they send a click on the clickable but not accessible container .addon-name-container in:

1. browser_globalwarnings.js#11,
2. browser_html_detail_view.js#346,405,
3. browser_html_updates.js#31
4. browser_gmpProvider.js#52
5. switchToDetailView() in head.js#1696 in browser_html_pending_updates.js

• while there is a fully accessible link element that is included in each card and thus should be an expected target for the Details View activation to test behavior for all users is functioning.

We could update this test to query the link element and send a click to it to simulate and confirm the card is accessible for users of keyboards and assistive technology as well as mouse/touch users, and to allow the a11y-checks to pass. In this case, we need to update the fail-if notations of the test manifest accordingly.

Comment 2

[Anna Yeddi [:ayeddi]]

Another test that is affected: browser_menu_button_accessibility.js#72

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/b0a09cf1582e
Update 6 mochitests that click on an addon-name-container instead of its containing link to pass a11y-checks. r=rpl

Comment 4

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/b0a09cf1582e