How the audit works
Plain-language notes on what is tested, with which tools, and what the results do and do not prove.
What gets tested
Every site listed in my shared site list, from the main portfolio to each subdomain app. Once a week (Monday 06:00 UTC), and whenever I start it by hand, a GitHub Actions workflow visits each site's home page.
If a site does not answer (its address does not exist yet, it times out, or it returns an error status), it is markedNot deployed yet and skipped. Most apps are still being built, so this is expected and is not counted as a failure.
The tools
axe-core
axe-core, by Deque Systems, is an open-source rule engine that inspects a rendered page and reports problems such as missing text alternatives, low colour contrast or buttons without a name. It runs inside a real Chromium browser driven by Playwright (a browser automation library), at these settings:
- desktop: 1280 pixels wide
- mobile: 360 pixels wide
- colour schemes: light and dark mode
That makes four runs per site. A problem found in several runs is listed once, with the runs where it appeared. Rule sets used: wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa, best-practice.
Lighthouse
Lighthouse, by Google, loads the page in headless Chrome (a browser without a window) on an emulated phone and scores four categories from 0 to 100: performance, accessibility, best practices and SEO (search engine optimisation). The version is pinned tolighthouse@12 so scores stay comparable. 90 or more is good, 50 to 89 needs work, below 50 is poor.
WCAG levels, briefly
WCAG (Web Content Accessibility Guidelines) is the W3C standard for accessible websites. Version 2.2 is current. Each requirement, called a success criterion, has a number such as 1.4.3 and a level:
- Level A
- The basics. Without these, some people cannot use the page at all.
- Level AA
- The usual legal and industry target, and mine. Adds things like 4.5:1 text contrast, visible keyboard focus and touch targets of at least 24 by 24 pixels.
- Level AAA
- The strictest level. Not required for whole sites.
Some axe rules are best practices: good advice that is not a WCAG requirement. They count towards the total, but not towards the badge.
Impact and the badge
axe rates each problem as minor, moderate, serious or critical, based on how badly it blocks people. A site shows theWCAG 2.2 AA badge only when the latest audit found zero serious and zero critical problems in all four runs.
Automated tools catch only part of all accessibility problems. The badge means "no serious automated findings", not a full conformance claim. I also test by hand with a keyboard, a screen reader and 200% zoom.
Where the data lives
Each run saves one JSON file in the repository (apps/a11y/src/reports/<date>.json) and commits it, so the full history is public and diffable. This site is rebuilt from those files and has no tracking and no client-side JavaScript. The newest report is also at latest.json.
When a problem disappears between two audits, the site page lists it under "Fixed issues" with a link to the code changes between the two audited commits.