- Home
- Skills
- Sanky369
- Vibe Building Skills
- Accessibility Excellence
accessibility-excellence_skill
16
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill sanky369/vibe-building-skills --skill accessibility-excellence- SKILL.md16.0 KB
Overview
This skill teaches teams to master web accessibility so products are usable by everyone, including people with disabilities. It covers WCAG guidance, semantic HTML, keyboard navigation, screen reader support, color contrast, and inclusive design practices. Accessibility is framed as a core requirement, not an optional feature.
How this skill works
The skill inspects interfaces against WCAG principles (Perceivable, Operable, Understandable, Robust) and flags common failures: missing alt text, poor contrast, broken keyboard focus, non-semantic markup, and ARIA misuse. It provides concrete fixes, code examples, test steps for screen readers, and a prioritized remediation plan focused on WCAG AA. You can use it to audit, implement, and document accessibility work across web and hybrid apps.
When to use it
- During design and planning to bake accessibility into features
- Before launch to audit WCAG AA compliance and reduce legal risk
- When rebuilding UI components to ensure semantic HTML and ARIA correctness
- While adding interactivity (modals, menus, forms) to verify keyboard and focus behavior
- When improving UX for color vision, readability, and multimedia (captions/transcripts)
Best practices
- Start with semantic HTML; enhance with ARIA only when necessary
- Follow WCAG AA as a minimum and prioritize critical user flows
- Ensure all functionality is keyboard accessible and provide visible focus indicators
- Use descriptive alt text, clear link/button labels, and meaningful error messages
- Test with real assistive technologies (NVDA, VoiceOver) and automated tools
Example use cases
- Audit an existing signup flow for keyboard traps, focus order, and form labeling
- Refactor a component library to replace div-based controls with semantic buttons and roles
- Add captions and transcripts to marketing videos and ensure media controls are accessible
- Create an internal WCAG AA checklist and remediation plan for the next sprint
- Validate brand color palette against contrast ratios and propose accessible alternatives
FAQ
WCAG AAA is ideal but often impractical; aim for WCAG AA as the recommended minimum for most products.
When should I use ARIA?
Prefer native, semantic HTML first. Use ARIA to expose semantics for custom widgets only when native elements cannot provide the needed behavior.