Every check, and how to fix it
One page each, in the same words the tool uses. If a scan showed you a finding, this is where the next question is answered.
| Check | Severity | In one line |
|---|---|---|
| Image without alt text | error | Screen readers announce the file name or nothing at all, so the image carries no information for a blind visit |
| Link with no accessible name | error | A link that contains only an icon or empty markup is announced as "link" with nothing else, so nobod |
| Button with no accessible name | error | A button with no label cannot be used with a screen reader or by voice control. |
| Form field without a label | error | The field is announced without saying what to type, which makes forms impossible to complete reliably without |
| Heading levels skip | warning | Screen reader users navigate by headings; jumping from h1 to h4 breaks the outline of the page. |
| Headings start below h1 | warning | This page has headings but no h1, so the outline starts halfway down: a visitor using a screen reader hears a |
| Empty heading | warning | An empty heading is announced as a heading with no text, which is confusing noise. |
| Page language is not declared | error | Without <html lang="..."> a screen reader may read the page in the wrong language, which sound |
| Table without header cells | warning | Without th cells, a screen reader cannot say which column or row a number belongs to. |
| Embedded frame without a title | error | Frames are announced by their title; without one the visitor hears "frame" and cannot tell what is e |
| Positive tabindex | error | A positive tabindex reorders the whole page for keyboard users and usually makes some controls unreachable. |
| Link text does not say where it goes | warning | Screen reader users often browse a list of links out of context, where "click here" means nothing. |
| Page has no title | error | The document title is the first thing announced and the label of the browser tab. |
| Duplicate id attributes | warning | An id must be unique. |
| Zoom is blocked | warning | Blocking pinch zoom or limiting maximum-scale makes the page unusable for people with low vision. |
| Focusable element hidden from screen readers | error | An element that can receive keyboard focus but is aria-hidden creates a focus stop that announces nothing. |
| Label points at an id that does not exist | error | aria-labelledby and label for point at an id. |
| Link opens a new window without warning | warning | A new tab is disorienting for people who cannot see that it happened, and the back button no longer behaves as |
| Media plays automatically | warning | Sound that starts on its own is one of the most disruptive failures, and it fights with a screen reader. |
| Alt text looks like a file name | warning | A screen reader will read "IMG 2481 dot jay peg" aloud. |
| Alt text says nothing useful | warning | Words like "image", "photo" or "logo" are announced before the description anywa |
| Link built out of JavaScript | error | href="javascript:..." cannot be opened in a new tab, copied, or reliably activated with a keyboard, |
| Interactive element inside another one | error | A link or button inside a link or button produces an unpredictable target for keyboard and screen reader users |
| Image button has no alt text | error | An <input type="image"> is a button. |
| Obsolete scrolling element | warning | marquee and blink cannot be paused, and moving content must be controllable. |
We also publish our coverage of the W3C ACT Rules, including the rules we do not implement, and what no automated checker can see.