CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

section-508

Expert Section 508 compliance advisor for US federal ICT accessibility. Use this skill whenever a user asks about Section 508, WCAG 2.0/2.1 AA for federal systems, VPAT or Accessibility Conformance Reports (ACR), accessibility audits, remediation planning, PDF accessibility, web or software accessibility, mobile accessibility, federal procurement accessibility requirements, contractor obligations, undue burden exceptions, assistive technology compatibility, or Section 508 testing. Covers the Revised Section 508 Standards (2018), all WCAG 2.0 Level AA success criteria, the four POUR principles, testing methodologies, and agency compliance workflows. Trigger even if the user doesn't say "skill" — any Section 508 or ICT accessibility question for federal systems should use this skill.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, highly actionable advisory skill body with precise regulatory citations, named testing tools, and clearly sequenced workflows. Its main inefficiency is the ~80-line inline WCAG 2.0 A/AA criterion tables, which restate knowledge Claude already has and overlap with the existing references/wcag-mapping.md bundle file.

Suggestions

Move the four POUR success-criterion tables out of SKILL.md and into references/wcag-mapping.md (which already maps those criteria to Section 508 provisions and failure patterns), keeping only the principle names and a pointer in the body.

Add an explicit validation/re-test step to the Accessibility Audit workflow (e.g., 're-verify each remediated criterion and update the issue table before finalizing the report') to close the feedback loop.

Replace the exhaustive criterion enumeration with the most common failure patterns per principle and rely on the reference file for the full list, cutting roughly half the body's token cost.

DimensionReasoningScore

Conciseness

The regulatory and workflow sections are dense and valuable, but roughly half the body consists of full WCAG 2.0 A/AA success-criterion tables (e.g., '1.4.3 Contrast (Minimum) | AA | Text/images-of-text: 4.5:1 contrast') that restate standard knowledge Claude already has and duplicate material already in references/wcag-mapping.md. This fits the score-3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') more than score 2, since the padding is one large redundant block rather than pervasive fluff.

3 / 5

Actionability

Guidance is concrete and executable throughout: a task-to-output-format table, named tools ('axe-core, Lighthouse, WAVE', 'NVDA + Chrome', 'Colour Contrast Analyser'), exact citations ('FAR Clause 52.239-2', 'E205', '36 CFR Part 1194', 'SC 1.4.3'), and specific thresholds ('Critical... 30 days; High... 60 days; Medium... 90 days'). Per the rubric's code-vs-instruction note, absence of code is not penalized; the specific guidance covers the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

Multi-step processes are clearly numbered and sequenced (VPAT steps 1–5, audit steps 1–7, undue burden steps 1–6) with some checkpoints present ('Document results per criterion with element references and screenshots', 'Retain documentation for audit; re-evaluate when ICT is next updated'). It is not a 5 because validation is implicit in places — e.g., the audit workflow lacks an explicit re-test/verify-fixes feedback loop and the VPAT workflow has no confirmation step before issuing conformance levels; it is above 3 because sequences are complete and mostly checkpointed.

4 / 5

Progressive Disclosure

Structure is good: a 'Reference Files' section clearly signals the single one-level-deep reference ('references/wcag-mapping.md — Complete WCAG 2.0 AA success criteria with Section 508 provision cross-references...'), which exists and nests no further. It is not a 5 because the body inlines reference-grade material — the full WCAG SC tables — that should be split into the reference file (whose charter already covers it), leaving SKILL.md as a true overview.

4 / 5

Total

16

/

20

Passed

Description

91%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, third-person description with explicit what/when triggers, rich natural keyword coverage including synonyms (VPAT/ACR), and a clearly scoped federal niche. The only weaknesses are nominal rather than verbal capability statements and a few broad accessibility trigger phrases that lack the federal qualifier.

DimensionReasoningScore

Specificity

The description names the role ('Expert Section 508 compliance advisor') and enumerates many concrete task areas ('VPAT or Accessibility Conformance Reports (ACR), accessibility audits, remediation planning, PDF accessibility... federal procurement accessibility requirements'), giving several specific actions with only minor coverage gaps. It falls just short of a 5 because capabilities are stated as topic nouns rather than explicit action verbs, and the coverage list is broad rather than comprehensive about what outputs are produced.

4 / 5

Completeness

Both 'what' ('Expert Section 508 compliance advisor for US federal ICT accessibility... Covers the Revised Section 508 Standards (2018), all WCAG 2.0 Level AA success criteria') and 'when' ('Use this skill whenever a user asks about...', reinforced by 'Trigger even if the user doesn't say "skill"') are explicitly answered with concrete trigger phrases. This matches the score-5 anchor exactly; the score-4 anchor's 'when could be more explicit' does not apply here.

5 / 5

Trigger Term Quality

Trigger terms are comprehensive and natural — users would literally say 'Section 508', 'WCAG', 'VPAT', 'accessibility audit', 'remediation planning', 'PDF accessibility', and 'Section 508 testing', with synonyms included ('Accessibility Conformance Reports (ACR)', 'assistive technology compatibility'). It clearly matches the top anchor's 'comprehensive coverage of natural terms including synonyms' rather than the score-4 anchor, which expects missing natural terms.

5 / 5

Distinctiveness Conflict Risk

The federal-ICT niche is clear and mostly distinct ('US federal ICT accessibility', 'Revised Section 508 Standards (2018)'), but the broad trigger phrases 'web or software accessibility, mobile accessibility' appear without a federal qualifier in the trigger list, creating minor overlap risk with a general WCAG/web-accessibility skill. Not a 5 because that residual conflict risk with closely related skills is real; not a 3 because the overall framing is unmistakably Section 508-specific.

4 / 5

Total

18

/

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

Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

Path

plugins/section-508/skills/section-508/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.