Default and Default Private Engine comboboxes in Settings UI are unlabelled
Categories
(Firefox :: Settings UI, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox123 | --- | fixed |
People
(Reporter: ayeddi, Assigned: ayeddi)
References
(Blocks 2 open bugs)
Details
(Keywords: access)
Attachments
(1 file)
The <menulist> with id defaultEngine
that opens for the Default Search Engine
selection on Settings
> Search
is not labelled. The combobox pattern is expected to provide an accessible name for the control even when the listbox opened has an accessible name.
We could refer to the #defaultEngineGroup
container with aria-labelledby
to ensure the combobox is labeled, and also to include a description via aria-describedby
referred to the on-screen <description>
provided for the control - this would communicate the purpose of opened list of options to an assistive technology user.
Same pattern could apply to the Default Private Engine <menulist>
.
Assignee | ||
Comment 1•1 year ago
|
||
The <menulist>
with id defaultEngine
that opens for the Default Search Engine
selection on Settings
> Search
is not labelled. The combobox pattern is expected to provide an accessible name for the control even when the listbox opened has an accessible name.
We could refer to the #defaultEngineGroup
container with aria-labelledby
to ensure the combobox is labeled, and also to include a description via aria-describedby
referred to the on-screen <description>
provided for the control - this would communicate the purpose of opened list of options to an assistive technology user.
Same pattern could apply to the Default Private Engine <menulist>
.
Since the browser/components/preferences/tests/browser_searchDefaultEngine.js
a11y_checks will be passing with this change, we are also removing the fail-if
notation from its test manifest.
Depends on D197535
Updated•1 year ago
|
Updated•1 year ago
|
Comment 3•1 year ago
|
||
bugherder |
Assignee | ||
Updated•1 year ago
|
Description
•