Verify keyboard operability and screen-reader parity hands-on with the assistive technology real users use. Reach for this on a parity question.
Scanned 9/23/2026
npx -y skills add mcorbett51090/RavenClaude --skill test-assistive-tech --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Test Assistive Tech?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-test-assistive-tech)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: test-assistive-tech
description: "Verify keyboard operability and screen-reader parity hands-on with the assistive technology real users use. Reach for this on a parity question."
---
# 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!