The short version

Supervisor opens your pages in real browsers and runs several accessibility checkers on each one: axe-core, QualWeb, IBM Equal Access and Alfa. It adds its own checks that use the page the way a person would: moving through it with the Tab key, zooming to 200%, narrowing it to 320 px and widening the text spacing. An AI review by Claude (Anthropic) looks at page titles, link texts, headings, labels and image descriptions. Guidance for what only a person can judge comes from the Accessibility Considerations Toolkit, published by Microsoft under the MIT licence.

Supervisor is an independent service. It is not affiliated with these projects or the companies behind them. Automated checks find only part of accessibility problems.

Why several tools

No single checker finds everything it could, and each has its own blind spots and its own mistakes. What Supervisor adds is the combination:

  • It runs the tools together on every page, in a real browser, at a desktop and a mobile size.
  • It merges their findings, so the same problem on the same element is one issue, not four.
  • It keeps the list of issues from check to check and marks an issue fixed when a later check no longer finds it.
  • It decides which findings are sure enough to go into your accessibility statement and which wait for a person.

The tools

Tool Made by What Supervisor uses it for
axe-core Deque Systems The main rule set, on every page at both sizes
QualWeb University of Lisbon, Faculty of Sciences A second opinion from 15 chosen rules
IBM Equal Access IBM A second opinion from 3 chosen rules
Alfa Siteimprove Listing the elements a keyboard user can reach, for the visible focus check
Supervisor’s own browser checks Supervisor Tab key, zoom, reflow and text spacing
AI review by Claude Anthropic makes Claude Titles, link texts, headings, labels and image descriptions
Accessibility Considerations Toolkit Microsoft Guidance for what a person has to judge. Planned, not in the product yet

How a page is checked

  1. One browser opens the page at a desktop size (1366 by 768) and scrolls through it, so that content that loads late is there.
  2. axe-core runs, and Supervisor takes a screenshot of each failing element. Findings on hidden elements are dropped.
  3. If the AI review is on, the browser gathers the texts and small image crops it needs.
  4. QualWeb and IBM Equal Access run. Their findings are kept only for elements that no earlier tool reported for the same WCAG criterion.
  5. The visible focus check and Supervisor’s own browser checks run. They come last because they press keys and resize the page.
  6. The page is set to a mobile size (402 by 678), and axe-core, QualWeb and IBM Equal Access run again.

The checkers run in a part of the browser that the page’s own scripts cannot reach, so a page cannot change its own result.

When a check follows a journey instead of crawling, only axe-core runs, at both sizes, after each step. The other checks focus elements and resize the page, which would disturb the journey.

What reaches your statement

Not every finding is equally sure. Supervisor measures each tool against a set of test pages with known problems, and uses the results to sort the findings.

  • Published as found. axe-core findings for most WCAG criteria, and six QualWeb rules, are open issues at once and count in the statement.
  • Waiting for a person. Findings for nine WCAG criteria wait as “needs review” whichever tool found them: 1.1.1, 1.3.1, 1.4.10, 2.4.4, 2.4.7, 2.5.1, 3.3.1, 3.3.2 and 4.1.2. So do all findings from IBM Equal Access, the other QualWeb rules, Supervisor’s own browser checks and the AI review.
  • Decided by you. A person, or your agent with your say, confirms each of those or marks it as a false positive. That decision sticks in later checks.

What no tool here can tell you

  • Whether a site meets the requirements. A check with no findings is not proof of that.
  • Whether a real task can be finished with a keyboard or a screen reader from start to end.
  • Whether captions and transcripts exist and are right, whether instructions are understandable, and whether error messages help.
  • Anything on pages the check did not reach. A crawl does not sign in or fill forms. Journeys cover those pages.

These need a person. Problems found by hand are recorded with add_accessibility_issue and are tracked beside the automated ones.

Versions

The check result names the tools and versions that ran, in its engine line, so the versions are not repeated here.