Success Criterion 4.1.2
Conformance level A

Accordion or Tab Missing Its Expanded or Selected State

4.1.2 — Name, Role, Value

Scenario

Setting

A calendar app's event-creation form

What’s wrong

Accordion/disclosure triggers missing aria-expanded (the open/closed state in code) — tabs missing aria-selected (the selected state in code)/tablist semantics.

Example

<div class="checkbox" onclick="toggle()"></div>

Why it matters

Screen-reader and voice-control users who can operate only what the accessibility tree exposes.

How to test

Toggle an accordion/tab component and check DevTools: aria-expanded/aria-selected should be present and update — missing attributes fail.

How to fix

Add aria-expanded (the open/closed state in code) to disclosure triggers and full tab/tablist/aria-selected (the selected state in code) semantics to tabs.

<input type="checkbox" id="opt-1">

<label for="opt-1">Email notifications</label>

A native input exposes its role and checked state automatically; a styled div exposes none of that without a lot of manual ARIA.

Outcome

On a calendar app's event-creation form, this barrier is gone for screen-reader and voice-control users who can operate only what the accessibility tree exposes — they get the same result as anyone else here.

Who is affected