Accessibility a11y
Skill jgamaraalv/delivery-loop/.claude/skills/accessibility-a11y
Continuous fullstack delivery loops — orchestrates frontend, backend, and quality subagents (behaviour drivers, engineers, UI/UX specialist, code/security reviewers, architects) in a test → diagnose → fix → review → secure → re-test cycle until the work is production-ready
npx -y skills add jgamaraalv/delivery-loop --skill accessibility-a11yAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Build inclusive, WCAG-compliant UIs. Use for a11y, screen readers, ARIA, keyboard nav, contrast, or accessibility audits.
SKILL.md
1.8 KB, as published. Nobody here has run it
Accessibility (a11y) Best Practices
You are an expert in web accessibility and inclusive design. Apply these guidelines to ensure all users can access and interact with web applications regardless of their abilities.
Core Accessibility Principles
- Follow WCAG (Web Content Accessibility Guidelines) standards
- Use semantic HTML to improve accessibility and screen reader compatibility
- Ensure high accessibility standards using ARIA roles and native accessibility props
- Design for all users including those with visual, auditory, motor, and cognitive disabilities
- Test with various assistive technologies
References
Each file is loaded on demand — read one only when the task needs that depth (progressive disclosure).
references/semantic-aria.md— semantic HTML (structural elements, form accessibility) and ARIA (when to use it, common patterns) · read when authoring markup, forms, or non-native interactive widgets.references/visual-keyboard.md— visual accessibility (color, contrast, focus management) and keyboard navigation (requirements, interactive elements, touch targets) · read when styling visuals/focus or making interactions keyboard-operable.references/content-responsive.md— content accessibility (images, media, text, typography) and responsive/adaptive design (mobile-first, user preferences likeprefers-reduced-motion) · read when handling images/media/copy or building responsive, preference-aware layouts.references/testing-css.md— testing & validation (automated tools, manual/screen-reader testing) and CSS best practices for accessibility · read when auditing/validating a11y or setting up styling conventions.