Fix guides
Clear, practical walkthroughs for the WCAG failures our scanner finds most often. Each one explains the success criterion, shows before-and-after code, and tells you how we detect it.
-
WCAG 1.4.3 · color-contrast
How to fix color-contrast issues
Low-contrast text is the single most common automated accessibility failure. Here is the exact contrast ratio you need and how to reach it.
Read guide -
WCAG 1.1.1 · image-alt
How to fix missing image alt text
A missing alt attribute means a screen-reader user gets nothing — or hears a filename. Here is how to write alternatives that actually help.
Read guide -
WCAG 2.4.4 · link-name
How to fix empty links
A link a screen reader announces as just "link" is a dead end. Here are the five reliable ways to give every link an accessible name.
Read guide -
WCAG 4.1.2 · button-name
How to fix buttons with no accessible name
A hamburger icon a screen reader reads as only "button" is a locked door. Here are four reliable ways to give every button an accessible name.
Read guide -
WCAG 1.3.1 · label
How to fix form inputs without labels
The most common form mistake is treating grey placeholder text as a label. Here is why that fails and how to associate a real label with every control.
Read guide -
WCAG 1.3.1 · heading-order
How to fix skipped heading levels
Screen-reader users navigate by heading level, so a skipped or faked heading breaks the page outline. Here is how to build a hierarchy that actually nests.
Read guide -
WCAG 3.1.1 · html-has-lang
How to fix a missing or wrong lang attribute
Without a lang attribute a screen reader reads your page in the wrong accent, turning content into noise. Here is the one-line fix and how to get the tag right.
Read guide -
WCAG 2.4.2 · document-title
How to fix a missing or generic page title
The <title> is the first thing a screen reader announces and the label on every browser tab. Here is a formula for titles that actually help people.
Read guide