How we check your page

What happens after you paste an address

1. We confirm that the address points to a publicly available web page.
2. We open the content shown immediately, without logging in, buying anything or submitting forms.
3. We run 16 groups of checks, including buttons, images, forms, headings and the page language.
4. We order any findings by how much they may affect a visitor.
5. For free, we show the first issue, a first repair step, an example location when available and what still needs a manual check.
6. The result stays in your current browser tab. We do not save a history of checks.

What we check

We check whether the page has a title and declared language, whether images have the required attribute, whether buttons and links say what they do, and whether form fields are labelled. We also look at heading order, video captions, mobile zoom and settings that may confuse keyboard or screen-reader users. The mere presence of an attribute does not prove that its text is useful, so that still needs a manual review.

Why there is no 0–100 score

A single number can look like proof that the whole page is good even though a quick check sees only a small part. That is why we do not show a score such as 100/100. Instead, we state what we checked, what we found and what still needs a manual review.

If we do not find an obvious issue, that does not mean the whole page is accessible or barrier-free. It only means that the immediately loaded content did not contain one of the issues this version can detect.

What is not checked

• whether the whole page can be used with a keyboard alone;
• how the page actually works with a screen reader;
• whether image descriptions are useful rather than merely present;
• whether text, buttons and messages are readable in every state;
• what happens after a click, invalid entry or form submission;
• content that appears only after loading or a click;
• pages behind a login, the cart, payment and the complete purchase journey;
• whether a particular law applies to your organisation.

Standards and sources

We connect each finding with a relevant Web Content Accessibility Guidelines (WCAG) rule. The limitations of tools like this are also explained in the W3C WAI guidance. A final confirmation requires an expert manual review.

Security boundaries

We do not allow checks of private addresses, links containing credentials or pages that are not publicly available. We also limit the number of checks in a short period. Even so, you may check only your own page or a page for which the owner has given you permission.