Individual skill
web-accessibility
Build accessible websites: semantic HTML, ARIA, keyboard support, focus management, and WCAG testing. Use for inclusive, compliant web development.
skills/web-accessibility/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 56
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- testing Derived category
- engineering Derived category
- engineering-web Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,726 bytes
Read excerpt
# Web Accessibility
A practical guide to building accessible websites: semantic HTML first, ARIA where needed, keyboard support, focus management, color contrast, and testing — covering WCAG 2.2 AA in practice, not just theory.
## Overview
Accessibility is **usability for everyone**, including people using screen readers, keyboards, voice control, or with low vision, color blindness, or motor/cognitive differences. The good news: 80% of it is unglamorous fundamentals — semantic HTML, labels, contrast, keyboard support. The expensive failures come from custom components (dropdowns, modals, tabs) built without the platform's built-in behaviors.
Rule: **use native elements first** (`<button>`, `<input>`, `<select>`, `<dialog>`). Custom components must reimplement everything native gives free.
## When to use
- Every web project (a11y is a requirement, not a feature).
- Auditing an existing site for WCAG compliance.