skills.rest
pacphi
pacphiCOMMUNITY
Explore all skills by this author →
𝕏@fastnsilverGitHub

accessibility-testing

Perform WCAG 2.2 accessibility testing on web applications with axe-core.

6|3|Updated Dec 3, 2025
Search Tags:#accessibility#a11y#wcag#keyboard#screen-reader
One-click install
npx skills add https://github.com/pacphi/ampel --skill accessibility-testing-pacphi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-testing
Source: https://github.com/pacphi/ampel/tree/main/.claude/skills/accessibility-testing
Command: npx skills add https://github.com/pacphi/ampel --skill accessibility-testing-pacphi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures products are accessible to all users by applying WCAG 2.2 criteria, keyboard navigation, and screen reader testing.

Core Features & Use Cases

  • Pour Principles: Perceivable, Operable, Understandable, Robust
  • Screen Reader Validation: Validate with VoiceOver, NVDA, JAWS
  • Automated & Manual: Axe-core automation with manual checks
  • RTL & Unicode: Accessibility checks across languages

Quick Start

npx playwright test --project=chromium tests/accessibility

Frequently Asked Questions about accessibility-testing

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

FAQPage Schema
How do I test web accessibility with WCAG 2.2 compliance?▼

WCAG 2.2 accessibility testing validates that web applications meet international accessibility standards. Use automated tools like axe-core combined with manual keyboard navigation and screen reader validation to check perceivable, operable, understandable, and robust design across features, forms, and navigation.

Can I automate accessibility testing in my CI/CD pipeline?▼

Yes. Axe-core automation integrates into continuous integration workflows to catch accessibility issues early. Run automated checks alongside manual screen reader validation with tools like VoiceOver, NVDA, and JAWS to ensure compliance gates before release.

What's the best way to validate keyboard navigation and screen reader support?▼

Keyboard navigation testing verifies operable interfaces without a mouse, while screen reader validation confirms content is announced correctly to assistive technology users. Test with VoiceOver on macOS, NVDA on Windows, and JAWS to cover diverse user environments and interaction patterns.

How do I check color contrast and accessibility across different languages?▼

Accessibility testing includes automated color-contrast verification to meet WCAG standards and manual checks across RTL and Unicode text to ensure perceivable, understandable content for international users on web and mobile interfaces.

Does accessibility testing apply to mobile web applications?▼

Yes. WCAG 2.2 accessibility testing applies to mobile web and native interfaces. Keyboard and screen reader validation, form accessibility, navigation structure, and color contrast checks ensure inclusive design across all device types and platform contexts.

Why should I perform manual accessibility checks beyond automated testing?▼

Automated tools catch structural issues but miss context-dependent problems. Manual keyboard navigation and screen reader testing validate real user experiences, confirm logical heading hierarchies, check focus management, and verify form labels—gaps automated checks cannot detect.

Related Skills

Explore More Design & Creative Skills→
emilneuraz-aiemilneuraz-ai

accessibility-compliance

Audit web interfaces for WCAG 2.2 compliance and apply ARIA patterns.

Community
Advanced
dreamingechoesdreamingechoes
2

accessibility-audit

Identify WCAG 2.2 AA compliance gaps through automated and manual audits.

Community
Advanced
AbhiRKeesaraAbhiRKeesara

accessibility-testing

Automates WCAG 2.1 accessibility checks in Playwright using axe-core.

Community
Intermediate
gsd-buildgsd-build
7.8k

accessibility

Audit web projects for WCAG 2.1 accessibility issues and generate remediation plans.

Official
Advanced