Accessibility Lab

Can you reach it without a pointer?

Compare a pointer-operable action with controls that also work using a keyboard.

Needs
Browser + keyboard
Optional
Screen reader + mouse or touchscreen
Time
~3 minutes
You'll test
Keyboard reachability and operation

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

First, use Tab and Enter or Space to try the three actions without a pointer. Then use a mouse or touchscreen to activate Preview. What changes?

Preview

No action activated yet.

The middle control is intentionally pointer-operable but not keyboard-focusable or keyboard-operable. It is an example of an inaccessible interaction, not a recommended implementation.

What did the interface require?

The Preview action works with a pointer, but keyboard users cannot reach it through normal focus navigation. Looking like a button does not provide the semantics or interaction behaviour of a button. The other two actions are real buttons and respond to keyboard activation.

What would a better implementation look like?

Use a native <button> for Preview, connect it to the same action and retain visible keyboard focus. An equivalent keyboard-operable way to accomplish the same result may also satisfy the relevant keyboard requirement, but none is supplied for Preview in this intentionally flawed example.

Go deeper — optional

With a screen reader, compare the real buttons with the visual-only Preview control. The status message and this explanation remain available without using the inaccessible control. With developer tools, inspect the underlying elements.

Read the related barrier · Use the keyboard testing guide

Follow the evidence trail

Barrier Testing guide WCAG 2.1.1 Keyboard

This Lab is one controlled example. Its result is evidence about this example, not proof that every related state or user experience has been covered.