w3c / aria

Accessible Rich Internet Applications (WAI-ARIA)
https://w3c.github.io/aria/
Other
639 stars 123 forks source link

Which roles serve as group names and descriptions? #1710

Open JAWS-test opened 2 years ago

JAWS-test commented 2 years ago

Which ARIA roles serve as group names/descriptions for contained child elements? For some it seems to be clear (e.g. role=group), for others not (role=generic may not have a name, but a description).

Maybe this can be added in the specification. Or is this left to AT to decide for itself which parent names and descriptions are relevant?

Currently the output is not consistent with screen readers, see: https://github.com/FreedomScientific/VFO-standards-support/issues/612

jnurthen commented 2 years ago

@JAWS-test can you add some more info. I'm not clear on the ask.

JAWS-test commented 2 years ago

@jnurthen

The label of some elements serves as a group label of contained elements. E.g. <legend> in <fieldset> is the group label for all form elements inside. The question now is, which elements serve as group label (and if their description then also serves as group description)

See: https://github.com/FreedomScientific/VFO-standards-support/issues/612 and https://codepen.io/jaws-test/pen/LYeRgJV

chlane commented 2 years ago

@jnurthen I think an<h1> inside a <section> element could be a label and a description if it is a lengthy heading.

scottaohara commented 2 years ago

That would be very problematic @chlane

sections do not get exposed as region landmarks if not named. If that were to change, that’d undo this purposeful restriction on the mapping so as to not expose an over abundance of region landmarks.