web-accessibility

Define accessibility acceptance criteria for web interfaces using WCAG 2.2.

40|6|Updated Jul 11, 2026

Search Tags:#accessibility #frontend #wcag #screen-reader #aria #keyboard-navigation

Ready to run

npx skills add https://github.com/magnus919/agent-skills --skill web-accessibility-magnus919

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: web-accessibility
Source: https://github.com/magnus919/agent-skills/tree/main/web-accessibility
Command: npx skills add https://github.com/magnus919/agent-skills --skill web-accessibility-magnus919

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill addresses the gap between visual design and functional accessibility, ensuring web interfaces are usable by people with disabilities across all input methods and assistive technologies.

Core Features & Use Cases

Requirement Definition: Translates feature flows into explicit accessibility acceptance criteria before implementation.
Evidence-Based Verification: Provides a structured protocol for manual and automated testing to ensure compliance with WCAG 2.2 standards.
Use Case: Use this skill to define the keyboard, focus, and screen-reader requirements for a complex custom modal or composite widget to ensure it remains fully accessible before a single line of code is written.

Quick Start

Use the web-accessibility skill to generate accessibility acceptance criteria for a new responsive navigation menu.

Frequently Asked Questions about web-accessibility

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

FAQPage Schema

How do I define accessibility acceptance criteria for a custom web widget before coding?▼

Define accessibility acceptance criteria by translating feature flows into explicit semantic structures, keyboard interaction contracts, and assistive technology requirements before implementation begins. This ensures complex custom modals or composite widgets remain fully accessible.

What's the best way to ensure my web interface meets WCAG 2.2 conformance standards?▼

Ensure WCAG 2.2 conformance by applying a structured protocol for both manual and automated testing. This evidence-based verification validates native HTML semantics, ARIA pattern implementation, and multi-modal input compatibility across your web interface.

How do I implement ARIA patterns and keyboard navigation for screen-reader compatibility?▼

Implement ARIA patterns and keyboard navigation by defining explicit focus management rules and semantic structures for assistive technologies. This process translates visual designs into functional, multi-modal interfaces compatible with screen readers.

When do I need to verify focus management for front-end development workflows?▼

Verify focus management whenever building interactive components that require assistive technology support. You need it to satisfy technical requirements for native HTML semantics and ensure multi-modal input works correctly for users with disabilities.

Does this approach support automated testing for screen-reader compatibility?▼

Yes, screen-reader compatibility is validated through a structured verification protocol that supports both manual and automated testing. This ensures your front-end workflows meet WCAG 2.2 standards and multi-modal input requirements.