Identify and remediate accessibility gaps using WCAG 2.2 and keyboard navigation best practices.
npx skills add https://github.com/ghaida/intent --skill include-ghaida
Please help me install this Agent Skill. Skill: include Source: https://github.com/ghaida/intent/tree/main/skills/include Command: npx skills add https://github.com/ghaida/intent --skill include-ghaida
Accessibility is a design quality that ensures every person, regardless of ability or context, can use what you build. This skill treats accessibility as a core design discipline, guiding WCAG 2.2 alignment, screen reader experience design, keyboard navigation, cognitive and motor accessibility, inclusive design beyond compliance, and comprehensive accessibility testing methodology.
Audit your interfaces for WCAG 2.2 conformance and create an inclusive design plan that covers keyboard navigation, screen reader order, and accessible content.
High-intent search queries and answers about installing and using this skill.
Audit WCAG 2.2 conformance by reviewing interface designs for perceivable, operable, understandable, and robust principles. This process identifies accessibility gaps across strategy, content, and IA, guiding remediation for inclusive design from ideation through delivery.
Inclusive design is a discipline ensuring every person, regardless of ability, can use what you build. Apply it from ideation through delivery to embed cognitive, motor, and perceptual considerations across strategy, experience design, and handoff activities.
Design for screen reader and keyboard navigation by specifying reading order, focus management, and operable controls. This ensures interfaces are robust and navigable, embedding accessibility methodology directly into front-end handoffs and design tokens.
Yes, you can align design strategy, experience design, content, and information architecture with inclusive design principles. This ensures accessibility requirements are embedded across all design activities rather than treated as a separate compliance checklist.
Document accessibility requirements for front-end handoffs by specifying design tokens, testing methodologies, and cognitive considerations. This embeds accessibility into developer documentation, ensuring robust, operable, and perceivable interfaces are delivered accurately.
Designs often fail screen reader accessibility due to inadequate reading order, missing keyboard navigation operability, or non-robust content. Applying WCAG 2.2 guidelines and comprehensive testing methodology identifies and remediates these perceptual and motor gaps.
adriaanmostert1976-labGenerate UX Design Briefs from structured interviews or UI mockups.
adrianliechtiGenerate engineer-ready handoff specifications from Figma URLs or design descriptions.
unthinkmediaA comprehensive accessibility review tool for the design and implementation of user interfaces.
ariesanhthuAudits WCAG 2.1/2.2 compliance and fixes accessibility violations in web projects.
