wcag-build
Skill4 starsChanged 5 days agoMITView on GitHub
Implement accessible UI and remediate WCAG 2.2 (default) or 2.1 criteria: forms, authentication, focus, pointer targets, gestures, media, semantic components, responsive behavior and assistive technology.
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-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-validateSkill
- wcag-visual-and-responsiveSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Start with the user task and real component states.
- Distinctive: line 15
Prefer accessible semantic HTML and tested built-in controls.
- Distinctive: line 18
Run focused unit/component tests, then browser interaction/AT checks for behavior that cannot be inferred statically.
≈ “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
Build and remediate accessible UI with versioned requirements
Scope
Resolve the target version and level using ../wcag-diagnose/references/standard-selection.md before coding. Default WCAG 2.2 AA, unless explicit user/contract/project policy differs. W3C normative source controls; consult the selected 2.2/criteria.json or 2.1/criteria.json, remediation recipes and matching specialist playbooks.
Procedure
- Start with the user task and real component states. Choose the applicable SC set; do not silently import 2.2 criteria into an explicit 2.1 project.
- Prefer accessible semantic HTML and tested built-in controls. Implement keyboard, mouse, touch, screen-reader information, responsive reflow, forms, loading, errors and recovery—not static appearances only.
- Under WCAG 2.2 AA, consider focus obscuration (2.4.11) with sticky UI; non-drag alternatives (2.5.7); 24 CSS-px target size or valid exceptions (2.5.8); help placement consistency (3.2.6); redundant form entry (3.3.7); and accessible authentication (3.3.8). For AAA check enhanced variants (2.4.12, 2.4.13, 3.3.9).
- Consult
references/implementation-contracts.mdplus focused specialist playbooks. Cover every required state and avoid adding ARIA as a substitute for correct interaction. - Run focused unit/component tests, then browser interaction/AT checks for behavior that cannot be inferred statically. Do not weaken automated rules to obtain a green scan.
- Report exact selected SC, implemented change, tests and any manual gap. A valid design/implementation decision is not a conformance certificate. Optional WCAG 3.0 draft exploration is an advisory design backlog, never a requirement or release gate.
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.