What changed in the product, newest first. Only what is live — anything still being built is on the pages that describe it, marked as such.
September 2026
Checks and scoring
- All 55 WCAG 2.2 A and AA success criteria. The catalogue the product scores against now holds every A and AA criterion; the six that were missing (1.2.4, 2.5.4, 3.2.3, 3.2.4, 3.3.3, 3.3.4) are tracked like the others, as untested until somebody records a result.
- Best practice is not a WCAG failure. Rules that axe-core classes as best practice — landmarks, heading order, one main landmark, a first-level heading — are still reported, but no longer counted as failures of WCAG 1.3.1. They weigh less in the score, which is now version 2 of the formula (how we test).
- Bypass blocks (2.4.1) is partly automated, not fully. Nothing automatic can decide it either way; the skip-link check is evidence, not a verdict.
- PDF documents. Linked PDFs on your own site are now opened and checked for tags, language, title, a displayed title and alternative text on figures. It is a subset of PDF/UA; the report says what is not checked.
- Pages that are not really pages. Redirects to other sites, error pages and pages the checks could not read are marked as not scored instead of scoring 100.
- Missing page titles are found (WCAG 2.4.2).
- Fewer false misspellings. Words are no longer joined across elements, and your own brand and domain are not flagged.
- Faster crawls, and a login for a protected site is never sent to another host, even when a link redirects there.
Reports and compliance
- EN 301 549, clause by clause. A view of chapter 9 of EN 301 549 V3.2.1 with each clause's status, and the clause number in reports and CSV exports, with links to the matching BITV-Test steps.
- Accessibility statements for public bodies. The statement editor now writes both the BFSG accessibility information for businesses and the public-sector accessibility statement with feedback contact and enforcement procedure.
- White-label reports and client workspaces for agencies on Growth and Enterprise: a client's name, logo and colour on its reports, and colleagues who see only that client's sites.
Working with issues
- Every occurrence, not only the first: the issue drawer lists each element with its page and markup.
- Tickets. An issue opens a prefilled ticket form in GitHub, GitLab or Jira and keeps the link you paste back. Nothing is synced.
- "More about this rule" now leads to our own rule reference instead of a third-party site.
- One definition per number. Issues, occurrences and pages mean the same thing on every screen, and times are shown in your time zone.
Free tools
- Free website checker at its new address.
- Colour contrast checker, including non-text and link contrast and the nearest passing colour.