Accessibility Lab

What does this button tell you?

The same visual control can expose very different information through the accessibility tree.

Needs
Browser
Optional
Screen reader · accessibility inspector
Time
~3 minutes
You'll test
Accessible names

Interface demonstration: this exercise demonstrates product behaviour; it is not intended to simulate a disability or another person's lived experience.

Why is this not a disability simulation?

These exercises compare how interfaces behave. They do not reproduce the experience of living with a disability, and no single demonstration can represent everyone’s experience. You can examine the interface using your usual input method or assistive technology without pretending to be someone else.

Try it here

Both examples use the same visible trash-can symbol. The first deliberately exposes no useful accessible name.

Unnamed

Named

What can you tell from the browser alone?

Visually, the two controls look the same. That observation is useful: you cannot determine the programmatic difference by sight alone. The browser-only lesson is recognising the limit of the evidence you currently have.

Run the optional experiment

If you have a screen reader available, compare what each button announces. If you have an accessibility inspector, compare their computed accessible names. These tools reveal the difference that the visual interface does not.

Read the related barrier.

Follow the evidence trail

Barrier Screen-reader testing guide WCAG 4.1.2 Name, Role, Value

A useful accessible name is one part of control accessibility; this example does not establish the quality of the surrounding task.