screen-reader-testing
Test Screen Reader Accessibility
Screen reader defects are hard to catch with visual testing alone. This skill guides practical VoiceOver, NVDA, JAWS, and TalkBack validation.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "screen-reader-testing" from https://skillstore.io/skills/wshobson-screen-reader-testing.md and its manifest at https://skillstore.io/api/skills/wshobson-screen-reader-testing/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "screen-reader-testing". Review a checkout form with required fields and validation errors.
Expected outcome:
- Test sequence covering field navigation, label announcements, required state, invalid input, submission, error announcement, and focus placement.
- Expected screen reader output for each step, plus a defect list for missing labels or disconnected error text.
Using "screen-reader-testing". Plan screen reader coverage for a new account settings page.
Expected outcome:
- Priority matrix for NVDA with Firefox, VoiceOver with Safari, and mobile VoiceOver or TalkBack.
- Checklist covering page title, landmarks, headings, controls, dialogs, and dynamic save status messages.
Using "screen-reader-testing". Debug a tab component that sounds confusing in screen readers.
Expected outcome:
- Keyboard test steps for tab movement, selection state, panel announcement, and focus order.
- Recommended fixes for missing labels, incorrect selected state, or hidden panel content.
Security Audit
SafeAll static findings were false positives after context review. Backtick findings are Markdown fences, sensitive findings are keyboard event examples, network findings are resource links, and blocker findings are accessibility examples. No prompt injection, exfiltration intent, or malicious execution instructions were found in SKILL.md.
Risk Factors
⚙️ External commands (35)
🌐 Network access (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/wshobson-screen-reader-testing/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/wshobson-screen-reader-testing?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/wshobson-screen-reader-testing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wshobson-screen-reader-testing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/wshobson-screen-reader-testing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
wshobson. (2026). screen-reader-testing security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wshobson-screen-reader-testing/audits/7BibTeX citation
@techreport{wshobson-wshobson-screen-reader-testing-2026,
author = {wshobson},
title = {screen-reader-testing security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/wshobson-screen-reader-testing/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "screen-reader-testing security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "wshobson"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/wshobson-screen-reader-testing/audits/7"
identifiers:
- type: other
value: "skillstore:wshobson-screen-reader-testing:audit:7"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-screen-reader-testing
2026-08-21
wshobson-screen-reader-testing
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Validate a Release Candidate
Run focused screen reader checks before shipping a web application update.
Build Regression Test Scripts
Create repeatable manual scripts for headings, forms, dialogs, and dynamic announcements.
Document Accessibility Defects
Capture expected announcements, actual screen reader behavior, and clear remediation notes.
Try These Prompts
Guide me through a basic screen reader review for this page using VoiceOver or NVDA. Focus on page title, headings, landmarks, links, and form labels.
Help me test this form with a screen reader. Check whether labels, required states, instructions, invalid entries, and error messages are announced correctly.
Create a screen reader test plan for a release candidate. Include priority browser combinations, test tasks, expected announcements, and defect notes.
Analyze this modal, tab interface, or live region for screen reader behavior. Define keyboard steps, expected announcements, focus handling, and likely failures.
Best Practices
- Test with real screen readers, not only automated scanners or browser accessibility trees.
- Start with semantic HTML before adding ARIA roles, states, or live regions.
- Record exact steps, expected announcements, actual announcements, and affected browser combinations.
Avoid
- Testing only one screen reader and treating the result as full coverage.
- Adding ARIA without confirming that keyboard behavior and focus management work.
- Checking only the successful path while skipping errors, loading states, and dialogs.