accessibility

Audit interfaces against WCAG principles covering keyboard, screen reader, contrast, and motion.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/sohampawar1866/zeromile-go --skill accessibility-sohampawar1866
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/sohampawar1866/zeromile-go/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/sohampawar1866/zeromile-go --skill accessibility-sohampawar1866

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Interfaces often block users who rely on screen readers, keyboards, captions, or reduced motion, and teams lack a structured way to find and fix these barriers. This Skill provides a POUR-based audit framework and concrete checklists to make products usable by people with disabilities. ## Core Features & Use Cases - POUR Audit Framework: Walks Perceivable, Operable, Understandable, and Robust principles with an 8-step checklist covering keyboard navigation, screen readers, contrast, structure, forms, targets, media, and zoom. - Cognitive Accessibility Guidance: Applies W3C COGA's eight objectives for clear language, low memory load, and forgiving flows beyond WCAG conformance. - Motion and Sensory Patterns: Provides prefers-reduced-motion CSS patterns, photosensitivity limits, and older-user ability guidance. - Use Case: When asked to make a checkout flow accessible, use this Skill to tab through the flow, verify screen-reader announcements, check contrast ratios, and confirm reduced-motion handling. ## Quick Start Audit this checkout page for accessibility issues and list the fixes needed for keyboard, screen reader, and contrast compliance.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit a web page for accessibility?

Walk the POUR principles with an eight-step checklist: tab through the flow for keyboard access, test with a screen reader, check contrast ratios (4.5:1 body text), verify semantic structure, label all form fields, check target sizes and timeouts, confirm captions and reduced motion, and test at 200% zoom.

What is the difference between accessibility and inclusive design?

Accessibility covers whether people with disabilities can perceive, operate, and understand a product using assistive tools. Inclusive design covers context-based exclusion like language, culture, device cost, and connectivity, which belongs to the separate inclusive-design skill.

Are automated accessibility checkers like axe enough?

No. Automated tools like axe, Lighthouse, and Accessibility Scanner catch roughly a third of issues. Always add manual checks: navigate with keyboard only, then with a screen reader, then with reduced-motion and large-text OS settings enabled.

How do I support prefers-reduced-motion in CSS?

Wrap vestibular-triggering animations in a @media (prefers-reduced-motion: reduce) block and replace scale, pan, or parallax motion with calm opacity cross-fades. Reduce or replace motion rather than removing all feedback, and never flash content more than about three times per second.

Does WCAG conformance cover cognitive disabilities?

Not fully. W3C COGA guidance is supplemental to WCAG and addresses needs like clear language, single-step instructions, low memory load, and forgiving error recovery for users with dyslexia, ADHD, dementia, or aphasia. A page can pass WCAG and still be unusable for these users.