Closed
Bug 1872925
Opened 5 months ago
Closed 5 months ago
Add an accessible name to a chromebutton in Desktop UI accesskeys test
Categories
(Firefox :: General, task, P3)
Firefox
General
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox123 | --- | fixed |
People
(Reporter: ayeddi, Assigned: ayeddi)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Attachments
(1 file)
The browser/base/content/test/general/browser_accesskeys.js sends a click on a custom chromebutton that lacks an accessible name which is reported by the a11y_checks. We need too add an aria-label for this control so the accessibility tests are passing and this would also allow us to remove the fail-if notation from its test manifest.
|
Assignee | |
Updated•5 months ago
|
Summary: Add an exception from a11y_checks for a click on a web content in Desktop UI → Add an accessible name to a chromebutton in Desktop UI accesskeys test
|
|
Assignee | |
Comment 1•5 months ago
|
||
The browser/base/content/test/general/browser_accesskeys.js sends a click on a custom chromebutton that lacks an accessible name which is reported by the a11y_checks. We need too add an aria-label for this control so the accessibility tests are passing and this would also allow us to remove the fail-if notation from its test manifest.
|
||
Updated•5 months ago
|
Assignee: nobody → ayeddi
Status: NEW → ASSIGNED
Pushed by ayeddi@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1ee0c495adf3 Add an accessible name to a chromebutton in Desktop UI accesskeys test. r=mconley
|
||
Comment 3•5 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
status-firefox123:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•