skills.rest
createtree2017
createtree2017COMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web interfaces against WCAG 2.2 for keyboard and assistive technology accessibility.

Updated Mar 3, 2026
Search Tags:#accessibility#screen reader#keyboard navigation#wcag 2.2#color contrast#form validation#aria
One-click install
npx skills add https://github.com/createtree2017/createtree-office --skill accessibility-createtree2017
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/createtree2017/createtree-office/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/createtree2017/createtree-office --skill accessibility-createtree2017

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you identify and resolve common web accessibility failures so your site works well for keyboard users and people using screen readers, aligning improvements with WCAG 2.2.

Core Features & Use Cases

  • WCAG 2.2-focused audits: Diagnose issues by auditing against POUR (Perceivable, Operable, Understandable, Robust) and common success criteria.
  • Concrete implementation guidance: Provide copy-paste-ready patterns for alt text, color contrast, focus states, skip links, keyboard access, ARIA usage, and live regions.
  • Keyboard and screen-reader readiness: Improve operability via focus visibility, focus not obscured, target sizes, and robust error/status announcements.

Quick Start

Ask the accessibility skill to audit the page you care about and return a prioritized list of WCAG 2.2 fixes for keyboard navigation, screen reader semantics, and form/error handling.

Frequently Asked Questions about accessibility

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

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

To audit web pages for WCAG 2.2 compliance, evaluate UI components, forms, and navigation against POUR principles to identify keyboard navigation, screen reader semantics, and form error handling failures.

What is the best way to fix keyboard navigation and screen reader accessibility?▼

The best way to fix keyboard navigation and screen reader accessibility is applying practical patterns for focus visibility, accessible names, ARIA usage, and live region announcements.

How do I implement accessible form validation and error messaging?▼

Implement accessible form validation and error messaging by ensuring robust status and error announcements using ARIA live regions, allowing assistive technologies to detect and read validation failures.

Does this accessibility audit cover color contrast and target size requirements?▼

Yes, this accessibility audit covers color contrast ratios and target size requirements, diagnosing interface issues against WCAG 2.2 success criteria to ensure operability for all users.

When do I need ARIA live regions for status and error messaging?▼

You need ARIA live regions for status and error messaging when dynamic content updates occur, ensuring screen readers announce validation errors and status changes without requiring page reloads.

Related Skills

Explore More Design & Creative Skills→
dragoscirjandragoscirjan

lang-html

Enforce semantic HTML, WCAG 2.1 AA accessibility, and keyboard navigability.

Community
Basic
imkdwimkdw
1

Frontend Accessibility

Implement accessible React components with ARIA, keyboard navigation, and WCAG compliance.

Community
Intermediate
LuisSambranoLuisSambrano
7

accessibility

Audit web accessibility with Lighthouse and axe-core for WCAG 2.1 compliance.

Community
Intermediate
Montte-erpMontte-erp
6

wcag-audit-patterns

Audit web pages for WCAG 2.2 violations with automated and manual checks.

Official
Intermediate