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 17 of 20 test cases with the skill, and 4 of 20 without it.
and 17 more in the full report
15 fixed4 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/1/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
In `src/components/ProductImage.jsx`, a developer wrote `<img src={src} alt="{alt}" />`. Provide the structural review finding and corrected React JSX code.
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the rule code as TQR-001. | Missed | Passed |
| Provides JSX fix code using alt={alt} without literal quotes around the variable. | 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 4 / 20 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.