skills.rest
Omar-Cc
Omar-CcCOMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web interfaces against WCAG 2.2 criteria and resolve accessibility issues.

Updated Jun 1, 2026
Search Tags:#accessibility#a11y#keyboard navigation#frontend#wcag#screen readers#aria
One-click install
npx skills add https://github.com/Omar-Cc/Integrador-II --skill accessibility-omar-cc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/Omar-Cc/Integrador-II/tree/main/frontend/.agents/skills/accessibility
Command: npx skills add https://github.com/Omar-Cc/Integrador-II --skill accessibility-omar-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and fix web accessibility barriers so websites and applications can be usable by people with disabilities and meet WCAG 2.2 expectations.

Core Features & Use Cases

  • Accessibility Auditing: Review interfaces against WCAG principles including perceivable, operable, understandable, and robust requirements.
  • Accessible Implementation Guidance: Apply patterns for keyboard navigation, screen readers, ARIA usage, forms, focus management, and media alternatives.
  • Use Case: A frontend team can use this Skill to improve a website before launch by finding missing labels, contrast issues, keyboard traps, and other accessibility problems.

Quick Start

Use the accessibility skill to audit my web page for WCAG 2.2 issues and suggest improvements.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit a web page for WCAG 2.2 compliance issues?▼

To audit web accessibility for WCAG 2.2 compliance, review interfaces against perceivable, operable, understandable, and robust requirements to identify missing labels, contrast issues, and keyboard traps.

What is the best way to implement ARIA attributes for screen reader support?▼

The best way to implement ARIA for screen reader support is applying accessible markup patterns that ensure robust assistive technology compatibility and validate against WCAG 2.2 criteria.

How do I fix keyboard navigation traps in frontend components?▼

Fix keyboard navigation traps by applying accessible implementation patterns for focus management and keyboard operability, ensuring users can navigate frontend interfaces without getting stuck.

When do I need to validate ARIA implementation for assistive technology compatibility?▼

You need to validate ARIA implementation during frontend development when building inclusive components, ensuring digital interfaces meet WCAG 2.2 expectations for robust assistive technology compatibility.

Does this approach work for auditing existing digital interfaces or only new frontend development?▼

This accessibility auditing approach works for both existing digital interfaces and new frontend development tasks, identifying WCAG compliance issues and suggesting inclusive component design improvements.

Related Skills

Explore More Software Engineering Skills→
Colten-CovingtonColten-Covington

accessibility-audits

Audit web content for WCAG 2.2 AA compliance and assistive technology compatibility.

Community
Basic
PriyanshKuniyalPriyanshKuniyal

accessibility-compliance

Implement WCAG 2.2 Level AA and AAA compliance for mobile accessibility.

Community
Advanced
raybargasraybargas

Frontend Accessibility

Enforce frontend accessibility compliance in web UI code.

Community
Basic
Tahona-AITahona-AI

wcag-audit-patterns

Audit website compliance with WCAG 2.2 standards using automated scripts.

Official
Intermediate