← ClaudeAtlas

test-assistive-techlisted

Verify keyboard operability and screen-reader parity hands-on with the assistive technology real users use. Reach for this on a parity question.
mcorbett51090/RavenClaude · ★ 7 · Testing & QA · score 63
Install: claude install-skill mcorbett51090/RavenClaude
# Skill: Test assistive tech Automated tools miss focus order, alt-text meaning, and name/role/value — only AT testing finds them (§3 #2 #3). ## Step 1 — Walk it by keyboard No traps, visible focus, logical order, every control reachable and operable (§3 #3). ## Step 2 — Test with a screen reader Name, role, value, state changes, and live-region announcements conveyed correctly (§3 #3). ## Step 3 — Cover the AT a population uses Multiple screen readers/magnification/switch as scope demands; date the AT/browser versions (§3 #8). ## Step 4 — Rank the gaps Order AT-found defects by user-impact via `accessibility_calc.py remediation`. ## Output An AT-session report naming the keyboard/screen-reader parity gaps automated tools missed, ranked by user-impact.