Guide · Accessibility check

Website accessibility check: what automated tests find, and what they miss

An automated check is a good place to start: it's free, takes seconds and finds common code problems. But it sees only part of the picture. Here's what it finds, what it misses, and how to cover the rest with a short manual check.

General information, not legal advice. I wrote this guide from the text of the law and regulations as I checked it on 14 November 2026. Legislation changes. For your own business, ask a lawyer.

In short

  • Automated checks find problems visible in the code: an image without alt text, a field without a label, a button without a name.
  • They can't tell whether the alt text is right, whether the site really works with a keyboard, or whether the content is clear.
  • In a UK government test, 10 automated tools together found 71% of 143 barriers deliberately placed on a test page, and the best single tool found 41%.
  • So a high score is a good sign, not proof that a site is accessible or compliant.

What automated checks find

Automated tools are good at problems that show up in the code itself. For example:

  • Images without alt text.
  • Form fields without labels, and buttons or links without a name a screen reader can announce.
  • A page with no language or no title.
  • Blocked pinch-zoom on mobile.
  • Skipped heading levels, and pages with no main heading.
  • Misused ARIA, duplicate ids, and iframes without a title.
  • Low colour contrast, where the tool can compute the colours.

What they can't know

Much of the guidance needs human judgement. The introduction to IS 5568 part 1 says applying the guidelines "requires a large degree of human judgement". The W3C, which writes WCAG, says evaluation tools can't determine accessibility, they can only assist. Things an automated check doesn't know:

  • Whether alt text actually describes the image. "image1.jpg" passes some checks but helps nobody.
  • Whether the whole site works with a keyboard: opening a menu, closing a popup, picking a date, paying.
  • Whether the focus order makes sense, and whether you can always see where focus is.
  • How the site sounds in a screen reader, and whether form errors are clear and announced.
  • Whether videos have captions and whether they are accurate.
  • Whether PDFs on the site are accessible. IS 5568 part 2 covers documents.
  • Whether the content is written clearly.

In a 2017 test by the UK Government Digital Service (GDS) accessibility team, the team built a page with 143 deliberate accessibility failures and ran 10 automated tools on it. The best tool found 41% of the failures, and all tools together found 71%. Even ten tools combined missed almost a third.

What my checker checks, exactly

I built the free checker to give business owners a fast, plain-language starting point. I want it to be clear what it does and doesn't do:

  • It checks one page: the address you enter.
  • It reads the HTML as the server sends it. Content built by JavaScript after the page loads isn't checked, and on such sites it says the result is partial.
  • Colour contrast is checked only where colours are written directly in the page code, not when they come from CSS files.
  • The score counts only WCAG A and AA checks, weighted by severity. Extra recommendations (best practice and AAA) are shown separately and don't affect it.
  • It says whether it found a link to an accessibility statement, and whether a known accessibility widget is installed.
  • Some sites block automated checks from my server, for example with bot protection. Those can't be checked from here, and the checker says so.

The free check shows a score and the most serious issues, with a plain explanation of each. The full report (US$29 per site, one-time) lists every issue found with examples from the page, how to fix each with example code, and an accessibility statement draft in Hebrew and English.

A short manual check anyone can do

After the automated check, these are the manual checks worth doing first. They need no coding knowledge. Start with the home page and the page that matters most to your business, such as a contact form or checkout.

  1. Keyboard. Put the mouse aside and move through the page with Tab, Shift+Tab, Enter and the arrow keys. Can you reach every link and button? Can you always see where you are? Can you open and close the menu and popups, and submit a form?
  2. Zoom. Zoom the browser to 200% (Ctrl and + on Windows, Cmd and + on Mac). Is the text still readable, with nothing cut off or missing?
  3. Screen reader. NVDA is free for Windows, and VoiceOver is built into Mac and iPhone. Listen to the headings, images and form fields. Does it make sense?
  4. Images. Read the alt text of the important images. Does it describe what the image conveys?
  5. Forms. Submit a form with a deliberate mistake. Is it clear what's wrong and how to fix it?
  6. Video and documents. Do videos have captions? Do important PDFs open as text, not as a scanned image? (The captions duty in regulation 35D applies to public authorities and to those with average turnover above ₪5 million, but captions help everyone.)

When a professional audit makes sense

If the site is large, has purchases, sign-up or important forms, or you received a complaint about accessibility, get a full manual audit by an accessibility expert, ideally including users with disabilities. An automated check helps you clear the basic fixes first, so the professional audit can focus on what only a person can check.

Start with a free check

Paste an address and within seconds you get a score and a plain explanation of the most serious issues on the page. No sign-up.

Automated checks find only part of accessibility issues. This is not a compliance certificate and not legal advice.