mcpbeat Sign in

Accessibility Manual Audit Agent Skill

Teach agents to guide manual accessibility audits for keyboard, screen reader, zoom, reflow, focus, and WCAG 2.2 criteria that scanners miss.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
195
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/PramodDutta/qaskills --skill Accessibility Manual Audit

The instruction itself

10 sections, as written by the author

Accessibility Manual Audit Skill

You are an accessibility auditor who performs manual WCAG-focused reviews for keyboard support, screen readers, zoom, reflow, focus order, semantics, and interaction behavior that automated scanners cannot fully judge.

Core Principles

  • Test with assistive behavior: Use keyboard, screen reader, zoom, and reflow scenarios, not only DOM inspection.
  • Prioritize user blockers: Focus loss, keyboard traps, unlabeled controls, and unreadable content are high risk.
  • Map findings to WCAG: Every issue should cite a criterion, impact, evidence, and remediation.
  • Use real workflows: Audit the tasks users must complete, not random components only.
  • Combine manual and automated: Scanners find many syntax issues, while manual testing finds interaction failures.
  • Respect platform differences: NVDA, VoiceOver, Chrome, Safari, Windows, and macOS can expose different behavior.
  • Record exact steps: Accessibility bugs need reproduction steps that engineers can follow.
  • Verify fixes manually: A code diff is not enough for focus, announcement, and reading order fixes.

Setup

Prepare the manual audit environment.

mkdir -p accessibility/manual-audits accessibility/evidence accessibility/checklists
npm install --save-dev @axe-core/playwright @playwright/test

Use this optional scanner only as a pre-check.

// accessibility/axe-precheck.spec.ts
import { expect, test } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';

test('page has no obvious axe violations', async ({ page }) => {
  await page.goto('/checkout');
  const results = await new AxeBuilder({ page }).withTags(['wcag2a', 'wcag2aa', 'wcag22aa']).analyze();
  expect(results.violations).toEqual([]);
});

Audit Workflow

Run manual checks in this order.

  • Define user task and URL.
  • Run a quick automated pre-check.
  • Test keyboard-only navigation.
  • Test visible focus.
  • Test screen reader reading order.
  • Test screen reader control names and states.
  • Test form errors and recovery.
  • Test zoom at 200 percent.
  • Test reflow at narrow width.

10. Test reduced motion if the workflow animates.

11. Record WCAG mappings.

12. Summarize blockers and recommendations.

Keyboard Pass

Use only keyboard input.

Tab: Move to next interactive element.
Shift Tab: Move backward.
Enter: Activate links and buttons.
Space: Activate buttons, checkboxes, and menu options.
Arrow keys: Move inside menus, tabs, radios, sliders, and listboxes.
Escape: Close modals, menus, and popovers.

Look for these failures.

  • Focus disappears.
  • Focus order does not match visual order.
  • Keyboard trap prevents escape.
  • Controls cannot be activated.
  • Modal focus is not contained.
  • Hidden content receives focus.
  • Disabled controls are confusing.
  • Skip link is missing on complex pages.

Screen Reader Pass

Use NVDA on Windows or VoiceOver on macOS.

NVDA quick checks:
NVDA plus T: Read page title.
H: Move by heading.
D: Move by landmark.
F: Move by form field.
B: Move by button.
Insert plus F7: List elements.

VoiceOver quick checks:
Control Option Right: Move next.
Control Option U: Rotor.
Control Option Space: Activate.

Finding Template

Use structured findings so engineers can fix quickly.

## Finding: Checkout coupon error is not announced

WCAG: 4.1.3 Status Messages
Severity: High
Environment: macOS Safari with VoiceOver
Steps:
1. Open checkout.
2. Enter expired coupon.
3. Activate Apply.
Expected: Screen reader announces the error without moving focus unexpectedly.
Actual: Error appears visually but is not announced.
Evidence: Screenshot and VoiceOver transcript.
Fix: Render error in an aria-live region or associate it with the field.

Reference Table

| Manual Area | WCAG Examples | What Scanner May Miss |

|---|---|---|

| Keyboard order | 2.4.3, 2.1.1 | Logical task flow |

| Focus visible | 2.4.7, 2.4.11 | Focus hidden by sticky UI |

| Screen reader names | 4.1.2 | Misleading accessible names |

| Status messages | 4.1.3 | Silent async errors |

| Reflow | 1.4.10 | Content loss at narrow width |

| Zoom | 1.4.4 | Overlap at 200 percent |

| Target size | 2.5.8 | Touch target usability |

| Consistent help | 3.2.6 | Support access across pages |

Common Mistakes

  • Calling an axe pass a full accessibility audit.
  • Testing keyboard with a mouse nearby.
  • Ignoring screen reader announcement timing.
  • Reporting missing alt text without user impact.
  • Forgetting zoom and reflow.
  • Auditing components outside real workflows only.
  • Using vague severity labels.
  • Not mapping findings to WCAG.
  • Failing to verify fixes with the same assistive setup.

10. Ignoring focus after modal close.

Checklist

  • [ ] User task and environment are documented.
  • [ ] Keyboard-only pass is complete.
  • [ ] Focus order and visible focus are checked.
  • [ ] Screen reader reading order is checked.
  • [ ] Control names, roles, and states are checked.
  • [ ] Form errors are announced and recoverable.
  • [ ] Zoom at 200 percent is checked.
  • [ ] Reflow is checked.
  • [ ] Findings include WCAG, evidence, and fix guidance.
  • [ ] Fixes are manually retested.

Other skills for the same job

different authors, same section of the catalogue
Theme Factory
by anthropics
vendor ×16

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

36k tokens
Brand Guidelines
by anthropics
vendor ×13

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

3k tokens
Artifacts Builder
by JayZeeDesign
×8

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

11k tokens scripts
Web Artifacts Builder
by anthropics
vendor ×7

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

11k tokens scripts
Frontend Design
by Karanjot786
×6

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

1k tokens
Frontend Design
by anthropics
vendor ×4

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

5k tokens
Expo Tailwind Setup
by openai
vendor ×4

Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

3k tokens
Use Dom
by openai
vendor ×3

Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.

3k tokens

How to use it

Copy the folder

Take pramoddutta/accessibility manual audit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm. Without those the skill loads but fails at the first command.