CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/widget-a11y-test-matrix

Per-widget manual accessibility test matrices where every row pairs one keystroke with the expected focus behavior, the expected NVDA announcement, the expected VoiceOver announcement, and the WCAG 2.2 success criterion that row verifies. Covers button, toggle button, checkbox, text input, modal dialog, menu button, and combobox archetypes, plus universal Tab traversal. Use when a rendered widget has cleared automated scanning and a tester needs a fill-in pass/fail sheet to run by hand against NVDA and VoiceOver.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A well-architected reference-matrix skill: actionable templates, a clear validated workflow, and clean one-level progressive disclosure. The only weakness is length — the scope and limitations prose is discursive and could be trimmed.

Suggestions

Tighten the 'What this owns, and what it does not' section: the four out-of-scope bullets overlap with the 'Limitations' section and could be merged or condensed to cut ~15 lines.

Consider moving the 'Announcement strings are expectations, not guarantees' methodology note into the extended reference file, keeping SKILL.md focused on the matrices and steps.

The 'Test stacks' prose paragraph largely restates the table above it; drop the redundant explanation and keep only the VoiceOver label-inference caveat.

DimensionReasoningScore

Conciseness

Assumes Claude's competence throughout (no padding with what screen readers or WCAG are) and every section maps to a deliverable, but the body is long and the 'What this owns / does not' and 'Limitations' prose could be tightened without losing clarity.

2 / 3

Actionability

Instruction-only yet copy-paste ready: concrete keystrokes, exact expected NVDA/VoiceOver announcement strings with placeholders, SC citations per row, a fill-in Result/Notes sheet template, and a fully worked example.

3 / 3

Workflow Clarity

Explicit Steps 1–5 are clearly sequenced with per-row PASS/FAIL/N/A checkpoints, an early-finding checkpoint in Step 3 (missing visible label recorded before proceeding), and failure attribution to the row's SC in Step 5.

3 / 3

Progressive Disclosure

Core matrices live inline while the longest tables (menu button M1–M10, combobox K1–K9) and the SC lookup are split into a real, well-structured references/widget-matrices-extended.md, signaled one level deep in two places.

3 / 3

Total

11

/

12

Passed

Description

100%

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 answers both what and when, uses natural trigger terms, and carves out a distinct niche. It is written in third person and contains no vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — pairing each keystroke with expected focus behavior, NVDA announcement, VoiceOver announcement, and WCAG 2.2 SC — and enumerates seven named archetypes plus universal Tab traversal.

3 / 3

Completeness

Clearly states what it does (per-widget keystroke/announcement/SC matrices) and when to use it via an explicit 'Use when a rendered widget has cleared automated scanning and a tester needs a fill-in pass/fail sheet' clause.

3 / 3

Trigger Term Quality

Uses natural terms a tester would say ('accessibility test matrices', 'NVDA', 'VoiceOver', 'WCAG 2.2', 'automated scanning', 'pass/fail sheet') with good coverage and no reliance on opaque jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — manual per-widget screen-reader test matrices run after automated scanning — with triggers unlikely to fire for general a11y, ARIA-authoring, or scanning skills.

3 / 3

Total

12

/

12

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