Stop 07 · Usability & Heuristic EvaluationTopics · 7/8

Accessibility Testing

Part of the UI/UX Design Roadmap

In short

Designing for accessibility is one thing. Checking that it actually works with a screen reader, a keyboard or low vision is another. Testing is where good intentions meet reality.

Actively verifying a design works for people with disabilities — screen reader testing, keyboard-only navigation, and color contrast checks — going beyond just following guidelines on paper.

The jaadu happily pushes a friend in a wheelchair up a gentle ramp to a building door.

Think of it like this

Checking the ramp, not just drawing it

An architect draws a wheelchair ramp. But someone has to roll a wheelchair up it to know if the slope is too steep or the door at the top is too narrow. Accessibility testing is that test roll.

Watch it happen

Layers of accessibility testing

Auto scan
Contrast
Keyboard
Screen reader
Real users

1/5Run an automated tool like Lighthouse or axe. It catches some issues fast, like missing alt text or labels.

The big ideas

What you need to know

Automation is a start

Automated scans miss many problems, like confusing order or bad alt text. Always add manual checks.

Follow the focus

While tabbing, the focus ring should always be visible and move in a logical reading order.

Listen to your design

A screen reader reads what's in the code. 'Button, button, image' means labels are missing.

Zoom to 200%

Enlarge text and the page. Nothing important should get cut off or overlap.

Save yourself the pain

Common mistakes

Oops

Getting a perfect Lighthouse score and calling the site accessible.

Do this instead

A score only covers what tools can detect. Do keyboard and screen reader checks too.

Oops

Testing accessibility only right before launch.

Do this instead

Check contrast and labels in Figma, then test builds regularly. Late fixes cost much more.

Your mission

Your first screen reader test

~30 min

Quick check

An automated scan shows zero errors. What should you do next?

Go deeper

  1. 1Test a design using a screen reader to experience how it's actually announced.
  2. 2Navigate a flow using only a keyboard and note any inaccessible elements.
  3. 3Learn to use a free contrast checker on every text/background color pairing in a design.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge