fc3c7ae8a2
Add repo-wide auditing and targeted repair scripts for skill metadata. Fix truncated descriptions automatically, keep heading normalization conservative, and remove synthetic boilerplate sections that degrade editorial quality while regenerating repo indexes and catalogs. Fixes #365
37 lines
1.0 KiB
Markdown
37 lines
1.0 KiB
Markdown
---
|
|
name: screen-reader-testing
|
|
description: "Practical guide to testing web applications with screen readers for comprehensive accessibility validation."
|
|
risk: unknown
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# Screen Reader Testing
|
|
|
|
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.
|
|
|
|
## Use this skill when
|
|
|
|
- Validating screen reader compatibility
|
|
- Testing ARIA implementations
|
|
- Debugging assistive technology issues
|
|
- Verifying form accessibility
|
|
- Testing dynamic content announcements
|
|
- Ensuring navigation accessibility
|
|
|
|
## Do not use this skill when
|
|
|
|
- The task is unrelated to screen reader testing
|
|
- You need a different domain or tool outside this scope
|
|
|
|
## Instructions
|
|
|
|
- Clarify goals, constraints, and required inputs.
|
|
- Apply relevant best practices and validate outcomes.
|
|
- Provide actionable steps and verification.
|
|
- If detailed examples are required, open `resources/implementation-playbook.md`.
|
|
|
|
## Resources
|
|
|
|
- `resources/implementation-playbook.md` for detailed patterns and examples.
|