Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

pour review

Free#75 of 129 in Website Accessibility ToolsAccessibility Testing Software

A broad free toolkit for local accessibility audits, simulations, source checks, and CI workflows.

3.0/10Editor score
pour3.0 Visit pour.dev

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

pour is a free, open-source accessibility toolkit for developers, designers, auditors, content editors, and others who build or review websites. Its browser extension audits live pages against WCAG 2.2, identifies affected elements, explains issues, and suggests fixes. The product also includes a bookmarklet, an iOS Safari shortcut, a command-line tool, a VS Code extension, contrast checking, and vision, sensory, and motor simulations. Audits run locally in the browser, with results remaining on the user’s device.

The main strength is breadth across review stages. Chrome, Edge, and Firefox extensions support live-page checks, while the bookmarklet can audit pages without installation. Keyboard tab-order and landmarks inspection, contrast checks, and simulations add manual-review context beyond automated findings. For development workflows, command-line audits include CI exit codes, site crawling, standalone HTML reports, and Markdown, CSV, and JSON exports. VS Code source-code checks and npm support extend the tool into editing and build environments.

All tools are free, with no account required, no subscriptions, and no paid tiers. That makes pour a practical fit for teams and individuals who want local audits without a purchasing process. Its primary one-click workflow focuses on individual pages, even though the command-line tool supports site crawling. It also does not provide a public scan API or scheduled scans, so organizations seeking centralized automation or recurring monitoring should choose a tool built around those capabilities instead. Pick pour for flexible browser, source, and CI checks; look elsewhere when API-driven or scheduled scanning is central.

pour pros and cons

  • Where it wins
    • WCAG 2.2 audits with element findings, explanations, and suggested fixes
    • Browser, bookmarklet, command-line, VS Code, and iOS Safari workflows
    • Simulations, crawling, CI exit codes, reports, and multiple export formats
  • Where it doesn't
    • No public scan API for connecting external systems
    • No scheduled scanning for recurring accessibility checks
    • The primary one-click workflow audits individual pages

pour fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update