Closed Bug 1910188 Opened 7 months ago Closed 4 months ago

[A11Y] [Microsurveys] Radio button options are not fully accessible with assistive technology

Categories

(Fenix :: Experimentation and Telemetry, defect, P3)

Firefox 130
All
Android
defect

Tracking

(Accessibility Severity:s2, firefox133 verified)

RESOLVED FIXED
133 Branch
Accessibility Severity s2
Tracking Status
firefox133 --- verified

People

(Reporter: ayeddi, Assigned: adam.orban)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxdroid])

Attachments

(5 files)

Steps to reproduce - TalkBack

  1. Turn TalkBack on.
  2. Activate the micvrosurvey feature from secret settings.
  3. Launch a microsurvey after using the print feature.
  4. Navigate to and activate Continue button
  5. Confirm the question with list of radio buttons is opened
  6. Using logical navigation with TalkBack (swiping left-to-right with one finger) focus each radio button in the survey and observe the announcement.
  7. Double-tab to activate one of the options and observe the TalkBack announcement.

Steps to reproduce - Universal Switch

  1. Turn Universal Switch on (ensure that at least one action is set to select item action, i.e. by using a phone camera as a switch and your head nod as an action to select).
  2. Repeat steps 2-5 of the TalkBack STRs above.
  3. While using (default) Item scan mode with Universal Switch, observe the focus order that the switch is offering on the survey screen.
    • To activate the Item scan, open the switch menu > Settings > toggle Item/Point scan (point scan is likely to be working while on a web page)
  4. Attempt to activate one of radio buttons with the switch

Expected behavior

  1. TalkBack announces radio buttons as: not selected, {label}, Radio button, {1} of {6}, double-tap to activate or selected, {label}, Radio button, {1} of {6}, double-tap to activate
  2. Universal Switch includes all radio buttons in its (item) focus order and allows a radio button to be selected without a point scan.

Actual behavior

  1. TalkBack announces radio buttons as: Not selected, {label}, Radio button or Selected, {label}, Radio button:
    • no double-tap to activate hint indicates that the element is not programmatically actionable, likely it is not focusable for the Accessibility API (lacking accessibility event, maybe?) and only has a click listener and the view is not set to be focusable - this causes the Switch to skip the controls in the item scan mode too. Also, the programmatic role needs to be checked, since the OS-provided radio buttons seem to work and have a hint as expected
    • list/set size and position is missing for this radio group
    • maybe the selected state is provided as a string?
  2. Universal Switch fully skips these radio buttons in its (item) focus order and only allows a radio button to be selected with a point scan mode (which is a tedious workaround).

Device information

  • Firefox version: Nightly 130.0a1
  • Android device model: Galaxy A54
  • Android OS version: Android 13

Captured an example of steps needed to submit a microsurvey feedback with Universal Switch, each activation of an item is a user action ("select" action of their switch). Of course, users relying on Universal Switch are likely to have the higher speed of interaction with them but not all and not always

The severity field is not set for this bug.
:towhite, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(towhite)
Component: Experimentation and Telemetry → Design System and Theming
Flags: needinfo?(towhite)
Component: Design System and Theming → Experimentation and Telemetry
Severity: -- → S3
Priority: -- → P3

The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:towhite, could you consider increasing the severity?

For more information, please visit BugBot documentation.

Flags: needinfo?(towhite)
Assignee: nobody → adam.orban
Status: NEW → ASSIGNED

Investigated the issue and the expected behavior for talkback, when radio buttons are used, is "double tap to toggle" and not "double tap to activate".
Fixed the issue and now the complete message when the user selects a radio button is:
when not selected "not selected, {label}, Radio button, {1} of {6}, double-tap to toggle"
when selected "Selected"

Severity: S3 → S2
Flags: needinfo?(towhite)
Pushed by rtudor@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a8b2e1006d27 treat survey options as group for talkback a11y r=android-reviewers,twhite
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
Flags: qe-verify+

The behavior now is as in the description in Comment 6:

  • when not selected "not selected, {label}, Radio button, {1} of {6}, double-tap to toggle"
  • when selected "Selected"

However there's an addition of reading an action that doesn't do anything, described here (The long press action).

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: