Open Bug 1783925 Opened 2 years ago Updated 8 months ago

Consider removing CSS marker from summary element's accessible name

Categories

(Core :: Disability Access APIs, defect)

Desktop
Unspecified
defect

Tracking

()

People

(Reporter: scottaohara, Unassigned)

Details

Attachments

(1 file)

The default CSS marker is included in the summary element's accessible name. When looking at Firefox's accessibility panel the name is returned as "▸ Whatever text I entered" when in the collapsed state. When expanded, the triangle changes to be downward pointing, and due to the accName change, the name of the control is re-announced.

This results in the spoken string of "Filled down pointing small triangle" or "Filled right pointing small triangle" followed by the actual name of the control, every time the expanded/collapsed state of the summary changes (variations in the exact wording of the triangle will vary depending on if you are using NVDA, JAWS or VoiceOver).

Note: with macOS Firefox + VO, if one were to style away the marker then no announcement of state is made at all, as the state change doesn't appear to be announced. I'm uncertain at this time if this is a Firefox issue, or a VoiceOver issue. But figured I would mention it here just in case, as if the behavior is changed to not announce the marker, then something would need to be adjusted so that Firefox paired with VoiceOver would still be able to announce a state change. Since right now, the triangle direction and re-announcement of the accName is the only cue for this pairing.

Test case:
https://codepen.io/scottohara/pen/xxWJOPp

Expected result:
Do not include the triangle marker as part of summary's accessible name, thus allowing the expanded/collapsed state alone to serve as the mechanism to inform users of the current state of the control, and removing the extra triangle marker description that precedes every non-styled instance of a summary element's accName.

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

For more information, please visit auto_nag documentation.

Flags: needinfo?(asa)

This seems reasonable, :Jamie what do you think?

Flags: needinfo?(asa) → needinfo?(jteh)
Severity: -- → S4

It seems reasonable, but I'm not sure how we'd implement it yet.

Component: Disability Access → Disability Access APIs
Flags: needinfo?(jteh)
Product: Firefox → Core

The combination of Firefox and VoiceOver now announces the state of the summary independently of the styling.

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

Attachment

General

Creator:
Created:
Updated:
Size: