skills.rest
latelierkiyose
latelierkiyoseOFFICIAL
Explore all skills by this author →
WebsiteGitHub

accessibility-compliance

Implement WCAG 2.2 compliant interfaces with ARIA and semantic HTML.

Updated Feb 13, 2026
Search Tags:#inclusive design#accessibility#a11y#screen reader#wcag#aria
One-click install
npx skills add https://github.com/latelierkiyose/wp-theme-v2 --skill accessibility-compliance-latelierkiyose
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/latelierkiyose/wp-theme-v2/tree/main/.agents/skills/accessibility-compliance
Command: npx skills add https://github.com/latelierkiyose/wp-theme-v2 --skill accessibility-compliance-latelierkiyose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures digital products are usable by everyone, regardless of ability, by adhering to accessibility standards and best practices.

Core Features & Use Cases

  • WCAG Compliance: Implement guidelines for perceivable, operable, understandable, and robust interfaces.
  • Assistive Technology Support: Ensure compatibility with screen readers, keyboard navigation, and other assistive technologies.
  • Use Case: Audit an existing web application for accessibility violations and refactor components to meet WCAG 2.2 AA standards, improving usability for users with visual impairments.

Quick Start

Audit the provided webpage for accessibility compliance against WCAG 2.2 AA standards.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I audit my web application for WCAG 2.2 compliance?▼

To audit web accessibility for WCAG 2.2 compliance, evaluate semantic HTML structure, ARIA implementation, and keyboard navigation. This process identifies violations against perceivable, operable, understandable, and robust interface guidelines to ensure usability for all users.

What is the best way to implement ARIA patterns for screen reader compatibility?▼

Implementing ARIA patterns for screen reader compatibility requires applying ARIA best practices over semantic HTML. This ensures assistive technologies accurately interpret dynamic web interfaces, enabling users with visual impairments to navigate digital experiences effectively.

Can I use this to check mobile accessibility for inclusive design?▼

Yes, you can check mobile accessibility for inclusive design. The process implements inclusive design patterns and platform-specific accessibility APIs, ensuring mobile interfaces support assistive technologies and meet perceivable, operable, understandable, and robust standards.

How do I fix keyboard navigation issues in my interface?▼

Fixing keyboard navigation issues involves auditing operable interface guidelines and refactoring components using semantic HTML and ARIA roles. This ensures logical focus order and full keyboard operability for users relying on non-mouse interactions.

When do I need to refactor components for platform-specific accessibility APIs?▼

You need to refactor components for platform-specific accessibility APIs when ensuring inclusive user experiences across web and mobile platforms. This adherence guarantees that assistive technologies interact correctly with underlying system accessibility frameworks.

Related Skills

Explore More Design & Creative Skills→
exceptionlessexceptionless
2.5k

accessibility

Enforce WCAG 2.2 AA compliance for frontend components with semantic HTML and ARIA.

Official
Intermediate
luissimon96luissimon96

graph-accessibility

Audit UI components against WCAG 2.2 AA accessibility standards.

Community
Advanced
Higashi-KotaHigashi-Kota

ui-component

Build accessible React UI components with design tokens and ARIA patterns.

Community
Advanced
thiagoooo34252thiagoooo34252
1

engineer-accessibility

Scan web applications for WCAG 2.2 violations using axe-core.

Community
Advanced