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 strong, expert-level compliance skill body with exceptionally concrete and executable guidance, well-sequenced workflows, and a properly structured single reference file. Its main weakness is token efficiency: the full inline WCAG 2.0 criteria tables duplicate both Claude's prior knowledge and the reference file, and workflows lack explicit validation/re-test checkpoints.

Suggestions

Replace the four inline POUR criteria tables (~55 lines) with a one-line summary (e.g., "All WCAG 2.0 Level A/AA criteria apply; see references/wcag-mapping.md for per-criterion failures, testing, and 508 provision cross-references") since the reference file already covers this in more depth.

Add explicit validation checkpoints to the workflows: e.g., after remediation, "re-test each fixed criterion and update the issue table status"; after VPAT completion, "cross-check every Supports claim against documented test evidence."

Consolidate the scattered time-sensitive material (Last verified date, November 2026 status check, FY2025 assessment figures, 2026 compliance-date extensions) into a single clearly labeled "Current status" section so stale facts are easy to locate and update.

DimensionReasoningScore

Conciseness

The body is dense and tabular with no padded prose, but the ~55-line inline enumeration of every WCAG 2.0 A/AA success criterion (lines 75–130) restates knowledge Claude already has and duplicates the detail already provided in references/wcag-mapping.md. Scattered time-sensitive dates ("Last verified: 2026-11-06", the November 2026 status check, FY2025 figures) add further tokens that could be consolidated.

3 / 5

Actionability

Guidance is fully concrete for an instruction-only skill: named tools (axe-core, NVDA, JAWS, VoiceOver, TalkBack, Colour Contrast Analyser), exact citations (E205, E302.1, FAR 52.239-2, SC 1.4.3), specific conformance levels, remediation SLAs with day counts, and an exact VPAT 2.x table structure. A user could execute any workflow directly from this text.

5 / 5

Workflow Clarity

The VPAT, audit, PDF, procurement, and undue-burden workflows are clearly numbered and well-sequenced (e.g., audit steps 1–7, undue burden steps 1–6). However, explicit verification checkpoints are missing — no re-test step after remediation and no consistency check after VPAT completion — though these are advisory workflows, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Good structure with a clearly signaled, one-level-deep reference ("references/wcag-mapping.md — Complete WCAG 2.0 AA success criteria with Section 508 provision cross-references, common failure patterns, and automated testing coverage") that exists and delivers the promised depth. The gap is that the inline criteria tables overlap the reference file's content rather than being fully offloaded to it.

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.

An excellent description that clearly and explicitly states both capability scope and trigger conditions with comprehensive, natural keyword coverage including synonyms. Its only weaknesses are topic-framed rather than action-framed capability listing and a few unqualified broad trigger terms that create minor overlap risk with general accessibility skills.

DimensionReasoningScore

Specificity

It lists several specific task areas — "accessibility audits, remediation planning, PDF accessibility, ... federal procurement accessibility requirements, contractor obligations, undue burden exceptions" — with concrete scope ("Revised Section 508 Standards (2018), all WCAG 2.0 Level AA success criteria"). It falls short of anchor 5 because capabilities are framed as topics the user asks about rather than actions the skill performs (no verb-first list like "completes VPATs, audits sites, drafts RFP clauses").

4 / 5

Completeness

It explicitly answers both questions: what ("Expert Section 508 compliance advisor ... 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") and when ("Use this skill whenever a user asks about ..." plus "Trigger even if the user doesn't say 'skill'"), matching the anchor-5 pattern of concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms and variants: "Section 508, WCAG 2.0/2.1 AA for federal systems, VPAT or Accessibility Conformance Reports (ACR), accessibility audits, ... assistive technology compatibility, or Section 508 testing." These are exactly the phrases a user with this need would say, including the VPAT/ACR synonym pair.

5 / 5

Distinctiveness Conflict Risk

The federal-ICT niche is clear and its signature triggers (Section 508, VPAT/ACR, undue burden, E-provisions) are highly distinct. Minor overlap risk remains with a general web-accessibility or WCAG skill because the trigger list includes unqualified broad terms like "web or software accessibility, mobile accessibility" — closer to anchor 4 than anchor 5.

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.