Glossary - Something about wrong aria-labels [RDI 2.22]

[LIT-EIA-OWNER]

Page / URL: Glossary (all pages)

Impact on Learner: People who use assistive technologies might find it difficult or impossible to use a composite control if its managed controls lack the required child role.

Details, screenshots, coding: Certain ARIA roles must contain particular children.

Why it matters

An ARIA role attribute can be added to an element to instruct assistive technologies to treat the element as something other than its native HTML element type. For example, a

element with role="listbox" is to be treated as a listbox control, not as a static list.

Some ARIA "parent" roles identify composite controls that always include managed controls, identified by "child" roles. For example, role="listbox" identifies a composite control that manages a set of managed controls identified by role="option". People who use assistive technologies might find it difficult or impossible to use a composite control if its managed controls lack the required child role.

[LIT-EIA-OWNER]

From DT 20210414:

Not sure how to fix this error. Did a correction on April 7th in 2.2 to rename the “Glossary Title” and the “Glossary description” field. Please fix this error or tell us how to fix it.

[LIT-EIA-OWNER]

Details, screenshots, coding: Certain ARIA roles must contain particular children.

(Screenshot of the glossary circled in red??? The checkbox has no label)

An ARIA role attribute can be added to an element to instruct assistive technologies to treat the element as something other than its native HTML element type. For example, a

element with role="listbox" is to be treated as a listbox control, not as a static list.

Some ARIA "parent" roles identify composite controls that always include managed controls, identified by "child" roles. For example, role="listbox" identifies a composite control that manages a set of managed controls identified by role="option". People who use assistive technologies might find it difficult or impossible to use a composite control if its managed controls lack the required child role.

How to fix

• Identify the ARIA role that best identifies the element’s function.
• In the Chrome or Edge accessibility pane, examine the element serving as the managing control to verify it has the correct "parent" role attribute.
• Identify the elements serving as managed controls and add the appropriate "child" roles to them.
• Apply any ARIA state and property attributes that are required for the given roles.
• Make sure the value of each ARIA property attribute is correct.
• Make sure the value of each ARIA state attribute updates as needed to reflect the element’s current state.

For details about composite widgets and their required roles, see WAI-ARIA Authoring Practices 1.1: Design Patterns and Widgets.