Enter a page address. We test it against common WCAG checks, such as colour contrast, alt text and form labels, and explain each problem in plain English. It takes about 30 seconds.
Whether text stands out enough from its background for people with poor eyesight to read it.
Whether images have a short description, so screen readers can say what they show.
Whether every box in a form says what it’s for, so screen readers and voice control can use it.
Whether every button and link has a name. Otherwise a screen reader just says “button”.
Signs we can spot automatically, such as controls that can’t be reached with the Tab key. A person still needs to try the page with a keyboard.
Automated tools, including this one, find only part of the problems WCAG covers. Some things need a person to judge: whether alt text is actually helpful, whether the page makes sense with a screen reader, and whether everything works with a keyboard alone.
So a clean result doesn’t mean your page meets WCAG or the law. It means none of the problems we can test for were found.
Around one in five people in the UK has a disability, and many more have poor eyesight, a shaky hand or a small screen. If they can’t read your text or fill in your form, they go to someone who makes it easy.
There’s a legal side too. In the UK, the Equality Act 2010 expects businesses to make reasonable adjustments for disabled people, and in the US, businesses have been taken to court over websites that can’t be used. Fixing the common problems is a good first step.
Each line is marked Passed, Worth fixing or Problem. Start with the problems: they are the ones most likely to cost you visitors or enquiries. The grade at the top (Good, Needs work or Poor) sums up the lines.
Each problem says where it is on the page. Contrast and alt text are usually quick fixes in your website builder; form labels may need your developer or a setting in your form plugin.
This checks one page. NetNav’s accessibility audit checks pages across your website, with a screenshot of each problem, and turns them into tasks with steps for your website platform.
The Web Content Accessibility Guidelines: the international standard for making websites usable by disabled people. Most guidance, and most laws that mention websites, point to WCAG 2.1 or 2.2 at level AA.
No. An automated check finds only part of the problems WCAG covers, and it checks one page. A clean result is a good sign, not proof. For full confidence, a person needs to test your site, ideally including people who use screen readers or a keyboard.
Not on its own. Overlays add a toolbar on top of your site, but the problems in the page itself, such as missing labels or low contrast, are still there. Fixing the page is what works.
The pages people need to contact or buy from you: your homepage, your contact or booking page, and your most visited service or product pages.
Yes. There’s no sign-up and no card. You can check as many pages as you like, within a fair-use limit.