Accessibility scoreboard
Every demo site, scanned in every toolbar mode.
We say every Remi site is built and tested to WCAG 2.2 AA. This page is the “show your work” half of that sentence: automated axe-core scans of every demo restaurant site we publish, run against the live pages in the default design and in each accessibility-toolbar mode — dark, high contrast, larger text, and calm colors. On July 18, 2026, 175 individual page scans found 32 violations of the WCAG 2.2 A/AA rules axe checks for.
The results
Scanned July 18, 2026 with axe-core 4.11.2, rule set WCAG 2.2 AA. Each site’s key pages — home, menu (for sites that have one), and booking — were scanned once per toolbar mode. “0” means axe found no violations of the rules it checks, on that page, in that mode.
| Demo site | Pages scanned | Modes tested | Violations found |
|---|---|---|---|
| Volta (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 0 violations |
| Liza Roeckl (opens the live demo site in a new tab) | 2 (home, book) | 5 (10 scans) | 0 violations |
| Nori (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 0 violations |
| Chez Laurent (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 0 violations |
| The Copper Hen (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 14 violations |
| Benny's (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 0 violations |
| Eleven Fifty Five (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 0 violations |
| Lumen (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 18 violations |
| Ostra (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 0 violations |
| Brasa (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 0 violations |
| Fleur (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 0 violations |
| Koji (opens the live demo site in a new tab) | 3 (home, menu, book) | 5 (15 scans) | 0 violations |
12 sites · 175 page scans · default, dark mode, high contrast, larger text, calm colors
What an automated scan does — and doesn’t — tell you
Automated tools like axe-core check the machine-checkable slice of WCAG: missing alt text, empty link and button names, contrast ratios, landmark and heading structure, form labels, ARIA misuse. That slice matters — it’s where most restaurant sites fail — but it is a slice. Widely cited research puts automated coverage at roughly a third of WCAG success criteria.
A “0” above means axe found no violations of the rules it checks, on those pages, in those modes, on that date. It does not mean a page could never have an accessibility problem — no scan can promise that. Things automation can’t judge — whether alt text actually describes the photo, whether a flow makes sense announced aloud, whether focus order feels right — we cover with manual testing: keyboard-only walkthroughs, VoiceOver and NVDA, and 200% zoom checks. How we test lists the full routine.
How these numbers are produced
- Same scanner, same rules. The scan runs axe-core 4.11.2 — the same engine behind our prospect site scanner — restricted to the WCAG 2.2 A/AA rule tags (wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa).
- Real pages, real browser. Each run loads the live site in headless Chrome — no mocks, no cached HTML.
- Toolbar modes applied the way a visitor applies them. Before each page load, the scanner seeds the same
localStoragepreference the accessibility toolbar saves, so the site’s own boot code turns the mode on. The scan then records the resultingdata-a11y-*attributes as proof the mode was live while axe ran. - Nothing edited by hand. The table above is rendered straight from
data/scoreboard.json, written byscripts/scoreboard-scan.mjs. Re-running the script re-scans every site and rewrites the file.