AI Blocks › Design things people love
Quarterly accessibility review
Give it your site each quarter. Get accessibility gaps ranked, last quarter's fixes checked and a statement kept current.
Quarterly accessibility review is a free AI agent for the job "Design things people love". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · Made by AI Blocks · Thinking: high
What it does
Accessibility work decays. A site is fixed once, then a redesign ships with a form nobody labelled, a brand refresh drops the button contrast under the line, and the statement on the footer describes a site that no longer exists. The next time anyone looks is when a customer or a buyer complains. This agent looks every quarter and after every redesign. It re-checks last quarter's fixes first, then checks the whole site and the pages that matter most. It ranks what to fix by whether it stops a real task, not just by which criterion it fails, and proposes at most ten fixes with where each goes in the code. It checks every colour pair when the palette changes and runs the Section 508 check when a government buyer asks. It keeps dated notes for your statement and never claims a conformance level. It changes nothing.
You give it
- Your site address and the pages where people buy, sign up, pay or get help
- Your code or templates, so fixes can be placed (advised)
- Your colour tokens or design direction (advised)
- What changed since last quarter (advised)
- Whether any buyer is a government body (optional)
- Codebase (optional)
- A design direction (optional)
- A buyer brief (optional)
You get
- Gaps by WCAG level, against last quarter
- At most ten fixes, task-blocking first, each with page, criterion and where it goes
- A verdict on each fix from last quarter, held or reopened
- Failing colour pairs and the closest passing colours
- Dated notes for your accessibility statement, with no over-claim
- A five-task human test to run with people who use assistive technology
Use it when
- You fixed accessibility once and are not sure it held.
- A redesign or brand refresh just shipped.
- A buyer or a regulator asked for your accessibility statement and you do not have a current one.
How to use it
- Start a chat with the agent. In Claude Code, add it as a skill or save it in .claude/agents, then ask it to run this quarter.
- Give it the site address and your key pages. Point it at the code and the colour tokens if you can.
- Say what changed since last quarter.
- Read the fix list. Make the changes you agree with, then tell the agent which were done.
- Run the human test with five users. Run the agent again next quarter; it re-checks what you fixed.