Most accessibility statements are written once, on launch day, and quietly rot. They say a site "is committed to accessibility," name a standard, and never mention a single thing that's actually wrong — which tells a guest nothing about whether they'll be able to use the site today.

We've rebuilt the accessibility page on every Remi site to do the opposite: publish what our testing actually finds, and update itself every night.

What's on the page now

  • A conformance status you can check. The site states its standard — WCAG 2.2 Level AA — and describes itself as partially conformant: built to meet that standard, with no independent audit of every success criterion completed. It's the honest claim, and it's the one that leaves room for what testing misses.
  • How the site is tested. Automated scanning with axe-core against the live site every night, plus a hand walk-through before launch — keyboard only, and every page checked in the standard, high-contrast, and dark display modes.
  • What testing can't settle. Automated checks catch only part of what can block someone. They can't judge whether a photo's description is useful, whether a reading order makes sense, or whether a booking flow works end to end with a screen reader. The page says so.
  • Known issues, in plain English. Whatever the most recent scan found, listed by what it means for a guest — not a rule ID — with the date it was found.
  • Where to report what we missed. The restaurant's own contact details, plus a route to the Remi team if a report goes unanswered.

Why publish the defects

Because the alternative is worse. A statement that claims a clean site and gets contradicted by the first guest who hits a barrier has spent its credibility. A statement that lists what's outstanding, dated, next to the scan that found it, is a record of an active program — and it turns a guest's report into an input instead of an ambush.

It also keeps us honest. The page is generated from the scan results, so we can't quietly leave something off the list.

How it stays current

The nightly scan writes to the site's record, and the page renders from the most recent result. Fix something and the entry disappears on the next scan. Break something and it appears. Nobody has to remember to update a page — which is exactly why hand-written statements go stale.

Every Remi site has this page, linked in the footer, from the day it goes live.

What it found on day one

Publishing your own test results is only worth something if you act on them. Building this out meant testing the platform properly for the first time in one pass — including our own admin dashboard, which restaurant staff use every day and which no guest ever sees.

That turned up seven real conformance failures in the dashboard, all now fixed: menu categories and items could only be reordered by dragging, with no keyboard or button alternative; a category could only be selected by clicking; a set of form fields had visible labels that were never programmatically connected to their inputs; some icon controls were too small to hit reliably and carried no proper name; and two text colours sat below the contrast minimum.

None of that was visible on a restaurant's public site. All of it mattered to the person running one.