Expert knowledge base for building accessible UI components with awareness of real-world assistive technology (AT) support gaps. Goes beyond the WAI-ARIA spec to provide actual AT compatibility data from a11ysupport.io, known screen reader quirks, proven workarounds, and the critical gotchas that emerge when ARIA meets real users on real devices. Use this skill whenever the user is building, reviewing, fixing, or testing an interactive UI component for accessibility — especially when they need to know what actually works across screen readers, not just what the spec says should work. Trigger on mentions of "ARIA", "a11y", "accessibility", "screen reader", "keyboard navigation", "WAI-ARIA", "APG patterns", "AT support", "assistive technology", "aria-modal", "tooltip role", "combobox", "menu pattern", "switch role", or any question about whether an ARIA feature actually works in practice. Also trigger when the user mentions specific screen readers (JAWS, NVDA, VoiceOver, TalkBack, Narrator) or asks about cross-browser/cross-AT compatibility for accessible components.
How to install aria-patterns?
weaaare/a11y-agents-kit/aria-patterns
$npx -y skills add weaaare/a11y-agents-kit --skill aria-patternsInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/weaaare/a11y-agents-kit" --skill "weaaare/a11y-agents-kit/aria-patterns"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/weaaare/a11y-agents-kit" that are relevant to the current task. Run `npx skills add "https://github.com/weaaare/a11y-agents-kit"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- gpt-image-2Create or edit images with Pilio GPT Image 2 through the unified Pilio developer API.Jul 2026
- spec-driven-implementationDrive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs…Jul 2026
- review-prReview a pull request diff and write structured feedback to review.json for the workflow to publish.Jul 2026
- write-product-specWrite a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation.Jul 2026
- write-tech-specWrite a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints.Jul 2026
- fix-errorsFix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests.Jul 2026
