Agent skill · software engineering · aj-geddes
frontend-accessibility
Implement WCAG compliance using semantic HTML, ARIA, keyboard navigation, and screen reader support. Use when building inclusive applications for all users.
Why this skill is useful
Codifies best practices for implementing WCAG compliance but AI already knows general accessibility principles.
What it needs
About 1k tokens when loaded. Last updated 2026-03-04. 307 stars on the source repository.
What this skill does
Frontend Accessibility Table of Contents Overview When to Use Quick Start Reference Guides Best Practices Overview Build accessible web applications following WCAG guidelines with semantic HTML, ARIA attributes, keyboard navigation, and screen reader support for inclusive user experiences. When to Use Compliance with accessibility standards Inclusive design requirements Screen reader support Keyboard navigation Color contrast issues Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents --- --- Semantic HTML and ARIA Semantic HTML and ARIA Keyboard Navigation Keyboard Navigation Color Contrast and Visual Accessibility Color Contrast and Visual Accessibility Screen Reader Announcements Screen Reader Announcements Accessibility Testing Accessibility Testing Best Practices ✅ DO Follow established patterns and conventions Write clean, maintainable code Add appropriate documentation Test thoroughly before deploying ❌ DON'T Skip testing or validation Ignore error handling Hard-code configuration values
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/frontend-accessibility