What can be proven, and what can't.

The target

This site aims to meet WCAG 2.2 at level AA.

It does not claim conformance. Conformance is a claim about all 86 success criteria, most of which no tool can decide, and no full manual audit of every one of them has been completed. Saying “WCAG 2.2 AA compliant” without that work is the exact habit pour exists to argue against, so this page won't do it either.

What the engine reports

Audited with pour engine against WCAG 2.2 level A and AA, on 16 August 2026. Page by page, because a single site-wide number would hide more than it tells you:

Every page also returns 55 success criteria that need a human. That number is not a failure either. It is the part of WCAG no automated tool can reach, on any site, including this one.

Run it yourself with the extension, the bookmarklet, or the command line. Expect your numbers to move: the counts above are taken while scrolled into the page, and at the very top of this page the engine returns nothing to review at all. That isn't flakiness. See below.

What goes to review, and why

“Needs review” does not mean “fails”. It means the engine found something it cannot honestly rule on and refused to guess. Here is every one of them on this site.

• The header, on every page: 6 elements

  The wordmark and the five navigation links. Once you scroll, the header becomes translucent and blurs whatever is passing beneath it, so there is no single backdrop colour to measure a ratio against. Scroll back to the top and the same six elements resolve cleanly and disappear from the report. A contrast result that depends on scroll position is exactly the kind of thing a tool should hand to a person rather than score.

• Home only: text over video, about 25 elements

  The home page sets text over moving footage and gradients, where there is no fixed background to compute against. Any tool reporting a clean pass there is reporting a number it did not compute. These are checked by eye, so if a combination reads poorly on your display, that is worth reporting.

• Home only: captions on five videos

  The crowd footage and the three sense demos are decorative: every one is muted, has no audio track, is aria-hidden, and is out of the tab order. There is no audio content to caption. The engine cannot confirm that from the DOM alone, so it abstains, correctly. There is no video on this page, which is why this one never appears here.

• Every page: focus obscured under the sticky header, up to 6 links

  WCAG 2.2's 2.4.11 Focus Not Obscured depends on scroll position and that same sticky header, a runtime condition rather than a fact about the markup. Verifying it by hand at every breakpoint is still outstanding.

What's been done

• Works without JavaScript

  The navigation is a plain link list until main.js upgrades it, so nothing essential depends on scripting.

• Keyboard throughout

  A skip link, a visible focus style, and no keyboard traps. Scrollable code samples are reachable and labelled as regions.

• Motion you control

  The background video is decorative and muted, it halts on its poster frame under prefers-reduced-motion, and there is a pause control regardless of your system setting.

• Typography

  Body text is set in Atkinson Hyperlegible, a typeface designed by the Braille Institute for low vision readers.

What this statement doesn't cover

This page is about the website. The extension and the bookmarklet share one interface, and it has not yet had a full independent audit. It's a complex application UI, and saying so is better than implying otherwise. If you use assistive technology and hit a wall in the audit panel, that report is more valuable than any feature request. The command line is plainer by nature: text out, severities named in words, colour never the only signal.

pour is in beta. This statement will change as the site and the tools do.

Report what's wrong here

If something on this site is inaccessible, or this statement overstates anything, email info@pour.dev. Include the page, what you were trying to do, and your browser and assistive technology if you know them. Every message is read, and replies aim to be within five working days.

Statement first published 3 August 2026 · last reviewed 16 August 2026.