ensuring-accessibility

Ensure WCAG 2.2 AA compliance for UI components and web pages.

1|2|Updated Feb 5, 2026

Search Tags:#inclusive design #accessibility #a11y #screen reader #keyboard navigation #design system #wcag

Ready to run

npx skills add https://github.com/7a336e6e/skills --skill ensuring-accessibility

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ensuring-accessibility
Source: https://github.com/7a336e6e/skills/tree/main/designer/ensuring-accessibility
Command: npx skills add https://github.com/7a336e6e/skills --skill ensuring-accessibility

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 Web Content Accessibility Guidelines (WCAG).

Core Features & Use Cases

WCAG Compliance: Meets WCAG 2.2 AA standards for color contrast, keyboard navigation, and screen reader support.
Accessible Forms: Guides the creation of forms that are usable by all users, including those with disabilities.
Motion Preferences: Respects user settings for reduced motion, preventing discomfort for users sensitive to animation.
Use Case: When designing a new user interface component, use this Skill to verify that all interactive elements are keyboard-navigable and that color contrast ratios meet the required standards.

Quick Start

Verify that the current UI design meets WCAG 2.2 AA standards for color contrast and keyboard navigation.

Frequently Asked Questions about ensuring-accessibility

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

FAQPage Schema

How do I make my UI components comply with WCAG 2.2 AA standards?▼

To make UI components comply with WCAG 2.2 AA, verify color contrast ratios, ensure keyboard operability, and use semantic HTML with ARIA attributes for screen reader compatibility.

What is the best way to design accessible forms for users with disabilities?▼

Designing accessible forms requires proper label associations, logical tab order, and keyboard navigation support to ensure all interactive elements are usable by individuals relying on assistive technologies.

How do I handle reduced motion preferences in an inclusive design system?▼

Handling reduced motion preferences involves detecting user settings and disabling or minimizing animations to prevent discomfort for users sensitive to movement in digital interfaces.

Does my web page need semantic HTML and ARIA attributes for screen reader compatibility?▼

Yes, semantic HTML and ARIA attributes are essential for screen reader compatibility, providing necessary context and roles that allow assistive technologies to interpret and navigate web page content accurately.

Can I get a testing checklist for automated and manual accessibility verification?▼

Yes, you can obtain a testing checklist for accessibility verification that covers both automated scanning and manual checks for keyboard navigation, contrast, and screen reader interactions.

What color contrast ratios are required to meet WCAG 2.2 AA compliance?▼

Meeting WCAG 2.2 AA compliance requires color contrast ratios of at least 4.5:1 for normal text and 3:1 for large text to ensure readability for visually impaired users.