CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/wcag-compliance-reporter

Builds a per-page WCAG 2.2 compliance score report by aggregating output from one or more accessibility scanners (axe-core / pa11y / lighthouse / WAVE / IBM Equal Access), pivoting violations by Success Criterion (1.4.3 contrast, 2.4.7 focus visible, etc.), grouping by conformance level (A / AA / AAA), reporting per-page coverage gaps explicitly (the \"this page wasn't scanned\" failure mode), and emitting both an executive summary and a per-page drill-down. Use after a multi-page accessibility scan - pa11y-ci, axe across a sitemap, lighthouse-batch - when the team needs a shareable conformance report rather than a per-page tool dump.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body that sequences a multi-step aggregation pipeline and pushes deep detail to clearly signaled one-level-deep references. Slight room to tighten the Overview and define the helper symbols referenced in the verdict code.

Suggestions

Define or inline `level_set` and `SC_BY_LEVEL` (or point to where they live) so the `conformance` example is fully self-contained.

Trim the Overview's blockquotes and the Anti-patterns table to the load-bearing detail, reducing token overhead without losing the binary-verdict rationale.

Add an explicit validate→fix→retry note for aggregation (e.g., re-run on missing-page flags) to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

Mostly lean with executable code and no generic 'what is WCAG' padding; the SC counts and binary-verdict rationale are load-bearing rather than filler. Minor instances of over-explanation in the Overview blockquotes and the Anti-patterns table could be tightened.

4 / 5

Actionability

Provides concrete executable TypeScript and Python code plus a YAML spec, covering the common aggregation and verdict cases. Minor gaps: `level_set` and `SC_BY_LEVEL` are referenced but not defined, and per-tool normalizer implementations are delegated to a reference.

4 / 5

Workflow Clarity

A clear 6-step sequence (Gather → Normalize → Aggregate → Conformance verdict → Coverage check → Render) with the 'unknown' verdict and coverage-gap flagging acting as validation, but there is no explicit validate→fix→retry feedback loop for the aggregation itself.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to three real files in references/ (tool-normalizers.md, sample-report-format.md, machine-output-and-ci.md) and a consolidated References section; content is appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete capabilities and provides an explicit trigger clause with natural terms. Only minor synonym coverage is missing, keeping trigger_term_quality just below full marks.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('aggregating output', 'pivoting violations by Success Criterion', 'grouping by conformance level', 'reporting per-page coverage gaps', 'emitting both an executive summary and a per-page drill-down') with comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (aggregates/pivots/groups/reports/emits) and 'when' ('Use after a multi-page accessibility scan ... when the team needs a shareable conformance report rather than a per-page tool dump') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger coverage including tool names users say ('pa11y-ci', 'axe across a sitemap', 'lighthouse-batch', 'conformance report', 'accessibility scan') but a few synonyms/extensions (e.g., 'a11y', '.json') are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche as a multi-tool/multi-page aggregation and conformance-reporting step, distinct from the upstream single-tool scanners it consumes; minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents