Content
53%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.
The body is a brief, well-sectioned overview with an appropriate one-level-deep reference, but it carries redundant restatements (Quick Reference, Explain) and its guidance stays high-level — the concrete verification steps and code examples all live in references/rule.md while the body itself gives neither a checking method nor an inline example. Sequencing of check → fix → verify is implied by section order rather than stated.
Suggestions
Merge the Quick Reference bullets into the Check/Fix sections (they restate the intro) and either concretize or drop the vague "Explain" section.
Inline one minimal verification step (e.g. "run axe-core or inspect the browser accessibility tree for the orphaned role") so the Check section states how, not just what — currently all verification detail is deferred to the reference.
Align the references/rule.md pointer with the file's actual contents (it holds the code example, rationale, exceptions, and verification steps, not the promised "framework-specific guidance").
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and mostly efficient, but the "Quick Reference" bullets ("Certain roles (like listitem) must be owned by specific parent roles (like list)") restate the intro paragraph and the Check section, and the one-line "Explain" section adds no new information. This is more than the minor trimmable instances of the 4 anchor, but well short of the padded sections of the 2 anchor. | 3 / 5 |
Actionability | Some concrete guidance is present — named roles to check ("listitem, tab, or menuitem") and a specific fix example ("wrap role=\"listitem\" in role=\"list\"") — but there is no code example, command, or verification method in the body itself; the Check section says only "verify that elements... are correctly nested" without how, and the concrete steps (axe, accessibility tree) live in the reference. This fits the 3 anchor (some concrete guidance but incomplete, missing key details) rather than 4, which requires concrete code or commands with only minor gaps. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections imply a rough sequence, but it is never explicitly ordered and validation is only vaguely gestured at ("note how to verify the fix with browser accessibility tooling or assistive tech") without a checkpoint or feedback loop in the body. This matches the 3 anchor (sequence present but checkpoints missing or implicit); the simple-skill 5 exception does not apply because check-then-fix-then-verify is a multi-step flow whose verification step is delegated entirely to the reference. | 3 / 5 |
Progressive Disclosure | The body is a compact overview with clear sections and a well-signaled, verified one-level-deep reference ("see `references/rule.md`", which exists and contains the code examples, rationale, and verification detail — no nested references). Not 5 because the pointer slightly over-promises: it advertises "framework-specific guidance" and "full implementation details" that references/rule.md does not actually contain, a minor navigation-accuracy gap matching the 4 anchor. | 4 / 5 |
Total | 13 / 20 Passed |