Success Criterion 4.1.2
Conformance level A

Complex Widget Relying on a Title Attribute for Its Name

4.1.2 — Name, Role, Value

Scenario

Setting

A streaming music app's search results

What’s wrong

title-only names on complex widgets where assistive technology support gaps make the name unavailable in practice (risk-level failure logged against name robustness).

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 a complex widget's name source in DevTools: if it relies only on a title attribute (with known inconsistent AT support), verify the name is still reliably available — if not, it fails.

How to fix

Provide the name via aria-label/labelledby rather than title alone.

<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 streaming music app's search results, this barrier is gone for screen-reader and voice-control users who can operate only what the accessibility tree exposes — they can complete the task without hitting this wall.

Who is affected