pour

Accessibility checks while you write code. The same engine as the pour browser extension, inside your editor.

What it does

• Checks your markup against WCAG 2.2 as you type.
• Puts each problem on the tag that caused it. Hover it, or open the Problems panel, to see what is wrong and how to fix it.
• Shows how serious each problem is with the pour mark next to the line number: red is critical, yellow is serious, then moderate and minor, and blue means "have a look".

Works with

• HTML files
• React (.jsx, .tsx)
• Vue (.vue)
• Svelte (.svelte)
• Angular templates (.component.html)
• Liquid (.liquid) and Nunjucks (.njk), as Eleventy uses them. An .html file that carries template tags is checked as a template too.

What it checks

Things it can see in the code: missing alt text, inputs without labels, buttons and links with no name, wrong ARIA, broken lists and tables, heading order, page title and language, and more. Run "pour: what pour checks" for the full list.

What it cannot check

• Anything that needs the page on screen: colour contrast, tap target size, focus, motion. For those, run pour in your browser on the real page.
• Anything a script builds. Scripts do not run here.
• In React, Vue, Svelte, Angular, Liquid and Nunjucks files, values that come from code, like alt={name} or alt="{{ alt }}". Those elements are skipped, and the status bar tells you how many. An include or a block can render anything, so the element around it is skipped as well, and in a layout the page-level checks that read that part of the page are skipped.

For the agents in your editor

• In chat: an agent can run this check on any file through the pour_check_file tool. Mention it as #pourCheck. It gets every finding with its line, the rule, the severity and the fix.
• In the browser: with the pour command line tool installed (npm install -g pour-cli), the extension registers pour's browser tools as an MCP server named pour. An agent can then audit a running page, trace its keyboard focus order and take screenshots through the vision and sensory simulations. Set pour: Mcp Command if the tool lives somewhere unusual.

Settings

• Best practices: also check heading order, landmarks and redundant ARIA. Off by default.
• Check while typing: on by default.
• Read linked CSS: skips elements the CSS hides. Nothing is fetched from the internet.
• Mcp Command: the pour command line tool that provides the browser tools. Empty turns them off.

Nothing leaves your machine.