Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →community-access/Text Quality Reviewer
Non-visual text quality reviewer for web applications.
Passed 19 of 23 test cases with the skill, and 3 of 23 without it.
and 28 more in the full report
16 fixed3 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
Examine this template image element: `<img src="/photos/office.jpg" alt="TODO">`. What text quality rule tag and WCAG criterion apply to this tag?
| Checked | Without skill | With skill |
|---|---|---|
| Flags the attribute value using rule code TQR-003 | Missed | Passed |
| Cites WCAG criterion 1.1.1 Non-text Content or 2.4.6 Headings and Labels | Passed | Passed |
The instructions your model reads when the skill loads.
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.
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 elementaria-labelledby and aria-describedbytitle 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 controlsYou do NOT own:
You own what those strings SAY -- whether the text content is meaningful, human-readable, and free of defects.
All non-text content has a text alternative that serves the equivalent purpose. Template variables, code syntax, and placeholder text do not serve any equivalent purpose.
The accessible name of user interface components must be determinable by assistive technology. Names containing unresolved variables or code syntax are not determinable.
The accessible name must contain the visible text. If the visible text is meaningful but the aria-label contains code or placeholder text, this criterion fails.
test cases passed, vs 3 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.