People who use screen readers
Software reads the page aloud. It needs alt text, form labels, link text that makes sense alone, and a clear heading outline.
Paste your page’s HTML. FairWeb AI checks text contrast, image descriptions, form labels and keyboard access, explains every problem in plain language, and hands you a report with fixes you can copy.
Runs entirely in your browser. Your code is never uploaded.
Paste the HTML of a page or component, or upload an .html file. To check a live site, open it, view the page source, and copy everything.
Full pages get page-level checks too (language, title, zoom). Snippets are checked as a fragment.
Pick a text color and a background color. See the ratio against the WCAG levels, and get the closest text color that passes.
–
Large text sample, 24px
Body text sample. The five boxing wizards jump quickly, and every one of them can read this.
Small print sample, 14px
Software reads the page aloud. It needs alt text, form labels, link text that makes sense alone, and a clear heading outline.
This includes people with motor impairments and anyone with a broken wrist or trackpad. Everything must be reachable with Tab, and the focus must be visible.
They need strong contrast, text that scales when zoomed, and meaning that isn’t carried by color alone.
Phone in bright sunlight, noisy train, one hand full. Accessible design is just design that holds up in real life.
The web only works if people can use it. Most accessibility tools are written for specialists. FairWeb AI is written for the developer who has never heard of WCAG and still wants to do the right thing.
Every problem comes with the same four answers: what is wrong, who it affects, how to fix it, and what it sounds like to a screen reader.
Automated checks find some barriers, not all. Use this as a fast first pass, then test with a keyboard and a screen reader.