Pour Get Pour

A non-profit initiative · WCAG 2.2

Make the web work for everyone.

One in six people experience the web differently than you think. Pour shows you what's getting in the way, and exactly how to fix it.

Add to Chrome Add to Edge

Launching soon on the Chrome Web Store and Edge Add-ons. A non-profit tool: payment never required.

Placeholder loop. Real product footage lands with launch.

  1. Built on the spec

    Pour Engine is clean-room: every rule comes from reading WCAG 2.2, never from copying what other tools do.

  2. Lives in DevTools

    Audit the page you're building, where you're building it. Findings point at the element and show the line to write instead.

  3. Honest coverage

    61 rules automate what a tool can see. A scoped human checklist covers the rest. Nothing silently skipped.

1.0 · What a screen reader finds

Hear the difference a few lines make.

  • graphic.
  • image.
  • link. link. link. link.
  • button.
  • edit text, blank.

Missing alt text, unnamed buttons, unlabeled fields: small gaps with a loud result. The image-alt, link-name, button-name, and form-label rules point at each one and show the line to write instead.

2.0 · The four principles

Four promises, straight from the spec.

WCAG 2.2 organizes all 86 of its success criteria under four principles: Perceivable, Operable, Understandable, and Robust. Their first letters spell POUR. It's where Pour gets its name, and it's how the whole suite is organized. Read the principles from your user's side and they're promises:

  1. “I can perceive it.”

    Text I can read, images that speak, video I can follow, whatever senses I bring.

    Perceivable · 29 criteria

  2. “I can operate it.”

    Everything works with my keyboard, my switch, and my voice, with targets big enough to hit.

    Operable · 34 criteria

  3. “I understand it.”

    Fields say what they want, errors say how to recover, nothing shifts under my feet.

    Understandable · 21 criteria

  4. “My tech works with it.”

    My screen reader, browser, and settings all get the truth from your markup.

    Robust · 2 criteria

3.0 · Pour DevTools

Understanding lives where you already work: DevTools.

Audit any page as you build it. The full report sits in a DevTools panel, a summary in the toolbar popup. Results are stored per tab and stay live in both.

Per-element findings
The offending markup, why it matters to real users, how to fix it, and a link to the rule's documentation.
Show me
One press scrolls the element into view and flashes it on the page.
Re-run diffs
Audit again after a fix and see exactly what improved and what's new.
WCAG your way
Version and level selection, 2.2 by default. Best-practice rules are opt-in, including checks for accessibility that should be removed.
  • ChromeAwaiting store review
  • EdgeAwaiting store review
  • FirefoxComing soon

No mock-ups here. Real product footage is coming with launch.

86 success criteria in WCAG 2.2

61 automated rules in Pour Engine

65 criteria that still need a human. We hand you the checklist

4.0 · Pour Engine

Honest about what a tool can see.

No automated tool can test most of WCAG. This one included. Pour Engine 1.1.0 is a clean-room engine built directly on the spec: its rules cover 21 of the 86 criteria, every finding explains itself in plain language, and for the other 65 criteria each audit ships a manual-review checklist scoped to your chosen version and level. Nothing silently skipped, nothing borrowed, and when a judgment call comes up it's settled by reading the spec, not by copying what other tools do.

5.0 · For organizations

The right thing is now also the required thing.

Accessible sites were always better sites. As of 2026 they're also what the law expects. No fear-marketing needed, just the dates:

RegulationWhoWhere it stands
European Accessibility Act Companies serving EU consumers In force since 28 June 2025; enforcement has begun, with per-country penalties
ADA Title II (US) State & local government services WCAG 2.1 AA required by 26 April 2027 (larger entities) / 2028 (smaller)
WCAG 2.2 The standard the laws point at The current W3C recommendation, and exactly what Pour tests

The WebAIM Million finds detectable WCAG failures on roughly 95% of the world's top homepages, year after year. Mostly alt text, contrast, and labels: your team can fix those this sprint.

Non-profit, by design.

Every tool is free to use: no subscriptions, no paid tiers, no sales calls, ever. Donations are welcome; payment never is.