• Success Criterion 4.1.2
  • Conformance level A

Expanded State Attribute That Never Updates When Toggled

4.1.2 — Name, Role, Value

Scenario

Setting

A fitness app's workout tracker

What’s wrong

aria-expanded (the open/closed state in code) present but never updated by JS (state stuck).

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 a stateful control (expand, select, check) and watch DevTools live: if the state attribute doesn't change value, it fails.

How to fix

Update aria-expanded (the open/closed state in code) in the same handler that opens/closes the content.

<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 fitness app's workout tracker, this barrier is gone for screen-reader and voice-control users who can operate only what the accessibility tree exposes — they no longer have to work around this.

Who is affected

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

Learn more