OpenForAllScan free
ENDE
Scan free

Our own accessibility

We run our own scanner on ourselves.

Selling an accessibility tool with an inaccessible product would be absurd, so we test ourselves. This page is a written-up snapshot of our last full self-test — including the things we know are still wrong.

Last self-test · 2 September 202694.2 / 10041 pages · WCAG 2.2 AA · automated rules

This is a written snapshot, not a live number. We update it by hand after each full self-test — so treat the date above as part of the figure.

Pages tested
41
Known issues open
4
Critical findings
0
External audit
None yet

How we test — two layers, both of them cheap

This is the whole routine. If you are looking for something you could copy into your own team next week without a budget, it is this.

Every deploy · automatedThe build refuses to ship a regression

A build is checked against 26 desktop and mobile views. A new WCAG A or AA failure, or a page that overflows sideways, stops the release. It catches roughly a third of real problems — but that third never comes back.

Every release · by handSomeone walks it with the mouse unplugged

Then again with a screen reader, and once at 200% zoom. Twenty minutes per release, and it finds what a machine structurally cannot: focus order, wording, and whether the thing actually makes sense.

Independent review

Everything here is our own testing. No third party has checked it.

We have not commissioned an independent expert review. When we do, the report and the reviewer will be named on this page.

What that means for the figures above

WCAG 2.2 AA is the target we test against, not a conformance claim someone else has verified. "Partially conformant" is the accurate status and the one we use in writing.

If you are weighing up the same decision

Automated checks plus a disciplined manual pass cost very little and cover a lot of ground. A formal audit is what you commission when a contract or a regulator asks for verified conformance — the two answer different questions.

What we know is still wrong

As of the last self-test on 2 September 2026. Published because we want to be transparent. Trust our evidence, not blind promises.

  • Exported PDF reports are not tagged for screen readersThe report inside the app is accessible; the PDF version is a visual document only. If you need the content non-visually, use the app view or the CSV export — both carry the same findings.Being worked on
  • The findings table needs sideways scrolling on very narrow screensBelow roughly 380px the table scrolls in two directions at once, which is awkward with magnification. We are rebuilding the row as a stacked card.Being worked on
  • A score change is shown as a colour and an arrowThe number is read out correctly, but the direction of travel is currently visual only. The accessible name needs the word "up" or "down" in it.Queued
  • The scheduling date picker is fiddly with a keyboard aloneArrow keys move day by day, but jumping a month needs the mouse. Typing the date into the field works today and is the reliable route.Queued

What this page is not

Not a conformance claim

WCAG 2.2 AA is the target we test against. Partially conformant is the honest status, and it stays that way until someone independent says otherwise.

Not a live feed

The figures above come from a self-test run on a stated date and are written up by hand. If the date looks old, ask us — that is a fair thing to hold us to.

Not a complete picture

Automated rules cover about a third of WCAG. Our manual pass covers the main journeys, not every screen. Barriers we have not found still exist — which is why the next section matters more than this one.

Feedback

Something here stopped you? That is a bug, and it jumps the queue.

No account needed. Tell us the page, what you were trying to do, and what you were using — screen reader, keyboard only, magnification, voice. Please leave out passwords and anything private.

What happens then

  1. Within two working days a person replies — not a ticket number.
  2. If there is a way around it, we send you that first, before the fix.
  3. Confirmed barriers are added to the list above at the next update, whether or not you are a customer.
  4. You get told when it ships.

Formal details

Down here rather than in the hero, because it matters to two readers — a procurement officer and a regulator — and to nobody else.

Applies to
openforall.io and app.openforall.io
Target standard
WCAG 2.2 level AA
Status
Partially conformant · 4 known issues
Method
Self-assessment · automated and manual · no external audit
Last self-test
2 September 2026