Success Criterion 4.1.2
Conformance level A
W3C reference F20

Content Changes That Never Update Their Accessible Name

4.1.2 — Name, Role, Value

Scenario

Setting

A webinar platform's registration form

What’s wrong

Content changes on screen but its alt text / accessible name is never updated, so screen readers announce old, wrong information.

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

Inspect the control's accessible name/alt after the content changes: if the old value is still announced instead of the updated one, it fails.

How to fix

Update the alt text / accessible name in the same code path that updates 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 webinar platform's registration form, 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