skills.rest
danieliudi
danieliudiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

include

Audits designs against WCAG 2.2 and guides accessible, inclusive interface design.

Updated Aug 26, 2026
Search Tags:#inclusive design#accessibility#a11y#screen reader#keyboard navigation#audit#wcag
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill include-danieliudi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: include
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/include
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill include-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design teams often ship interfaces that exclude users with disabilities because accessibility is treated as a late compliance checkbox rather than a design discipline. This Skill embeds WCAG 2.2 guidance, screen reader experience design, keyboard navigation patterns, and inclusive design principles directly into the design workflow, catching exclusion before it ships. ## Core Features & Use Cases - WCAG 2.2 Design Guidance: Translates the four WCAG principles (Perceivable, Operable, Understandable, Robust) into actionable design decisions covering contrast ratios, touch targets, focus management, and semantic structure. - Screen Reader & Keyboard Experience Design: Provides methodology for reading order, landmarks, heading hierarchy, ARIA live regions, focus traps, and roving tabindex patterns. - Accessibility Testing Methodology: Combines automated tools (axe, Lighthouse, WAVE) with manual keyboard, screen reader, zoom, contrast, and reduced-motion testing to cover the 70% of issues automation misses. - Use Case: Before handing off a checkout flow, run an accessibility audit to verify keyboard operability, screen reader announcements, color contrast, and cognitive load, then produce a prioritized remediation plan (P0-P3). ## Quick Start Ask the assistant to audit your checkout flow design for WCAG 2.2 accessibility issues and produce a prioritized remediation plan.

Frequently Asked Questions about include

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

FAQPage Schema
How do I audit a design for WCAG 2.2 accessibility?▼

Audit against the four WCAG principles: Perceivable (contrast ratios, alt text, reflow), Operable (keyboard access, touch targets, no traps), Understandable (reading level, consistency, error handling), and Robust (semantic HTML, correct ARIA). Combine automated scans with manual keyboard and screen reader testing.

What accessibility issues do automated tools miss?▼

Automated tools like axe, Lighthouse, and WAVE catch roughly 30% of issues, mostly programmatic ones like missing alt text or low contrast. The remaining 70% — illogical reading order, confusing interaction patterns, poor focus management — require manual testing with keyboards and real screen readers.

How do I test a website with a screen reader?▼

Use VoiceOver on Mac/iOS (Cmd+F5), NVDA on Windows (free), or TalkBack on Android. Listen for logical reading order, announced roles and states on interactive elements, form labels, live region updates, and meaningful heading and landmark structure.

What are the WCAG 2.2 touch target size requirements?▼

WCAG 2.2 requires a minimum of 24x24 CSS pixels for touch targets, with 44x44px recommended for primary actions and at least 8px spacing between adjacent targets. Measure the tappable area including padding, not just the visible element.

When should ARIA be used instead of native HTML?▼

ARIA should only supplement HTML when no native element exists for the pattern. The first rule of ARIA is to prefer native elements like button and nav; incorrect ARIA is worse than none because it announces semantics the element does not actually support.

Is web accessibility legally required?▼

Yes, WCAG conformance is legally mandated in many jurisdictions, including the ADA in the US, the European Accessibility Act in the EU, and Section 508 for US government. Web accessibility lawsuits have increased every year for a decade.

Related Skills

Explore More Design & Creative Skills→
junevmjunevm

ux-designer

Produce research-grounded UX plans covering information architecture, user flows, wireframing, prototyping, and design-system handoff.

Community
Intermediate
BWCbewchanBWCbewchan
5

web-accessibility

Implement WCAG-aligned ARIA patterns and keyboard navigation in web applications.

Community
Intermediate
ghaidaghaida
116

evaluate

Evaluate UX issues and route findings to responsible Intent skills.

Community
Advanced
myPOStechmyPOStech

legal-triage-inspection-support

Triages regulatory inspection and supervisory review requests with mandatory human review escalation.

Official
Basic