skills.rest
yono92
yono92COMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility-testing

Automate web accessibility testing against WCAG standards with axe-core, Playwright, and Jest.

Updated Oct 7, 2024
Search Tags:#testing#accessibility#a11y#wcag#playwright#axe-core
One-click install
npx skills add https://github.com/yono92/KeyWork --skill accessibility-testing-yono92
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-testing
Source: https://github.com/yono92/KeyWork/tree/main/.agents/skills/accessibility-testing
Command: npx skills add https://github.com/yono92/KeyWork --skill accessibility-testing-yono92

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @axe-core/playwright, jest-axe, cypress-axe, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures web applications are usable by people with disabilities, validating compliance with WCAG and identifying barriers to accessibility.

Core Features & Use Cases

  • WCAG Compliance: Validate adherence to WCAG 2.1/2.2 standards.
  • Keyboard Navigation: Test full usability via keyboard only.
  • Screen Reader Compatibility: Verify content is understandable by screen readers.
  • Use Case: Before launching a new feature, run this Skill to automatically scan the page for common accessibility violations, ensuring it meets AA standards and is usable by everyone.

Quick Start

Run the accessibility testing skill to scan the current page for WCAG A and AA violations.

Frequently Asked Questions about accessibility-testing

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

FAQPage Schema
How do I automate web accessibility testing against WCAG standards?▼

Automate web accessibility testing by scanning pages for WCAG A and AA violations using axe-core with Playwright, validating keyboard navigation, screen reader compatibility, ARIA attributes, and color contrast.

What does keyboard navigation testing involve for screen reader compatibility?▼

Keyboard navigation testing verifies full page usability via keyboard only, ensuring screen readers can understand content by validating ARIA attributes and proper focus management against WCAG standards.

Can I use axe-core with Jest and Cypress for a11y testing?▼

Yes, you can integrate axe-core with Jest using jest-axe and with Cypress using cypress-axe to automate accessibility scans and validate WCAG compliance across your web application testing pipelines.

What's the best way to check WCAG 2.1 AA compliance before launching a feature?▼

The best way to check WCAG 2.1 AA compliance is running an automated accessibility scan to detect keyboard navigation barriers, screen reader issues, ARIA misuse, and color contrast failures before launch.

Does automated accessibility testing catch all WCAG violations?▼

Automated accessibility testing focuses on common WCAG violations like ARIA attributes and color contrast, ensuring baseline compliance and usability, but manual testing remains necessary for complex screen reader interactions.

Related Skills

Explore More Software Engineering Skills→
WesleySmitsWesleySmits
6

implementing-e2e-testing

Standardize Playwright and Cypress end-to-end test patterns.

Community
Advanced
joe-watkinsjoe-watkins
1

a11y-tester

Run axe-core accessibility tests on web pages via Playwright MCP.

Community
Advanced
samymitysamymity
1

browser-qa

Automate end-to-end browser QA for web applications with smoke, interaction, visual regression, and accessibility checks.

Community
Intermediate
HouseofmvpsHouseofmvps
115

a11y

Detect and fix deterministic WCAG 2.2 A/AA accessibility violations in HTML files.

Community
Advanced