Hire an AI accessibility auditor

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A list of barriers, each with the WCAG rule, severity, who it affects, location and fix
• A result for each rule in scope, either pass, fail, not tested or not applicable
• A plain verdict of does not conform, not determined or conforms, with what was left untested
• A keyboard test checklist and a screen reader test script for your key flows
• A fix order, with the quick wins marked

How it does the job well

• Never claim a screen reader said something, or that a flow works with one, unless the user tested it and pasted what happened.
• Never write that a page is accessible or conforms from a scan or a code read alone.
• Do not invent a WCAG rule number or wording. If unsure, write CHECK: and name the document to look up.
• This is an audit aid, not a legal certificate or advice. Rules differ by country and by who you are. Send the user to a qualified auditor or counsel for those.
• Do not edit, publish or send anything. Hand over the report for the user to act on.
• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You are about to launch a site, app or feature and want an accessibility check first.

• Scope. The pages, flows, standard and tools, plus what was assumed or missing.
• Results by rule. Pass, fail, not tested or not applicable for each WCAG rule in scope, with evidence.
• Findings. Each barrier with rule, severity, who it affects, location, current code, fix and how to verify.
• Verdict. Does not conform, not determined or conforms, and the scope left untested.
• Tests to run. A keyboard checklist, a screen reader script, and zoom and motion checks for your flows.
• Fix order. Items to fix now, next and later, plus the patterns worth keeping.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Set the scope. It lists the pages, flows and page states in scope, the standard and level, and what is out of scope.
• Plan the automated pass. It lists the scanner checks to run on each page, and notes that a scan covers only the rules a tool can test.
• Plan the manual tests. It writes a keyboard test, a screen reader test, a zoom and reflow test, and a reduced motion and contrast test.
• Review components. It looks at custom parts such as tabs, menus, pop-ups and forms for correct roles, keys and announcements.
• Write the findings. Each gets a WCAG rule by number and name, a severity, who it affects, the evidence, the current and fixed code, and how to verify.
• Give the verdict. It gives a result for each rule and a verdict, and lists what was not tested.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id testing-accessibility-auditor only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/testing-accessibility-auditor/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The pages or flows in scope, such as "sign up and check out", as a link, HTML or screenshots
• The level you are aiming for, such as WCAG 2.2 AA (it assumes this if you do not say)
• The tools you can use, such as a scanner, a screen reader or just a keyboard
• Your tech stack, such as React or plain HTML (optional)
• Barriers users have already reported (optional)

Helpful context (optional)

• The scan report for each page.
• A short list of the tasks users must finish.
• Your design system or component list, if you have one.

Tools and access

• axe, Lighthouse or WAVE: These free scanners find the barriers a tool can detect. Paste their output so the agent can sort it.
• NVDA, VoiceOver or JAWS: A screen reader is how you confirm what the AI can only predict. NVDA is free on Windows and VoiceOver is built into Mac and iPhone.
• Claude Code or another AI that can open your project: It can read your real components and suggest fixes in place. In a plain chat you paste the code.

Functions and deliverables

• Accessibility auditor: Audit a web page or app for accessibility barriers. Get findings tied to WCAG 2.2, a test plan for keyboard and screen readers, and a fix list.
  • A list of barriers, each with the WCAG rule, severity, who it affects, location and fix
  • A result for each rule in scope, either pass, fail, not tested or not applicable
  • A plain verdict of does not conform, not determined or conforms, with what was left untested
  • A keyboard test checklist and a screen reader test script for your key flows
  • A fix order, with the quick wins marked
  Source: Michael Sitarzewski and Agency Agents contributors.
• WCAG accessibility reviewer: Share site code or pages and target WCAG level. It checks selected issues and suggests fixes; retest results depend on tools and manual review.
  • A list of issues by severity
  • Before and after code fixes
  • A re-check after the fixes
  • A report for managers
  • A pipeline check to stop new issues
  Source: Alireza Rezvani.
• Web accessibility checker: Check a web page or code for WCAG 2.2 accessibility problems. Get a ranked list with where each one is, and fixes if you ask.
  • A ranked list of WCAG 2.2 problems
  • The place in the page or code for each
  • Fixes applied and re-checked, if you asked
  • A note on what automated checks cannot cover
  Source: sickn33.
• Accessibility standards checker: Check your site against WCAG accessibility rules. Give it your page code or screenshots. You get gaps by level, ranked fixes and draft statement notes. Not legal advice.
  • A gap table with status for each criterion
  • Fixes ranked by priority
  • Annotated code with corrections
  • Draft notes for an accessibility statement
  • A map from rules to laws
  Source: Hemant Naik.
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.

Tasks you can use it for

• You are about to launch a site, app or feature and want an accessibility check first.
• A customer, school or partner asks for proof that your product is accessible.
• A scan came back clean, but a user says they could not use a form or menu.
• You built a custom tab, menu or pop-up, and want to know if it works for screen reader and keyboard users.

Limits to check before starting

• You are a U.S. government body or contractor and need a Section 508 report. Use the Section 508 accessibility reviewer.
• You need a legal certificate of conformance. Only a qualified auditor can give one.
• You want the page fixed and rebuilt. Take the findings to the Frontend developer, or fix them yourself in your code.
• You want a general quality check of how a site looks and works. Use the Visual QA evidence collector.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. Or paste SKILL.md into a new chat, then paste references/source-agent.md after it.
• List the pages and flows in scope, say the level you are aiming for, and paste the code or screenshots. Say which tools you have. A chat AI cannot open your site, so paste what it should check.
• Read the plan. Run the scanner if it lists one, then the keyboard test. Use a screen reader for the key flows, such as NVDA on Windows or VoiceOver on Mac.
• Paste your results into the chat, one flow at a time. Ask the agent to update the findings and the verdict.
• Fix the critical and serious items in your code first. Run the same tests again to prove each fix.
• Keep the final report with your release notes. Plan a re-check after big changes.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/testing-accessibility-auditor for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.