Fix guides
Accessibility errors, explained in plain English
Scanner reports use technical wording. Each guide below takes one error, says what it means for real visitors, and shows the exact fix.
These are the problems that appear again and again. In the WebAIM Million 2026 report, 95.9% of the top one million home pages had at least one detectable WCAG failure, and a small set of error types made up most of them. Fixing these first removes most of the risk.
Low-contrast text
Reported as: “Elements must meet minimum color contrast ratio thresholds”
Light text on a light background fails WCAG. See the contrast ratios you need, how to measure them, and how to fix gray text without a redesign.
Images with no alt text
Reported as: “Images must have alternative text”
How to fix the 'images must have alternative text' error: what good alt text looks like, when to leave it empty, and where to add it in WordPress and Shopify.
Links with no text
Reported as: “Links must have discernible text”
An empty link is announced as just 'link' by screen readers. Find icon-only and image-only links and give each a clear name, with copy-paste code.
Buttons with no label
Reported as: “Buttons must have discernible text”
Icon buttons like the menu, close and search buttons often have no name for screen readers. Here is how to find them and fix each one with a single attribute.
Form fields with no label
Reported as: “Form elements must have labels”
Placeholder text is not a label. Learn how to connect a real label to every form field so contact, booking and checkout forms work for screen reader users.
Page language not set
Reported as: “<html> element must have a lang attribute”
Tell browsers and screen readers what language your page is in. A one-line fix for the html-has-lang error, with the correct language codes.
Page has no title
Reported as: “Documents must have <title> element to aid in navigation”
Every page needs a clear, unique title. See how to write page titles that help screen reader users and search results, and how to add them on common platforms.
Pinch-to-zoom blocked
Reported as: “Zooming and scaling must not be disabled”
A viewport setting can stop visitors from pinch-zooming on a phone. Here is the one-line fix for the meta-viewport error and why it matters.
Headings skip levels
Reported as: “Heading levels should only increase by one”
Jumping from an H2 straight to an H4 confuses people who navigate by headings. Learn how to fix heading order without changing how your page looks.
Page has no main heading
Reported as: “Page should contain a level-one heading”
Every page should have one H1 that says what the page is about. Here is why it matters for screen readers and how to add one without changing your design.
Embedded frames with no title
Reported as: “Frames must have an accessible name”
YouTube videos and Google Maps embeds need a title so screen readers can say what they contain. Here is the one-attribute fix for the frame-title error.
No main content area
Reported as: “Document should have one main landmark”
Wrap your page's primary content in a main element so screen reader users can skip straight past the menu. A short guide to landmarks, with code.
Links only distinguished by color
Reported as: “Links must be distinguishable without relying on color”
If links inside a paragraph differ only by color, color-blind visitors may miss them. Learn the simple underline fix for the link-in-text-block error.
Videos with no captions
Reported as: “<video> elements must have captions”
Videos need captions for deaf and hard-of-hearing visitors, and for people watching with the sound off. See how to add captions in HTML and on YouTube or Vimeo.
Buttons and links too small to tap
Reported as: “All touch targets must be 24px large, or leave sufficient space”
WCAG 2.2 asks tap targets to be at least 24 by 24 pixels, or spaced apart. Learn the exceptions and how to fix tiny icons, close buttons and crowded links.