skills.rest
monam2
monam2COMMUNITY
Explore all skills by this author →
GitHub

Accessibility

Audit web interfaces for WCAG 2.1 AA compliance and implement accessibility fixes.

Updated Jan 18, 2026
Search Tags:#accessibility#a11y#frontend#wcag#contrast#keyboard#aria
One-click install
npx skills add https://github.com/monam2/traders --skill accessibility-monam2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Accessibility
Source: https://github.com/monam2/traders/tree/main/.agent/skills/accessibility
Command: npx skills add https://github.com/monam2/traders --skill accessibility-monam2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams implement WCAG 2.1 AA accessibility standards to create inclusive user experiences across web interfaces.

Core Features & Use Cases

  • Accessibility auditing and conformance checks against WCAG 2.1 AA
  • ARIA labeling guidance and semantic structure recommendations
  • Color contrast guidance and validation for text and UI components
  • Use Case: When building a new web app, ensure all interactive elements are keyboard accessible, have visible focus indicators, and provide ARIA attributes where appropriate.

Quick Start

Audit your app for WCAG 2.1 AA compliance and start integrating ARIA attributes and accessible color contrast.

Frequently Asked Questions about Accessibility

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

FAQPage Schema
How do I check my web app for WCAG 2.1 AA compliance?▼

To check WCAG 2.1 AA compliance, audit your web app's interactive elements for keyboard navigation, validate color contrast ratios, and verify semantic structure and ARIA attributes. This identifies accessibility gaps and provides actionable steps for conformance.

When do I need to add ARIA attributes to frontend components?▼

You need to add ARIA attributes to frontend components when interactive elements lack semantic HTML structure or require additional context for screen readers. This ensures keyboard navigation and visible focus indicators meet WCAG 2.1 AA accessibility standards.

What is the best way to ensure keyboard navigation works for accessibility?▼

The best way to ensure keyboard navigation accessibility is auditing your user interface to verify all interactive elements are reachable, provide visible focus indicators, and apply appropriate ARIA labeling to meet WCAG 2.1 AA conformance checks.

Does WCAG 2.1 AA compliance require specific color contrast validation?▼

Yes, WCAG 2.1 AA compliance requires specific color contrast validation for text and UI components. You must validate color contrast ratios to address accessibility gaps and ensure inclusive user experiences across web interfaces.

Can I audit existing UI components for accessibility gaps?▼

Yes, you can audit existing UI components for accessibility gaps by running conformance checks against WCAG 2.1 AA standards. This process evaluates current ARIA usage, keyboard access, and contrast to specify actionable improvement steps.

Related Skills

Explore More Design & Creative Skills→
ryan-nguyen-01ryan-nguyen-01
4

skill-ui-accessibility

Analyze web UI structure, semantics, and ARIA usage for accessibility gaps.

Community
Advanced
yezannnnnyezannnnn
148

senior-secops

Automate security scans, risk scoring, and compliance reporting for software projects.

Community
Advanced
Tristan578Tristan578
5

web-accessibility

Implement WCAG 2.1-compliant web interfaces with semantic HTML and ARIA.

Community
Advanced
artsmcartsmc

accessibility-specialist

Identify and remediate web accessibility issues for WCAG 2.1 AA compliance.

Community
Advanced