Content
65%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, well-organized overview with excellent progressive disclosure to a single real reference file. The weaknesses are thin actionability (no inline example markup or detection steps) and an implicit workflow with no explicit verification steps.
Suggestions
Add one small before/after markup snippet (or a concrete detection step like 'Tab through the page and note where focus jumps') to the Check or Fix section so the guidance is executable without opening references/rule.md.
Make the sequence explicit — e.g., number the steps '1. Check for positive tabindex values and unfocusable custom elements → 2. Fix by... → 3. Verify by re-tabbing through the page / checking the browser accessibility tree'.
Merge the redundant Check/Fix/Explain one-liners, which restate the Quick Reference bullets, to tighten the body further.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~30-line body is compact and the Quick Reference delivers the core rules in three bullets, but the Check/Fix/Explain sections largely restate those bullets ("positive tabindex values" appears in all three), so a few lines could be trimmed. | 4 / 5 |
Actionability | Concrete attribute values are given ("tabindex=\"0\"", "tabindex=\"-1\"", avoid positive values), but the Check/Fix sections are one-line directives with no example markup or concrete detection steps (e.g., how to walk the tab order or inspect the accessibility tree) — those details are deferred entirely to references/rule.md. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections imply a rough sequence, but the steps are not explicitly ordered and validation checkpoints are only implicit — the Code Review section says to "note how to verify the fix with browser accessibility tooling" without describing any verification step. | 3 / 5 |
Progressive Disclosure | The short body holds the core rules and defers implementation details, code examples, and framework guidance to a single clearly signaled one-level-deep reference (references/rule.md), which exists as a real 51-line file; navigation is easy. | 5 / 5 |
Total | 15 / 20 Passed |