WCAG AA and ARIA best practices — screen readers, keyboard navigation, focus management. Use when building any user-facing interface or reviewing accessibility compliance.
75
63%
Does it follow best practices?
Impact
95%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/design/design-accessibility/SKILL.mdIcon button accessibility
aria-label on icon buttons
100%
100%
No unlabelled icon buttons
100%
100%
Decorative icons hidden
100%
100%
Semantic button elements
100%
100%
No div/span as interactive
100%
100%
sr-only text method used
100%
0%
Single h1
100%
100%
No skipped heading levels
100%
100%
Semantic HTML over ARIA
100%
100%
Links for navigation
100%
100%
Alt text on images
100%
100%
Form label accessibility
No placeholder-only labels
100%
100%
htmlFor + id pairing
100%
100%
All inputs labelled
100%
100%
aria-labelledby used sparingly
100%
100%
Submit uses button element
100%
100%
focus-visible for focus styles
25%
100%
No outline removal
100%
100%
Single h1 on page
100%
100%
No skipped heading levels
100%
100%
Semantic HTML over ARIA
100%
100%
sr-only visually hidden labels
100%
100%
Modal keyboard navigation
Escape closes modal
100%
100%
Focus moves into modal
100%
100%
Focus trapped in modal
100%
100%
Focus returns to trigger
70%
100%
focus-visible for focus ring
100%
100%
No outline removal
100%
100%
Semantic button for trigger
100%
100%
Semantic HTML over ARIA
62%
100%
Single h1 on page
100%
100%
No skipped heading levels
100%
100%
Alt text on images
100%
100%
Click outside closes modal
100%
0%
7b466be
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.