Skip to content

jaktestowac/awesome-copilot-for-testers / plugins/auditing-accessibility/skills/auditing-accessibility

auditing-accessibility

Verified

Performs webpage and user-flow accessibility audits with WCAG 2.2 guidance, manual verification checklists, prioritized remediation output, and stakeholder-ready summaries. Use when auditing accessibility on a URL, triaging suspected a11y issues, or producing technical findings with practical next steps.

resources/manual-a11y-checklist.md

View on GitHub
# Manual Accessibility Checklist

Use this checklist for triage, retest, or when automated tools cannot confirm a finding.

## Structure and semantics

- [ ] Page has a meaningful title
- [ ] One clear main heading exists
- [ ] Landmarks such as header, nav, main, and footer are present where appropriate
- [ ] Interactive elements have accessible names
- [ ] Form inputs have labels or equivalent accessible names

## Keyboard and focus

- [ ] Every interactive element is reachable by keyboard
- [ ] Focus order follows the visual and logical flow
- [ ] Focus is clearly visible
- [ ] No keyboard trap appears in dialogs, menus, or widgets
- [ ] Escape or equivalent closes dismissible overlays when expected

## Forms and feedback

- [ ] Required fields are identified clearly
- [ ] Error messages are visible and understandable
- [ ] Error state is announced or associated programmatically
- [ ] Success and status messages are discoverable

## Visual accessibility

- [ ] Text remains usable at zoom
- [ ] No critical content disappears at 200% to 400% zoom
- [ ] Contrast looks sufficient for text, icons, and focus rings
- [ ] Meaning is not conveyed by color alone
- [ ] Motion does not block use or overwhelm the interface

## WCAG 2.2 spot checks

- [ ] Focus is not hidden behind sticky UI
- [ ] Touch targets look large enough to use comfortably
- [ ] Dragging interactions have an easier alternative when needed
- [ ] Authentication does not rely on memory puzzles or complex cognitive steps

## Retest notes

- [ ] Findings verified after the fix
- [ ] Residual risk documented
- [ ] Anything still requiring assistive-technology testing is listed explicitly
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall