wcag-validate
Skill4 starsChanged 5 days agoMITView on GitHub
Validate WCAG 2.2 (default) or 2.1 audit evidence with automated, keyboard, touch, zoom and assistive technology checks; detect incorrect version/level mixes and report incomplete manual reviews.
In this repository55 other files it gives its agents.
- design-balance-and-proportionSkill
- design-brand-and-art-directionSkill
- design-buildSkill
- design-color-theorySkill
- design-diagnoseSkill
- design-hierarchy-and-emphasisSkill
- design-imagery-and-textureSkill
- design-layout-and-gridSkill
- design-movement-and-flowSkill
- design-reviewSkill
- design-rhythm-and-patternSkill
- design-typographySkill
- design-unity-and-systemsSkill
- design-validateSkill
- security-api-files-and-realtimeSkill
- security-authentication-and-sessionsSkill
- security-authorizationSkill
- security-browser-and-originSkill
- security-buildSkill
- security-configuration-and-secretsSkill
- security-crypto-and-dataSkill
- security-dependencies-and-buildSkill
- security-diagnoseSkill
- security-injection-and-validationSkill
- security-logging-and-failureSkill
- security-reviewSkill
- security-threat-model-and-designSkill
- security-validateSkill
- ux-accessibilitySkill
- ux-buildSkill
- ux-controls-and-inputsSkill
- ux-decisions-and-loadSkill
- ux-diagnoseSkill
- ux-feedback-and-performanceSkill
- ux-forms-and-errorsSkill
- ux-journeys-and-motivationSkill
- ux-navigation-and-structureSkill
- ux-onboarding-and-learningSkill
- ux-reviewSkill
- ux-trust-and-ethicsSkill
- ux-validateSkill
- ux-visual-hierarchySkill
- wcag-alternatives-and-mediaSkill
- wcag-assistive-tech-and-statusSkill
- wcag-buildSkill
- wcag-diagnoseSkill
- wcag-forms-and-error-preventionSkill
- wcag-keyboard-and-focusSkill
- wcag-language-and-predictabilitySkill
- wcag-navigation-and-discoverySkill
- wcag-pointer-and-touchSkill
- wcag-reviewSkill
- wcag-semantics-and-reading-orderSkill
- wcag-time-and-motionSkill
- wcag-visual-and-responsiveSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
If working in this distribution repository, run python scripts/check_wcag_audit.py path/to/report.json --json.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Validate WCAG 2.x evidence and version-specific audit coverage
Scope
Resolve selected WCAG 2.2 (default) or 2.1, conformance level and scope before testing (../wcag-diagnose/references/standard-selection.md). A target-selection decision is not proof that the target was met.
Procedure
- For full evaluations, use
../wcag-diagnose/references/evaluation-methodology-2.0.mdto check the documented scope, accessibility support baseline, representative sample rationale, complete processes, and untested areas; a sample must not be reported as whole-product conformance. Then load the selected standard's2.2/criteria.json/2.1/criteria.jsonand conformance catalog. At AA review 55 criteria for 2.2 or 50 criteria for 2.1. Do not mix versions or import 4.1.1 into 2.2. - For all required criteria, require
pass,fail,not_applicable,not_testedorneeds_manual_reviewwith evidence and N/A rationale. Differentiate incomplete from failed. - Combine automated scanners with keyboard, zoom, responsive, touch/drag alternatives, focus-occlusion, forms, authentication, screen-reader, media and content reviews. Read
references/manual-and-automation.mdand the appropriate specialist playbook. - Retest affected complete processes and all relevant states; test the non-interference conditions (1.4.2, 2.1.2, 2.3.1, 2.2.2) even for third-party content.
- If working in this distribution repository, run
python scripts/check_wcag_audit.py path/to/report.json --json. The script rejects invalid version/criterion combinations and checks report structure only; in a consuming repository, obtain or implement equivalent tooling rather than assuming this distribution script was installed. - Report verified scope, environment, date, selected version/level, failures and missing manual coverage. Do not assert certification. WCAG 3.0 Working Draft is advisory only and may never receive A/AA/AAA conformance outcomes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

