Open Bug 2086547 Opened 19 days ago Updated 8 hours ago

[customizable-menu] "Customize menu" accessibility support

Categories

(Firefox for Android :: Menu, task)

All
Android
task

Tracking

()

ASSIGNED

People

(Reporter: petru, Assigned: petru)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxdroid][android-core])

Attachments

(10 external files, 1 obsolete file)

Attached image a11y specs.png (obsolete) —
Attachment #9670469 - Attachment is obsolete: true
See Also: → 2092011
See Also: → 2092153

Also check that Preview and Reset to default are read as buttons, as the design asks, which they already are.

The position follows the names in the description, for TalkBack to read it after them,
as in the design, whatever order of state and description is set in TalkBack.
Eg: "VPN. Position 2 of 5" or "Back, Forward, Share, Refresh. Position 1 of 5".

Not all of them are menu sections so a read of the total would be confusing for the user.
Each menu section already has their position and total of sections siblings read.

Before: "VPN. Position 2 of 5. In list. 11 items"
After: "VPN. Position 2 of 5. In list"

Only the sections the design names get a name: Page controls, Page actions, Libraries and Accounts and settings.
The others read just the names of their items.

Move it out of the drag handler, for the accessibility actions of the next commits to save their moves the same way.

The moves are saved the same way as the ones done by dragging.

The sections which cannot be removed from the menu have no action hiding them.

After Move up, Move down, Hide or Unhide, TalkBack now says what happened,
e.g. "VPN moved to position 3 of 5", "VPN removed" or "VPN added to menu".

The announcement is drawn over the list, because TalkBack is not told about
changes to a node that another one covers.

Keeping it laid out where it was, or bringing it into view, lets accessibility services keep their focus on it.

When the customize menu screen opens the menu as a preview, TalkBack now first reads
the whole menu as the heading "Menu preview. Items can't be activated here.", as the
design asks, before its handle and items.

It is set on the view of the menu rather than on a Compose node, as a Compose node
can't be a focusable heading spanning the whole menu without TalkBack also reading
its children.

To test:

  • Turn on TalkBack, open the customize menu screen and tap Preview.
  • "Menu preview. Items can't be activated here, heading" is read first, with the
    focus around the whole menu, then "Close menu" and the menu items one by one.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: