Shopping Microsurvey includes an unlabelled visually hidden button that is focusable at the end of the container
Categories
(Firefox :: Messaging System, defect, P1)
Tracking
()
People
(Reporter: ayeddi, Assigned: jprickett)
References
(Blocks 2 open bugs)
Details
(Keywords: access)
Attachments
(2 files)
Preconditions:
- Set the
browser.shopping.experience2023.enabled
-TRUE
- Set the
browser.shopping.experience2023.optedIn
-1
- Set the
browser.shopping.experience2023.survey.pdpVisits
-4
- Set the
browser.shopping.experience2023.survey.hasSeen
-FALSE
STR:
- Reach the following PDP link: https://www.amazon.com/dp/B07V6ZSHF4?th=1
- Ensure the microsurvey
Help improve Firefox
is shown in the Shopping sidebar (if it's not, try reloading the page. <sup>I'm not sure how to reliably prompt it</sup>) - Navigate with
Tab
keypresses through the Shopping Sidebar past theHelp improve Firefox
radio button group and observe the focus indication movement between this group and the followingHow we determine review quality
control. - Enable a screen reader, i.e. NVDA on Windows
- When a screen reader is running and the
How we determine review quality
is focused, pressTab + Shift
to move the focus to the previous focusable element and observe the announcement for this control and (if possible) visible position of the focus indication
Expected:
- Only visible and active UI elements (controls that can be clicked/tapped) are receiving keyboard focus and when they are focused, the focus indication's position is clearly visible on the screen
- Every focusable with
Tab
element is announced by a screen reader so the user could hear the purpose of this element (its label/accessible name), role (button/radio button/link, etc.) and, when applicable, state.
Actual:
- The off-screen element is receiving keyboard focus, while the focus indication jsut disappears from the screen and its location remains unknown until the user presses
Tab
orShift+Tab
once again. - A button that is announced by a screen reader is not labelled and its purpose is unknown.
Reporter | ||
Comment 1•1 year ago
|
||
If a user presses Enter
while this secret button is focused, the microsurvey is dismissed that would prevent a keyboard-only user or/and a screen reader user from being able to share their feedback. This is not reversible (unless the user tries to change the about:config
which should not be expected, especially from users with cognitive difficulties who rely on a screen reader to understand the content.
Thus, bumping the accessibility severity to S2
Reporter | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Should be fixed in bug 1851264. The micro survey is still in active development, with layout changes incoming. Per the Figma spec, the dismiss button is supposed to be there, the layout just needs to be adjusted to make room for it.
Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Comment 4•1 year ago
|
||
Should the Feature Callouts have ARIA labels and tooltips as well? I don't think we were given strings for that, but we could just use the same "Close" for every dismiss button.
Comment 6•1 year ago
|
||
bugherder |
Description
•