skills.rest
oborchers
oborchersCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Review web interfaces for WCAG 2.2 AA accessibility compliance.

28|3|Updated Feb 22, 2026
Search Tags:#accessibility#a11y#screen reader#keyboard navigation#wcag#contrast#spa
One-click install
npx skills add https://github.com/oborchers/fractional-cto --skill accessibility-oborchers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/oborchers/fractional-cto/tree/main/saas-design-principles/skills/accessibility
Command: npx skills add https://github.com/oborchers/fractional-cto --skill accessibility-oborchers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need for web and application accessibility, ensuring compliance with legal standards and providing an inclusive user experience for all individuals, including those with disabilities.

Core Features & Use Cases

  • WCAG 2.2 AA Compliance: Guides users to meet or exceed accessibility standards.
  • Keyboard Navigation & Focus Management: Details how to ensure all interactive elements are operable via keyboard and that focus is always visible and managed correctly, especially in Single Page Applications (SPAs).
  • Screen Reader Support: Provides guidance on ARIA attributes and best practices for screen reader compatibility.
  • Color Contrast: Specifies minimum contrast ratios for text and UI elements.
  • Accessible Component Primitives: Recommends using established libraries to avoid common pitfalls in custom component development.
  • Use Case: When designing a new user interface component, use this Skill to ensure it meets all keyboard navigation, screen reader, and color contrast requirements before development begins.

Quick Start

Review the provided checklist to ensure the current interface meets WCAG 2.2 AA standards for color contrast and keyboard operability.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I ensure my web application meets WCAG 2.2 AA accessibility standards?▼

To meet WCAG 2.2 AA accessibility standards, verify keyboard operability, manage focus correctly, ensure screen reader compatibility, and check minimum color contrast ratios. A compliance review checklist helps validate these interface requirements before development.

What is the best way to handle keyboard navigation and focus management in a Single Page Application?▼

Keyboard navigation and focus management in a Single Page Application require ensuring all interactive elements are operable via keyboard and that focus remains visible during dynamic routing updates. Proper ARIA attributes and accessible component primitives help achieve this operability.

How do I add screen reader support using ARIA attributes?▼

Screen reader support using ARIA attributes involves implementing correct roles, states, and properties on dynamic elements. Establishing accessible component primitives prevents common custom development pitfalls and ensures screen readers correctly interpret UI interactions.

What are the minimum contrast ratios required for WCAG 2.2 AA compliance?▼

Minimum contrast ratios for WCAG 2.2 AA compliance specify exact visual thresholds for text and UI elements against their backgrounds. Reviewing these color contrast ratios during the design phase ensures readable interfaces for visually impaired users.

When should I use accessible component primitives instead of building custom UI components?▼

Use accessible component primitives instead of custom UI components when standard interactions like keyboard operability or screen reader support are needed. Established libraries prevent common accessibility pitfalls and streamline WCAG 2.2 AA compliance verification.

Does this approach provide manual testing methods for WCAG compliance verification?▼

Yes, WCAG compliance verification includes manual testing methods and a review checklist. These methods help verify keyboard operability, focus management, screen reader compatibility, and color contrast ratios against the required accessibility standards.

Related Skills

Explore More Design & Creative Skills→
jpoindexterjpoindexter
1

accessibility-and-inclusive-design

Implement WCAG 2.2 AA accessibility standards for web and native applications.

Community
Advanced
ryan-nguyen-01ryan-nguyen-01
4

skill-ui-accessibility

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

Community
Advanced
mae616mae616
9

accessibility-engineer

Enforce accessible UI with semantic HTML and minimal ARIA.

Community
Basic
oborchersoborchers
28

accessibility-inclusive-design

Guide WCAG 2.2 AA compliance with color contrast and keyboard operability checks.

Community
Intermediate