Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences (WCAG 2.2 compliance, mobile accessibility, keyboard navigation).
WCAG 2.2 compliant interfaces with proper screen reader support, keyboard navigation, and inclusive design — reducing legal risk and expanding user reach.
Use Cases
A frontend team launches a new web app but receives user complaints about screen reader usability. They invoke this skill to audit the UI against WCAG 2.2, apply ARIA patterns from references, and fix missing labels and focus traps. Result: app passes automated and manual accessibility checks, expanding reach to disabled users.
A product designer builds a mobile signup form and must support iOS VoiceOver and Android TalkBack. Using this skill's mobile accessibility reference, they implement proper labels, reduced-motion, and high-contrast styles. Value: inclusive mobile experience compliant with standards from first release.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File
