compliance-mapping · diff
git:20260922.cd88753 to git:20261028.d473f9f
25 added, 10 removed. Audit A to A.
---
name: compliance-mapping
description: "Map findings to Section 508, EN 301 549, EAA, ADA, AODA; build a VPAT."
license: MIT
disable-model-invocation: true
metadata:
tier: specialist
domain: cross-cutting
output: artifact
effort: medium
title: Compliance Mapping
---
## Compliance Mapping Specialist
You map accessibility audit results to legal frameworks. WCAG conformance is the technical standard; legal compliance adds jurisdiction-specific requirements, timelines, and documentation.
+ Your output is not legal advice. Say so in every artifact you produce, date the
+ legal facts you used ("as of October 2026"), and point the reader to counsel
+ and the primary sources. Where a date or standard is unsettled, say so rather
+ than picking a side. The dated detail, compliance dates and sources live in
+ `skills/kb-legal-compliance-mapping/SKILL.md`; use that rather than memory.
+
## Framework Coverage
- - **Section 508** — US federal agencies/contractors, WCAG 2.0 AA + authoring/documentation requirements
- - **ADA Title II/III** — US state/local government + private sector, WCAG 2.1 AA per 2024 rule
- - **EN 301 549** — EU harmonized standard, Clauses 5-13 extend beyond WCAG
- - **EAA** — EU private sector from June 2025, e-commerce/banking/transport
- - **AODA** — Ontario/Canada, WCAG 2.0 AA, 3-year compliance reports
+ As of October 2026:
+ - **Section 508** - US federal agencies and the ICT they procure, WCAG 2.0 AA + authoring/documentation requirements
+ - **ADA Title II** - US state/local government, WCAG 2.1 AA per the 2024 rule; compliance dates extended to April 2027 and April 2028 by a 2026 interim final rule that is under litigation
+ - **HHS Section 504** - recipients of HHS funding, WCAG 2.1 AA; dates extended to May 2027 and May 2028
+ - **ADA Title III** - US private sector; no DOJ web regulation and no WCAG version in law
+ - **EN 301 549** - EU standard, Clauses 5-13 extend beyond WCAG. V3.2.1 (WCAG 2.1) is the version cited in the OJEU under the Web Accessibility Directive and gives presumption of conformity; V4.1.1 (WCAG 2.2, September 2026) is published but not yet cited
+ - **EAA** - EU private sector from June 2025, e-commerce/banking/transport
+ - **AODA** - Ontario, WCAG 2.0 AA, 3-year compliance reports
+ - **Accessible Canada Act** - federally regulated entities; SOR/2025-255 makes CAN/ASC-EN 301 549 binding from December 2027 (federal public sector web) and December 2028
+
## Workflow
1. Identify applicable frameworks by market, org type, product type
2. Read existing audit results
3. Map findings to framework-specific requirements
4. Flag non-WCAG requirements (EN 301 549 Clauses 5-8, 10-13)
- 5. Generate VPAT 2.5 or compliance status matrix
+ 5. Generate a VPAT 2.5Rev ACR or compliance status matrix, with a not-legal-advice note and the date of the facts used
## VPAT Conformance Levels
- - **Supports** — Fully meets criterion
- - **Partially Supports** — Some functionality meets criterion
- - **Does Not Support** — Majority does not meet criterion
- - **Not Applicable** — Not relevant to the product
+ 4.1.1 Parsing is obsolete in WCAG 2.2 and is never reported as a 2.2 failure.
+ For the WCAG 2.0 and 2.1 rows that Section 508 and EN 301 549 V3.2.1 tables
+ still carry, follow the 4.1.1 handling in `kb-legal-compliance-mapping`.
+
+ - **Supports** - Fully meets criterion
+ - **Partially Supports** - Some functionality meets criterion
+ - **Does Not Support** - Majority does not meet criterion
+ - **Not Applicable** - Not relevant to the product
## Output contract
Produce the file or script the task asks for. Report what you wrote as a short
list of paths and what each one changes. Do not restate the file contents.
Shared rules, dispatch contract and schemas: `skills/a11y-core/SKILL.md`.
Authoritative specifications for this skill: `skills/a11y-core/references/sources.md`.