Open
Bug 1868216
Opened 1 year ago
Updated 9 months ago
Accessible name of the magnifying glass icon is "View Site Information"
Categories
(Firefox :: Address Bar, defect, P2)
Firefox
Address Bar
Tracking
()
NEW
Accessibility Severity | s3 |
People
(Reporter: ayeddi, Assigned: yazan)
References
Details
(Keywords: access, papercut, Whiteboard: [sng][search-papercut][search-a11y])
Attachments
(1 file)
STR:
- Ensure a screen reader is running
- Open Firefox
- With a screen reader, navigate to the address bar's first control that is visually appearing as a magnifying glass
- Observe a screen reader's announcement
- Open Accessibility Inspector in Devtools and review the accessible properties of this control
Expected:
- Visually labelled as a magnifying glass icon and located within a search bar of a browser, the control is expected to be announced as
Search
Actual:
- The control is announced as
Visit Site Information
that is not implied from its visual label (icon)
Notes:
- It may be that the magnifying glass is just an image placed over the real Lock and shield control and that this image has no functionality serving as a mere visual label for the search input of the awesomebar. In this case, we would need to ensure this image is rendered as such by the Accessibility API and that the underlying control is hidden for all users, not only for sighted users without screen readers.
- If the magnifying glass is expected to be functioning as a button, it should be marked as such and be accessible with a screen reader at minimum (we probably won't want to make it keyboard focusable since this would create an additional tab stop in an already complex component and there are other keyboard accessible ways exist to submit the search request as well. In this case we would still need to make sure the visually hidden control is hidden for all users.
At this moment, the labeling of the element is very confusing for a sighted user of an assistive technology, and it would especially affect users of screen readers with low vision, with cognitive difficulties, neurodiverse users, users with dyslexia, and users of speech-to-text software (i.e. voice control).
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Updated•9 months ago
|
Assignee: nobody → yalmacki
You need to log in
before you can comment on or make changes to this bug.
Description
•