skills.rest
tsuji-tomonori
tsuji-tomonoriCOMMUNITY
Explore all skills by this author →
GitHub

a11y-testing-manual

Standardize manual accessibility testing for WCAG 2.2 AA compliance.

1|Updated Feb 11, 2026
Search Tags:#accessibility#a11y#screen reader#keyboard navigation#manual testing#wcag
One-click install
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill a11y-testing-manual
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-testing-manual
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/a11y-testing-manual
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill a11y-testing-manual

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes manual accessibility testing to ensure WCAG 2.2 AA compliance, catching issues that automated tests miss, especially concerning keyboard navigation, screen reader output, and mobile usability.

Core Features & Use Cases

  • Standardized Manual Testing: Provides a checklist for keyboard, screen reader, zoom, and mobile testing.
  • WCAG 2.2 AA Focus: Targets critical accessibility standards often missed by automated tools.
  • Use Case: Before releasing a new feature, use this Skill to perform a thorough manual accessibility audit on the key user flows, ensuring a high-quality, inclusive user experience.

Quick Start

Use the a11y-testing-manual skill to perform a manual accessibility audit on the user registration flow.

Frequently Asked Questions about a11y-testing-manual

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

FAQPage Schema
How do I perform manual accessibility testing for WCAG 2.2 AA compliance?▼

Manual accessibility testing for WCAG 2.2 AA compliance requires systematically checking keyboard navigation, screen reader output, zoom functionality, and mobile touch targets against a standardized checklist to catch issues automated tools miss.

What issues does manual accessibility testing catch that automated tests miss?▼

Manual accessibility testing catches critical issues in focus management, reading order, keyboard-only operation, and screen reader output quality that automated testing tools often overlook in web applications.

How do I test keyboard navigation and screen reader compatibility?▼

Testing keyboard navigation and screen reader compatibility involves verifying keyboard-only operation completeness and evaluating screen reader output quality using a standardized manual checklist to ensure proper focus management and reading order.

Does manual accessibility testing cover mobile interactions and zoom functionality?▼

Manual accessibility testing covers mobile interactions by verifying touch target sizing and operational completeness, while also validating zoom functionality to ensure web applications meet WCAG 2.2 AA standards across all interaction modes.

When do I need manual accessibility testing for web applications?▼

You need manual accessibility testing before releasing a new feature or flow to perform a thorough manual audit, ensuring a high-quality, inclusive user experience that automated tools alone cannot guarantee.

What are the limitations of automated tools for WCAG 2.2 AA compliance?▼

Automated tools for WCAG 2.2 AA compliance cannot evaluate subjective screen reader output quality, keyboard navigation flow, or mobile usability nuances, requiring standardized manual testing to address these operational completeness gaps.

Related Skills

Explore More Software Engineering Skills→
keshavraj936keshavraj936

webapp-testing

Automate web application testing with Playwright end-to-end scenarios and accessibility checks.

Community
Advanced
KaakatiKaakati
2

accessibility-auditor

Audit web content against WCAG 2.2 AA standards with automated checks.

Community
Advanced
VanhPokerVanhPoker

accessibility-expert

Identify and fix WCAG 2.1/2.2 accessibility violations in web interfaces.

Community
Advanced
sigmadigitalzasigmadigitalza
1

frontend-accessibility-review

Audit web frontends for WCAG 2.2 AA conformance with static and live checks.

Official
Advanced