pour
What it is
pour is a web accessibility tool for checking pages against WCAG 2.2. It lists page-level scanning and provides several ways to access its tools: a browser extension, bookmarklet, command-line scanner and VS Code extension. A contrast checker is also included. The tool lists CI/CD integration, which can connect accessibility scanning with a development workflow. Its listed platforms are web and iOS, and the described scan scope is an individual page. The Free plan costs nothing, requires no account and has no subscription; no paid tiers are listed. These terms let readers use the listed tools without signing up for an account or choosing a subscription. The available formats cover browser, command line and code editor use, alongside the iOS platform. For readers choosing an accessibility checker, pour's listed focus is page-level scanning, with a contrast checker and CI/CD integration among the included options. Its plan information does not describe broader scan scope or additional pricing tiers.
For and against
For
- Checks pages against WCAG 2.2.
- Includes a contrast checker.
- Offers browser, command-line and VS Code tools.
- Lists CI/CD integration.
- Free plan requires no account or subscription.
Against
- Listed scan scope is limited to a page.
- No broader scan scope is described.
The verdict
pour combines page-level accessibility scanning with a contrast checker and several ways to access its tools. The free plan has no account requirement or subscription, while the listed scan scope is page-level.
Who it suits
pour suits people who want to check individual pages against WCAG 2.2. Its browser, command-line and VS Code options may suit different development workflows.
Plans and prices
Free
All tools · no accounts · no subscriptions · no paid tiers
Read 11 Oct 2026 · pour.dev
On the record
- AI integration
- The CLI supports the Model Context Protocol and can provide an AI agent with an audit, keyboard focus order, and screenshot.pour.dev · read 11 Oct 2026
- Browser audits
- The browser extension audits the current page, groups findings by severity, and provides affected markup and repair guidance.pour.dev · read 11 Oct 2026
- Browser extension
- Yespour.dev · read 21 Sep 2026
- CI/CD integration
- Yespour.dev · read 21 Sep 2026
- Command line
- The CLI runs audits in headless Chrome, can act as a CI gate, take simulation screenshots, and crawl sites to create standalone HTML reports.pour.dev · read 11 Oct 2026
- Coverage limit
- The engine assists with 51 of WCAG 2.2's 86 success criteria, and the audit includes a manual-review checklist because automated tools cannot fully test WCAG criteria.pour.dev · read 11 Oct 2026
- Editor support
- The VS Code extension checks HTML, React, Vue, Svelte, Angular, Liquid, and Nunjucks source files as you type.pour.dev · read 11 Oct 2026
- Engine package
- The pour accessibility engine can be installed directly in projects with npm install pour-engine.pour.dev · read 11 Oct 2026
- Integrations
- The browser extension works with Chrome, Edge, and Firefox, and audit results can be exported as Markdown, CSV, or JSON.pour.dev · read 11 Oct 2026
- iOS support
- On iPhone and iPad, the Safari share sheet can run the pour bookmarklet as a shortcut.pour.dev · read 11 Oct 2026
- Privacy
- Pour's tools run locally and transmit no audit results, analytics, telemetry, account data, or crash reports.pour.dev · read 11 Oct 2026
- Purpose
- Pour provides tools to find website accessibility issues and explain how to fix them.pour.dev · read 11 Oct 2026
- Quest app
- The Meta Quest app supports Quest 3 and 3S, runs simulations over the headset view, and uses no network or microphone permission.pour.dev · read 11 Oct 2026
- Scan scope
- pagepour.dev · read 21 Sep 2026
- Simulations
- Pour includes more than 55 accessibility simulations and lenses, including vision effects, keyboard tab order, and page structure.pour.dev · read 11 Oct 2026
- Support
- Security vulnerability reports can be emailed to [email protected], with replies aimed for within five working days; the page says there is no bounty programme.pour.dev · read 11 Oct 2026
- Trust and verification
- The engine source is public on GitHub, and the security page says extension releases are published on GitHub for inspection.pour.dev · read 11 Oct 2026
- WCAG version
- wcag 2.2pour.dev · read 21 Sep 2026
The review
Pour is a free accessibility toolkit for people who need to inspect web pages, source code, or sites in a CI workflow. Its strength is the range of ways it supports an audit, from severity-ranked browser findings to simulations and command-line reports.
Overview
Pour helps identify website accessibility issues and gives repair guidance. Its browser extension audits the page currently open, groups findings by severity, and shows affected markup. A manual-review checklist acknowledges a central constraint: automated tools cannot verify every WCAG criterion.
The engine assists with 51 of WCAG 2.2's 86 success criteria. That makes Pour useful for finding issues and guiding follow-up, but an automated pass cannot stand in for a full accessibility review. The page-level scan scope also suits inspecting individual pages more directly than it does assessing an entire site in one browser audit.
Key features
More than 55 simulations and lenses let users examine vision effects, keyboard tab order, and page structure. These views add ways to explore how a page behaves and is perceived; they complement the findings rather than replacing manual review.
The CLI runs audits in headless Chrome, can serve as a CI gate, capture simulation screenshots, and crawl sites to produce standalone HTML reports. This makes Pour relevant to developers who want checks in an automated workflow as well as reports they can review outside the command line. Through the Model Context Protocol, the CLI can also give an AI agent an audit, keyboard focus order, and a screenshot.
The VS Code extension checks HTML, React, Vue, Svelte, Angular, Liquid, and Nunjucks files as they are edited. Teams can also install the accessibility engine in a project with npm install pour-engine. Browser audit results export as Markdown, CSV, or JSON, which gives users several formats for sharing or processing findings.
On iPhone and iPad, users can run the Pour bookmarklet from Safari's share sheet. A separate Meta Quest app supports Quest 3 and 3S, running simulations over the headset view without network or microphone permission.
Pour's tools run locally and transmit no audit results, analytics, telemetry, account data, or crash reports. The engine source is public on GitHub, and extension releases are published there for inspection. Security vulnerability reports can be emailed to [email protected]; replies are aimed for within five working days, and there is no bounty programme.
Pricing
Free — free. The plan includes all tools, requires no account, and has no subscription or paid tiers. With no trial period to manage and no paid upgrade, Pour is an unusually accessible option for individuals and teams wanting to add accessibility checks without a software charge. The trade-off is scope: the engine covers 51 of 86 WCAG 2.2 success criteria, and users still need manual review.
Platforms
Pour supports API, browser extension, iOS, Linux, macOS, web, and Windows. Its browser extension works with Chrome, Edge, and Firefox, while the CLI supports headless Chrome and CI/CD integration. The VS Code extension and installable engine package give developers additional ways to use it within their editing and build workflows.
Who it's for
Pour suits developers, accessibility practitioners, and teams who want no-cost tools for page audits, source checks, simulations, or CI workflows. Its local operation will also appeal to users who want audit data to stay on their machines. It is less suited to anyone expecting automated scans alone to establish full WCAG conformance, or seeking a page-level browser scan to cover an entire site without using the CLI's crawl capability.
Pros and cons
- Pros: Every tool is free, with no account or subscription, so there is little friction in adopting it.
- Pros: Browser audits show severity, affected markup, and repair guidance, making findings more actionable than a bare issue list.
- Pros: CLI, CI gate, crawl reports, editor checks, simulations, and AI-agent support serve a broad range of development workflows.
- Pros: Local operation and no transmission of audit results or telemetry give users a clear privacy advantage.
- Cons: Automated assistance covers 51 of WCAG 2.2's 86 success criteria, so a manual-review step remains necessary.
- Cons: The browser extension audits the current page; broader site crawling requires using the CLI.
Alternatives
Choose WAVE if a freemium accessibility checker with browser extensions and an API is a better fit. Its listed subscription API starts at $10 a month, with a 250-credit minimum purchase.
IBM Equal Access Accessibility Checker is another free option, with browser extensions and CI/CD and automated testing packages.
For organizations seeking a paid service with tailored quotes based on site and goals, consider Siteimprove Accessibility. Welcoming Web offers a free core accessibility widget and a Pro plan from $19/m; Evinced, Assistiv Labs, Stark, and Binclusive are also options to compare.
Browse more tools in Accessibility Testing Software and Website Accessibility Tools.
Verdict
Pour is an easy recommendation for developers and accessibility teams who want a capable, no-cost toolkit spanning browser, editor, CLI, and CI workflows. Its combination of simulations, actionable findings, and local processing is compelling. Look elsewhere if you need automated coverage of all WCAG criteria or expect an automated scan to replace manual assessment.