Check web pages for accessibility problems
WCAG 2.2 AA problems on each page, with the element, the rule and a fix, the blockers first.
- You start it: When you start it
What it does
The task
Open each page in this list: urls. Check it against WCAG 2.2 level AA: images without alt text, low color contrast, form fields without labels, the heading order, and link text such as 'click here'. Use each page with the keyboard only, and note where the focus is lost or hidden. Write a report in a new Google Doc with one row per problem: the page, the element, the WCAG rule, the impact and a fix. Put the problems that stop a user from finishing a task first.
- It works in any website and Google Docs, in the workspace you pick, and signs in with passwords from your Cuiar vault.
- It runs once, when you start it.
What you give it
| Blank | What to give | Example |
|---|---|---|
| urls | The pages to check, one per line or separated by commas | https://brightleaf.app/signup, https://brightleaf.app/checkout, https://brightleaf.app/pricing |
What you get back
An example run with the example values above. Your run uses your own data.
3 pages checked: 14 problems, 3 stop a task
| Page | Element | Rule | Fix |
|---|---|---|---|
| /signup | E-mail field with no label | 1.3.1, 3.3.2 | Add a label element for the field |
| /checkout | Card form: the focus is lost after the expiry field | 2.4.3 | Fix the tab order in the card form |
| /signup | Submit button, contrast 2.9:1 | 1.4.3 | Use #1F5FBF on white (5.6:1) |
| /pricing | 6 links with the text "Learn more" | 2.4.4 | Name the plan in each link |
... 10 more
Report saved as "Accessibility check, 4 Nov".
Run it in Cuiar
- 01
Open it
Click Use in Cuiar on this page. The side panel opens with the task in the composer.
- 02
Fill in the blank
Type urls. Tab moves to the next blank.
- 03
Run it
Run sends it to the agent. Follow each step in the panel, and stop it at any time.
From the terminal
cuiar exec "Open each page in this list: https://brightleaf.app/signup, https://brightleaf.app/checkout, https://brightleaf.app/pricing. Check it against WCAG 2.2 level AA: images without alt text, low color contrast, form fields without labels, the heading order, and link text such as 'click here'. Use each page with the keyboard only, and note where the focus is lost or hidden. Write a report in a new Google Doc with one row per problem: the page, the element, the WCAG rule, the impact and a fix. Put the problems that stop a user from finishing a task first."Run it from your AI agent
Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call run_task yourself.
1. Add Cuiar to Claude Code
claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp2. Ask your agent
Use the Cuiar tool run_task to run my "Check web pages for accessibility problems" template with urls = https://brightleaf.app/signup, https://brightleaf.app/checkout, https://brightleaf.app/pricing.Setup for other agents: AI agents.
The tool call
{
"name": "run_task",
"arguments": {
"task": "Open each page in this list: https://brightleaf.app/signup, https://brightleaf.app/checkout, https://brightleaf.app/pricing. Check it against WCAG 2.2 level AA: images without alt text, low color contrast, form fields without labels, the heading order, and link text such as 'click here'. Use each page with the keyboard only, and note where the focus is lost or hidden. Write a report in a new Google Doc with one row per problem: the page, the element, the WCAG rule, the impact and a fix. Put the problems that stop a user from finishing a task first."
}
}Related templates
All engineering templatesEngineering
Follow your quickstart guide and report where it breaks
Each step of your guide tried in the product, with the steps that are wrong, unclear or out of date.
You start it: When you start it- Any website
- Google Docs
Engineering
Compare staging with production before a release
Text, layout and console differences page by page, with the ones that look like bugs marked.
You start it: When you start it- Any website
- Google Docs
Engineering
Check your pages at phone, tablet and desktop sizes
Layout problems at each screen width, with a screenshot and the element that breaks.
You start it: When you start it- Any website
- Google Docs
Engineering
Write an incident postmortem from the timeline
A blameless draft with the timeline, impact, cause and actions, built from chat, monitors and deploys.
You start it: When you start it- SSlack
- Datadog
- GitHub
- +1 more: Google Docs
ResearchOdyssey
Research a topic into a cited report
Many sources, compared, in one report with a citation for each claim.
You start it: When you start it- Google Scholar
- Wikipedia
- Google Docs
ResearchOdyssey
Write a literature review on a research question
Recent studies grouped by theme, what they agree on, where the evidence is weak, and a full reference list.
You start it: When you start it- Google Scholar
- Semantic Scholar
- PubMed
- +1 more: Google Docs