wcag22aa-scope

Defines WCAG 2.2 AA scope, success criteria mapping, and Definition of Done for web applications.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill wcag22aa-scope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wcag22aa-scope
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/wcag22aa-scope
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill wcag22aa-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes the definition of WCAG 2.2 AA scope and acceptance criteria (DoD) for consistent accessibility implementation across development, testing, and operations.

Core Features & Use Cases

  • Scope Definition: Clearly outlines what parts of a product/feature are in scope for accessibility compliance.
  • Criteria Mapping: Maps WCAG 2.2 A and AA success criteria to specific features and user flows.
  • Definition of Done (DoD): Establishes clear, actionable acceptance criteria for implementation and verification.
  • Use Case: When launching a new user authentication flow, use this Skill to define which WCAG criteria apply, how they will be tested (e.g., keyboard navigation, screen reader compatibility), and what constitutes a "done" and compliant implementation.

Quick Start

Use the wcag22aa-scope skill to define the scope and DoD for the new user registration feature.

Frequently Asked Questions about wcag22aa-scope

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

FAQPage Schema
How do I define WCAG 2.2 AA scope for a new web application launch?

Defining WCAG 2.2 AA scope involves mapping specific A and AA success criteria to user flows. This Skill standardizes that scope and acceptance criteria, ensuring consistent accessibility compliance across product, design, and engineering teams.

What should be included in a Definition of Done for web accessibility compliance?

A web accessibility Definition of Done requires clear, actionable acceptance criteria for implementation and verification. It specifies how features are tested, such as keyboard navigation and screen reader compatibility, ensuring a compliant implementation.

How do I map WCAG 2.2 success criteria to specific user flows like authentication?

Mapping WCAG 2.2 success criteria to authentication flows requires identifying applicable A and AA rules. This Skill maps those criteria to specific features, defining how to test integrations and what constitutes a compliant user flow.

Can I use WCAG AA scope definitions for major refactors in cloud-native app development?

WCAG AA scope definitions apply to major refactors in cloud-native app development. This Skill addresses specific cloud-native challenges, ensuring accessibility consistency across SaaS integration, authentication, and CI/CD pipelines.

When do I need to establish accessibility acceptance criteria for my product?

Accessibility acceptance criteria are needed when launching new products or features and during major refactors. Establishing a standardized Definition of Done ensures consistent implementation, testing, and operational compliance across teams.