- 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
A tester reviewing a webinar platform's registration form finds this: content changes on screen but its alt text / accessible name is never updated, so screen readers announce old, wrong information.
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. On a webinar platform's registration form, that means they can't complete the task without extra help.
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.
Outcome
With the fix in place on a webinar platform's registration form, they get the same outcome as everyone else.
Who is affected
Screen-reader and voice-control users who can operate only what the accessibility tree exposes.
Learn more
- Understanding Understanding document (opens in a new tab)
- Technique Related technique (opens in a new tab)
Related scenarios
- Custom Dropdown or Slider With No Accessibility API Support
- Scripted Link or Button With No Real Role or Keyboard Support
- Clickable Div Turned Into a Control but Given No ARIA Role
- Form Field With No Programmatic Label at All
- Assistive Technology Never Told Which Element Currently Has Focus
- Multi-Part Field Where Each Box Has No Individual Name