メニュー
Build UIs that work for all users including keyboard navigation, screen readers, and WCAG 2.2
Design multi-agent systems with robust tool interfaces, state management, and failure handling
Build ML systems with disciplined training, evaluation, deployment, and safety practices
Design APIs that are stable, ergonomic, and evolvable
Design systems at the right scale with explicit trade-off documentation
Design services that are reliable, observable, secure, and maintainable
Design CI/CD pipelines with fast feedback, quality gates, and reliable deployments
| name | accessibility-engineering |
| description | Build UIs that work for all users including keyboard navigation, screen readers, and WCAG 2.2 |
| difficulty | senior |
| domains | ["web","mobile"] |
Accessibility is not a checklist — it is a commitment to not excluding users. 1 in 4 adults has some form of disability. Inaccessible software is defective software. This skill bakes accessibility in during development, not as a retrofit.
/review workflow for frontend changesUse the right HTML elements before reaching for ARIA:
<button>), links for navigation (<a href>)<h1>–<h6> in correct order)<ul>, <ol>)<label for>)<nav>, <main>, <header>, <footer>, <aside>)ARIA only when native semantics are insufficient.
Every interactive element must be:
:focus-visible style)Test: complete the key user journeys using only the keyboard.
Test with at least one screen reader:
Verify: can a screen reader user complete the same tasks as a sighted user?
aria-live regionsalt textalt=""prefers-reduced-motionRun axe-core, Lighthouse, or WAVE on every page. Automate in CI. These catch ~30–40% of accessibility issues.
<div> for everything)