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 validating screen reader compatibility, debugging assistive technology issues, or ensuring web app accessibility for VoiceOver/NVDA/JAWS/TalkBack.
A practical testing workflow with command references and code patterns that helps teams verify AT support and fix accessibility bugs efficiently.
Use Cases
A frontend team launches a new dashboard but screen reader users report missing form labels and unannounced errors. Using this skill, the team follows the NVDA and VoiceOver checklists, reproduces issues with provided commands, and applies the aria-describedby/role=alert fixes. Result: compliant forms and verified AT support before release.
An auditor needs to verify a SPA's dynamic content announcements and modal focus trapping. They use the JAWS and TalkBack sections plus the modal/tab live-region code patterns to test on Windows and Android, catching focus-return bugs. Value: evidence-based WCAG conformance and better UX for assistive tech users.
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
