accessibility-compliance

Audit web interfaces against WCAG 2.2 AA accessibility requirements.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/trobias/portfolio-nextjs-v2 --skill accessibility-compliance-trobias
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/trobias/portfolio-nextjs-v2/tree/main/.agents/skills/accessibility-compliance
Command: npx skills add https://github.com/trobias/portfolio-nextjs-v2 --skill accessibility-compliance-trobias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web interfaces often ship with accessibility defects—missing labels, broken keyboard navigation, poor contrast, or motion that harms sensitive users—that block people using assistive technologies and create compliance risk. This Skill provides a structured audit workflow to find and fix those issues against WCAG 2.2 AA. ## Core Features & Use Cases - Semantic and ARIA Review: Inspect landmarks, heading order, labels, accessible names, and status messages, preferring native HTML over ARIA. - Keyboard and Focus Testing: Verify complete keyboard operation, focus order, visible focus indicators, skip navigation, and modal focus containment. - Visual and Motion Checks: Check contrast, zoom/reflow, touch target size, reduced-motion support, and flashing or autoplay hazards. - Use Case: Before launching a Next.js marketing site, run the audit to confirm forms announce errors to screen readers, modals trap and restore focus correctly, and all interactive elements meet contrast and target-size requirements. ## Quick Start Audit this page for WCAG 2.2 AA accessibility issues and report the findings with recommended fixes.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I audit a website for WCAG 2.2 AA compliance?▼

Audit a website by inspecting semantics and landmarks, testing complete keyboard operation, checking contrast and reflow, and verifying forms and dynamic updates against WCAG 2.2 AA criteria. Confirm automated findings manually before claiming compliance.

How to test keyboard accessibility and focus management?▼

Test keyboard accessibility by tabbing through every interactive element, verifying logical focus order and visible focus indicators, and checking skip navigation links. Modals must contain focus while open and restore focus to the trigger when closed.

When should I use ARIA instead of native HTML?▼

Use ARIA only when native HTML semantics are insufficient for the component you are building. Native elements like button, nav, and label carry built-in accessibility behavior that ARIA cannot fully replicate, so prefer them first.

Does accessibility testing require reduced motion support?▼

Yes, WCAG requires respecting the user's reduced-motion preference. Avoid flashing content, vestibular-triggering effects, autoplay, and any animation that is required to understand the content.

Can automated accessibility tools prove compliance?▼

No, automated tools only surface leads. Important issues must be confirmed manually through keyboard testing, screen-reader verification, and visual inspection before claiming compliance.