CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-eu-accessibility-audit

Audits a website or app against the European Accessibility Act and WCAG 2.1 AA, producing a scope memo, remediation report, and accessibility statement. Use when: Determine if a business falls under European Accessibility Act scope; Perform a full WCAG 2.1 AA audit with step-by-step testing instructions; Create prioritized remediation reports with specific code fixes.

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-web-audits/skills/nex-eu-accessibility-audit/SKILL.md

The canonical home for this skill is nex-eu-accessibility-audit in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

17%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.

The body is a promotional README rather than an operational skill: it markets capabilities and deliverables but contains no executable audit procedure, decision tree, testing instructions, or templates, and concedes the scripts and templates are missing from the folder. Roughly half the content is marketing padding (FAQ, pitch, footer links).

Suggestions

Replace the descriptive bullets with the actual operational content: the EAA scope decision tree (service categories, micro-enterprise exemption, disproportionate-burden route), the WCAG 2.1 AA testing procedure per category (keyboard, screen reader, zoom/reflow, automated scanning), and the accessibility statement structure.

Ship the claimed bundle — the reusable checklist of the 50 A/AA success criteria, remediation report template, and statement template — as files in references/ and link to them explicitly from the body, instead of noting they are 'not in this folder'.

Delete the FAQ section, 'Why use this', and the promotional footer links, which restate the description and consume token budget without adding instructions.

DimensionReasoningScore

Conciseness

Noticeably padded: the five-question FAQ section, "Why use this", and the closing promotional links ("More skills, including the paid catalog") restate the description and add no operational value, and time-sensitive dates ("applies from June 2025", "before the June 2025 deadline") are stated outside any deprecated/old-patterns section. Matches anchor 2 'several unnecessary explanations or padded sections'; not 3 because well over a third of the body is marketing filler rather than occasional tighten-able sentences.

2 / 5

Actionability

The body only describes capabilities ("Walks a decision tree", "Runs the full WCAG 2.1 AA audit across all 50 A and AA success criteria") without any decision tree, testing steps, commands, code, or statement template, and it admits "Scripts, extension source, and templates from the original package are not in this folder". This matches anchor 1 'only describes rather than instructs'; not 2 because there are not even high-level executable hints — no step, tool, or command is given anywhere.

1 / 5

Workflow Clarity

The "What it does" bullets imply a rough sequence (scope memo → audit → remediation report → statement → re-run checklist), matching anchor 2 'Rough sequence present but many gaps; steps poorly defined; validation absent'. Not 1 because a recognizable order exists; not 3 because no step is defined in executable terms and there are no checkpoints or validation steps anywhere.

2 / 5

Progressive Disclosure

The body claims a multi-file bundle ("Ships the reusable checklist core", "Scripts, extension source, and templates from the original package are not in this folder") but no references/, scripts/, or assets/ directories exist, so the detailed content has nowhere to live and navigation to it is impossible. Matches anchor 2's 'minimal structure' end; not 3 because the problem is not organization of inline content but that the promised reference layer is entirely absent.

2 / 5

Total

7

/

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 description: concrete third-person capability statement with named deliverables, an explicit multi-clause 'Use when' trigger list, and a well-differentiated EU accessibility niche. The only weakness is modest synonym coverage (no 'EAA', 'EN 301 549', or 'a11y' phrasing).

DimensionReasoningScore

Specificity

Quotes: "Audits a website or app against the European Accessibility Act and WCAG 2.1 AA, producing a scope memo, remediation report, and accessibility statement" — multiple concrete actions with named deliverables, in third person. Matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; it is not score 4 because there are no meaningful coverage gaps within its stated domain.

5 / 5

Completeness

Explicitly answers both: what ("Audits... producing a scope memo, remediation report, and accessibility statement") and when ("Use when: Determine if a business falls under European Accessibility Act scope; Perform a full WCAG 2.1 AA audit...; Create prioritized remediation reports..."). Matches anchor 5 with concrete trigger phrases; not 4 because the 'when' is explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

Natural triggers include "European Accessibility Act", "WCAG 2.1 AA", "audit", "remediation report", and "accessibility statement" — the exact phrases a user needing this skill would say. It is not 5 because common variations like "EAA", "EN 301 549", "a11y", and "accessibility compliance" are missing; not 3 because the core keyword coverage is strong rather than partial.

4 / 5

Distinctiveness Conflict Risk

Clear niche — EU accessibility law (Directive-based EAA scope plus WCAG 2.1 AA auditing) — with distinct trigger terms unlikely to fire for unrelated skills. Matches anchor 5 'Clear niche with distinct triggers; minimal conflict risk'; not 4 because the EU-specific legal framing leaves virtually no overlap with generic web-audit or ADA-focused skills.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-web-audits/skills/nex-eu-accessibility-audit/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.