Practice · Accessibility
Rank accessibility failures by severity
Accessibility Medium at worst 27 of 30
Try it yourself
Google's accessibility check on one page. All four failed, and all four are worth fixing.
Which one stops somebody using the site at all, rather than making it harder?
-
Serious, and it affects a lot of people — anyone with low vision, and everybody outdoors in sunlight. The text is hard to read. It can still be read.
-
This is the one. A button with no name is announced as "button" and nothing else, so somebody using a screen reader is asked to choose between three identical unmarked controls. It is usually an icon-only button — a basket, a search magnifier — needing nothing more than aria-label to fix.
-
Close second, and often the same underlying habit. A form can still be worked through by guessing from the surrounding text; an unnamed button gives you nothing to guess from.
-
Real, and a one-line fix — without it a screen reader may read English in a French accent. Annoying rather than blocking.
Pick a line. Every one of them has an answer.
Show me the answer
Buttons do not have an accessible name failed
This is the one. A button with no name is announced as "button" and nothing else, so somebody using a screen reader is asked to choose between three identical unmarked controls. It is usually an icon-only button — a basket, a search magnifier — needing nothing more than aria-label to fix.
The written version
What Google’s accessibility check found →
How to check your own site for this, what to change, and how to confirm it worked.
Now the real thing
Run this check on your own site.
The same check, plus twenty-nine others, against your actual pages. Free, no account, about a minute.