web-a11y-testing

Validates web accessibility through automated scans, keyboard walkthroughs, and screen reader smoke tests.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/pedropenha/project-skills --skill web-a11y-testing-pedropenha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-a11y-testing
Source: https://github.com/pedropenha/project-skills/tree/main/.agents/skills/web-a11y-testing
Command: npx skills add https://github.com/pedropenha/project-skills --skill web-a11y-testing-pedropenha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a web UI is accessible requires many manual checks across keyboard navigation, screen readers, and user preference modes, and regressions are easy to miss. This Skill provides a structured, repeatable testing workflow with checklists and reporting guidance so accessibility verification is consistent and traceable. ## Core Features & Use Cases - Ordered Test Workflow: Runs automated scans first, then keyboard-only journeys, screen reader smoke passes, and zoom/reflow/reduced-motion/forced-colors checks. - Reusable Smoke Checks: A companion CHECKS.md file provides repeatable keyboard, screen reader, and preference-mode smoke steps. - Structured Regression Reporting: Produces reports covering scope, tools, pass/fail results, reproduction steps, and residual risk. - Use Case: After shipping a new checkout form, run this Skill to confirm every control is keyboard-reachable, errors are announced to screen readers, and the flow remains usable at 200 percent zoom. ## Quick Start Use the web-a11y-testing skill to verify the accessibility of the updated checkout page and report any failures with reproduction steps.

Frequently Asked Questions about web-a11y-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test web accessibility for a new UI page?▼

Run an automated scan on the changed surface first, then perform a keyboard-only journey, a screen reader smoke pass, and preference-mode checks like zoom and reduced motion. This Skill defines that exact test order with a checklist for each stage.

How to do a keyboard accessibility smoke test?▼

Reach every interactive control with Tab and Shift+Tab, activate controls with Enter or Space where expected, and confirm visible focus is always present. The Skill's CHECKS.md file lists these keyboard smoke steps for repeatable execution.

What should a screen reader smoke test cover?▼

Verify the page title, landmarks, and heading map, then check role, name, and state on critical controls. Trigger dynamic updates such as dialogs, validation, and pagination, and confirm announcements are meaningful without stale or duplicate output.

Does accessibility testing cover zoom and reduced motion preferences?▼

Yes, the workflow includes zoom and reflow at 200 percent for key flows, reduced motion mode for animated interactions, and forced-colors or high-contrast checks for form controls and focus rings.

What should an accessibility regression report include?▼

Include the scope tested, tools used, pass/fail results, reproduction steps for each failure, and residual risk. This structure keeps findings actionable for developers fixing the issues.