Website accessibility check against WCAG
We open the page in a browser and check it against WCAG 2.2 rules: alternative text, contrast, form labels, headings, keyboard use and text resizing. You get a 0–100 score and a list of barriers, most serious first, each with its WCAG criterion and an instruction you can pass to your developer.
What exactly we check
- Alternative text for images, image buttons and image maps
- Text contrast against the background and links in body text that stand out from plain text
- Form field labels and button and link names for screen readers
- Page language, title, heading structure and landmarks
- Visible focus and keyboard access to elements, with no traps
- Text resizing to 200% and a layout on a narrow screen without sideways scrolling
- Correct use of ARIA attributes and element roles
We check one page in one state: as it looks when it opens. Dialogs opened with a click, further form steps, videos and PDF documents need a human review, as does whether alternative text describes the image well. The automated check points to the places; a person judges the meaning.
How to read the result
Score 0–100
Each problem takes away points depending on its severity and the number of elements it affects. Each severity has a cap: a hundred minor issues will not take away as much as one critical problem. The same formula scores your site in the panel once you sign up, so the check and the monitoring results can be compared.
Critical and serious
A critical problem can block some visitors completely: a button without a name, a form without labels, an image link without a description. A serious one makes the page so hard to use that people give up. Start with these.
Moderate and minor
Obstacles that can be worked around, and best practice recommendations. Fix them when you next change the template, because they usually affect many pages at once.
No problems found
The automated rules found nothing. That does not mean the page is accessible: automation covers part of the WCAG criteria and the rest needs a human review. With every result we state how many criteria the check covered.
Questions and answers
Is this check enough to meet legal requirements?
No. It is an automated check of one page that points to the most common barriers. Assessing compliance means checking all WCAG criteria, including those a person has to review, on a representative sample of pages.
How does the check work?
We open the page in a real browser and run the rules of axe-core, a widely used accessibility testing engine, plus our own tests of keyboard use, text resizing and narrow screens.
Does the check put load on my website?
It is one browser visit to one page, just like an ordinary visitor. We do not fill in forms or crawl other pages.
What happens to my email address?
We send the check report to it. We only send commercial information if you tick a separate consent box, which you can withdraw at any time. We keep the result and the address for 90 days.
Other tools
Is my website down
Check from the outside whether the site responds, and whether the problem is on your end.
SSL certificate
Expiry date, issuer, name coverage and everything else that makes the padlock disappear.
Domain expiry
When the domain expires, who the registrar is and whether anyone can move it without your knowledge.
SPF, DKIM and DMARC
Why your email lands in spam, and whether someone can send invoices from your address.
Security headers
Eight items you set on the server in a quarter of an hour, and every audit asks about them.
robots.txt analysis
One file can take the whole site out of Google while the server answers perfectly. Check what you let get indexed.