Color Audit
rome-os/rome
Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…
A skill your agent uses when performing accessibility audits of web pages, components, or full user flows.
Install Screen Reader Testing
$ npx skills add thedaviddias/Front-End-Checklist --skill screen-reader-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist screen-reader-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/screen-reader-testing .claude/skills/screen-reader-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "screen-reader-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/screen-reader-testing into .claude/skills/screen-reader-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screen-reader-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/screen-reader-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill screen-reader-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist screen-reader-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/screen-reader-testing .agents/skills/screen-reader-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "screen-reader-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/screen-reader-testing into .agents/skills/screen-reader-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screen-reader-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill screen-reader-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist screen-reader-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/screen-reader-testing .cursor/skills/screen-reader-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "screen-reader-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/screen-reader-testing into .cursor/skills/screen-reader-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screen-reader-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/screen-reader-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill screen-reader-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist screen-reader-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/screen-reader-testing .gemini/skills/screen-reader-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "screen-reader-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/screen-reader-testing into .gemini/skills/screen-reader-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screen-reader-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist screen-reader-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill screen-reader-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/screen-reader-testing .github/skills/screen-reader-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "screen-reader-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/screen-reader-testing into .github/skills/screen-reader-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screen-reader-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill screen-reader-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist screen-reader-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/screen-reader-testing .opencode/skills/screen-reader-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "screen-reader-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/screen-reader-testing into .opencode/skills/screen-reader-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screen-reader-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
screen-reader-testing- GitHub stars
- 74k
- Token cost
- ~1k tokens
- SKILL.md length
- 482 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when performing accessibility audits of web pages, components, or full user flows.
- Performing accessibility audits of web pages
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Full user flows
What it does
Screen Reader Testing is an agent skill from thedaviddias/Front-End-Checklist. Use when performing accessibility audits of web pages, components, or full user flows. Applies to all web content accessed via assistive technology. Particularly important for custom JavaScript widgets, single-page applications, dynamically updated content, modal dialogs, and forms with validation.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Frontend & Design, covering Accessibility and UX design. It works with JavaScript. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Performing accessibility audits of web pages
- Full user flows
Example prompts
- “/screen-reader-testing”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Screen Reader Testing loads about 1k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 482 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 482 words, ~1,017 tokens.
Download SKILL.mdSave it as
.claude/skills/screen-reader-testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- screen-reader-testing
- description
- Use when performing accessibility audits of web pages, components, or full user flows. Applies to all web content accessed via assistive technology. Particularly important for custom JavaScript widgets, single-page applications, dynamically updated content, modal dialogs, and forms with validation.
- metadata.category
- accessibility
- metadata.priority
- high
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 60
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/accessibility/screen-reader-testing
Test with screen readers
Screen readers are the primary interface for blind users and many users with severe low vision or motor disabilities. Automated accessibility scanners cannot detect incorrect announcements, wrong reading order, missing context, focus traps, or broken keyboard interactions. A page that passes automated checks can still be completely unusable by a screen reader user. Manual screen reader testing with representative tasks is the only way to verify real usability for this population.
Quick Reference
- Automated tools catch ~30-40% of accessibility issues — screen reader testing finds the rest
- Test with NVDA + Chrome or Firefox on Windows; JAWS + Chrome on Windows; VoiceOver + Safari on macOS/iOS; TalkBack + Chrome on Android
- Verify: all interactive elements are reachable by keyboard, announced correctly, and operable
- Check dynamic content: live regions (
aria-live), modal dialogs (focus trap), and custom widgets (menus, tabs, trees) - Test real user flows: form completion, navigation to a destination, error correction
Check
Test the page with at least two screen reader / browser combinations: (1) NVDA + Chrome (Windows) or VoiceOver + Safari (macOS). Navigate using only the keyboard: Tab for focusable elements, arrow keys for widgets, heading navigation (H key in NVDA/JAWS), landmark navigation (D/R keys), and links list (NVDA: Insert+F7). Verify: all interactive elements are reachable and announced with name + role + state; custom widgets (menus, tabs, dialogs) follow ARIA Authoring Practices Guide keyboard patterns; dynamic updates are announced via live regions; focus is managed correctly when modals open and close.
Fix
Common issues and fixes: (1) Missing accessible names — add aria-label or associate <label> elements. (2) Wrong reading order — reorder DOM structure to match visual order; use CSS for visual reordering only. (3) Focus lost after modal closes — return focus to the trigger element. (4) Dynamic content not announced — add aria-live='polite' (non-critical) or aria-live='assertive' (critical alerts) to containers. (5) Custom widget not keyboard operable — implement ARIA APG keyboard patterns (roving tabindex for menus, arrow keys for tabs). (6) Form errors not announced — associate error messages via aria-describedby or use aria-live regions.
Show full SKILL.md (153 more words)Show less
Explain
Screen readers convert web content to audio or braille output. They build their understanding of a page from the accessibility tree — a parallel representation of the DOM constructed from HTML semantics and ARIA attributes. Automated tools check the tree structure for known violations, but cannot verify whether a blind user can actually complete a task. Screen reader testing requires navigating with real screen reader commands: reading mode (virtual cursor) for browsing content, forms/application mode for interacting with widgets, and shortcut keys for headings, landmarks, and links. Each screen reader + browser combination has unique behavior quirks.
Code Review
Review the rendered markup and interactive states that affect Test with screen readers. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/screen-reader-testing
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/screen-reader-testing of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Screen Reader Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Screen Reader Testing this skillthedaviddias/Front-End-Checklist | 74k | — | ~1k | Automated safety check: Pass | MIT | |
| Color Auditrome-os/rome | 725 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Bdgszymdzum/browser-debugger-cli | 161 | — | ~2.3k | Automated safety check: Notes | MIT | |
| Connect Component To Figmadequelabs/cauldron | 129 | — | ~2k | Automated safety check: Pass | MPL-2.0 | |
| Frontend Design Principlespretend1111/claude-desktop-app | 494 | 1 repos | ~824 | Automated safety check: Pass | Custom licence | |
| Dont Make Me Thinkluongnv89/skills | 131 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Bdg
szymdzum/browser-debugger-cli
Use bdg CLI to drive and debug a real Chrome via Chrome DevTools Protocol - navigate, click, fill and submit forms, check what an action changed (navigation, new messages, pending requests), inspect…
Connect Component To Figma
dequelabs/cauldron
Add a Figma Code Connect (.figma.tsx) file for a Cauldron React component.
Frontend Design Principles
pretend1111/claude-desktop-app
Gives practical design rules for polished HTML, CSS and JavaScript interfaces and browser games, covering spacing, type, color, components, motion and responsive breakpoints.
Dont Make Me Think
luongnv89/skills
Review UI usability using Steve Krug's principles and produce a scannable report.
Super UI UX Design
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete UI/UX design capability — a wiki-style knowledge map of design theory (UX laws, Nielsen heuristics, usability, visual hierarchy, typography, contrast/WCAG, design systems…
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Works with
Categories
Questions about Screen Reader Testing
What does Screen Reader Testing do?
A skill your agent uses when performing accessibility audits of web pages, components, or full user flows. Screen Reader Testing is an agent skill from thedaviddias/Front-End-Checklist. Use when performing accessibility audits of web pages, components, or full user flows.
When should I use Screen Reader Testing?
Screen Reader Testing fits situations like: performing accessibility audits of web pages; full user flows.
How do I install Screen Reader Testing in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill screen-reader-testing -a claude-code`. Or copy the skill folder (skills/screen-reader-testing in thedaviddias/Front-End-Checklist) into .claude/skills/screen-reader-testing in your project. Claude Code loads it when a task matches its description.
How do I install Screen Reader Testing in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill screen-reader-testing -a codex`. Or copy the skill folder (skills/screen-reader-testing in thedaviddias/Front-End-Checklist) into .agents/skills/screen-reader-testing in your project. Codex loads it when a task matches its description.
Can I use Screen Reader Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill screen-reader-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/screen-reader-testing, .gemini/skills/screen-reader-testing, .github/skills/screen-reader-testing and .opencode/skills/screen-reader-testing in your project.
What does Screen Reader Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Screen Reader Testing is instructions for the agent only.
Does Screen Reader Testing access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Screen Reader Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Screen Reader Testing use?
Screen Reader Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Screen Reader Testing use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
What are the alternatives to Screen Reader Testing?
Skills that share tags, products or a category with Screen Reader Testing: Color Audit (rome-os/rome, 725 stars), Bdg (szymdzum/browser-debugger-cli, 161 stars), Connect Component To Figma (dequelabs/cauldron, 129 stars) and Frontend Design Principles (pretend1111/claude-desktop-app, 494 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Screen Reader Testing?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,398 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.