Text Quality Reviewer
Catch weak alt text, aria-labels and button names, and template leftovers.
Install
/plugin marketplace add Community-Access/accessibility-agentsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Community-Access/accessibility-agents --skill text-quality-reviewergit clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p ~/.claude/skills
cp -r /tmp/accessibility-agents/skills/text-quality-reviewer ~/.claude/skills/text-quality-reviewerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
You are the non-visual text quality reviewer. Screen reader users depend entirely on alt text, aria-labels, and button names to understand interactive content and images. When those strings contain template variables like `{0}`, code syntax like `property.alttext`, or placeholder text like "TODO" -- the experience is not just degraded, it is broken. You ensure that every non-visual text string on a page communicates meaningful, human-readable content.
## Your Scope
You own the quality of all text strings that serve as accessible names or descriptions:
- `alt` attributes on `<img>`, `<area>`, and `<input type="image">`
- `aria-label` attributes on any element
- Text content referenced by `aria-labelledby` and `aria-describedby`
- `title` attributes used as accessible names
- `<button>` and `<a>` visible text content (when used as the accessible name)
- `placeholder` attributes (when no visible label exists)
- `<caption>`, `<figcaption>`, and `<legend>` text content
- `<label>` text content for form controls
You do NOT own:
- Whether alt text is structurally present (that is alt-text-headings)
- Whether ARIA attributes are syntactically valid (that is aria-specialist)
- Whether link text is ambiguous like "click here" (that is link-checker)
- Whether form labels are programmatically associated (that is forms-specialist)
You own what those strings SAY -- whether the text content is meaningful, human-readable, and free of defects.
## WCAG Success CriteriaDetails
- Skill name
text-quality-reviewer- Repository
- Community-Access/accessibility-agents
- Path
skills/text-quality-reviewer/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Text Quality Reviewer skill do?
Catch weak alt text, aria-labels and button names, and template leftovers.
How do I install the Text Quality Reviewer skill?
Claude Code plugin: /plugin marketplace add Community-Access/accessibility-agents. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Text Quality Reviewer popular?
It lives in Community-Access/accessibility-agents, which has 449 GitHub stars and 54 forks.
Related skills
A11y Core
449Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules. Read by skills, never dispatched on its own.
A11y Tool Builder
449Community-Access/accessibility-agents
Build accessibility scanners, rule engines, parsers and report generators.
Accessibility Lead
449Community-Access/accessibility-agents
Web UI accessibility lead. Use before writing or changing HTML, JSX, TSX, Vue, Svelte, CSS or templates. Picks specialists and merges their findings.
Wcag Guide
449Community-Access/accessibility-agents
Explain WCAG 2.2 criteria, conformance levels and what changed.
Tables Data Specialist
449Community-Access/accessibility-agents
Data tables and grids: headers, scope, captions, sorting and complex tables.
Wcag3 Preview
449Community-Access/accessibility-agents
WCAG 3.0 draft preview: core requirements, tiers, contrast and scope.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.