Text Quality Reviewer

Detect non-human-readable accessible names in web application text.

387|42|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Community-Access/accessibility-agents --skill text-quality-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Text Quality Reviewer
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/text-quality-reviewer
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill text-quality-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical issue of low-quality or inaccessible text content in web applications, ensuring that screen reader users and others can understand interactive elements and images.

Core Features & Use Cases

  • Detects common text defects: Identifies template variables, code syntax, placeholder text, and other non-human-readable strings used in accessible names.
  • Enforces WCAG standards: Aligns with criteria for Non-text Content, Name Role Value, and Label in Name.
  • Use Case: Reviewing a new e-commerce product page to ensure that all alt text for images, aria-labels for buttons, and form labels are descriptive, human-readable, and free of development artifacts like {product.name} or TODO.

Quick Start

Use the Text Quality Reviewer skill to check the accessibility of all alt text and aria labels on the current page.

Frequently Asked Questions about Text Quality Reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check web pages for non-human-readable aria-labels and alt text?

To check web pages for non-human-readable aria-labels and alt text, use this Skill to identify template variables, code syntax, and placeholder text. It flags low-quality strings to ensure screen reader users understand interactive elements and images.

What is considered low-quality accessible text for web development?

Low-quality accessible text includes template variables like `{product.name}`, code syntax, placeholder text, duplicate labels, and filename-based alt text. These non-human-readable strings fail WCAG standards and confuse screen reader users navigating web applications.

Does this accessibility check work with vanilla HTML and any web framework?

Yes, this accessibility check works with any web framework or vanilla HTML/CSS/JS. It evaluates text strings used for accessible names independently of the underlying technology stack to enforce WCAG 1.1.1, 4.1.2, and 2.5.3 criteria.

How do I enforce WCAG 1.1.1, 4.1.2, and 2.5.3 for accessible names?

To enforce WCAG 1.1.1, 4.1.2, and 2.5.3 for accessible names, apply this Skill to detect development artifacts and duplicate labels. It ensures all interactive elements and images have descriptive, human-readable text compliant with accessibility standards.

Why does my screen reader announce template variables instead of button names?

Your screen reader announces template variables because non-human-readable strings like `{product.name}` or code syntax are used for accessible names. This Skill identifies and flags these text defects so you can replace them with descriptive labels.