mcpField
L
legal-compliance-mapping

legal-compliance-mapping

github.com/community-accessOther429129 installsUpdated today
Repository

About legal-compliance-mapping

Legal Compliance Mapping Skill organizes accessibility laws and standards across jurisdictions. It is intended for compliance-mapping agents and report generators, with comparisons covering scope, WCAG alignment, enforcement, VPAT mappings, and statement requirements.

Key features

  1. 01Jurisdiction and framework comparisons
  2. 02WCAG version and scope mapping
  3. 03Non-WCAG requirements reference
  4. 04VPAT edition and conformance mapping
  5. 05Accessibility statement requirements

Use cases

  1. 01Comparing accessibility obligations across regions
  2. 02Mapping a product to VPAT standards
  3. 03Preparing accessibility statement requirements

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/community-access/accessibility-agents --skill legal-compliance-mapping

After installing, type/legal-compliance-mappingin Claude Code to confirm it loaded.

Details

From the project README

Legal Compliance Mapping Skill

Maps accessibility legal frameworks across jurisdictions. Used by compliance-mapping agent and any agent generating compliance reports.


Framework Comparison

FrameworkJurisdictionWCAG VersionScopeEnforcement
Section 508 (Revised)US (Federal)WCAG 2.0 AAFederal agencies and their ICTAdministrative complaints, lawsuits
ADA Title IIUS (State/Local)WCAG 2.1 AA (DOJ 2024 rule)State and local government websitesDOJ enforcement, lawsuits
ADA Title IIIUS (Private)No explicit WCAG version; courts use 2.0/2.1 AAPublic accommodationsPrivate lawsuits, DOJ enforcement
EN 301 549 v3.2.1EUWCAG 2.1 AA (Chapter 9-11)Public sector + private sector ICTEU member state enforcement
European Accessibility Act (EAA)EUWCAG 2.1 AA (via EN 301 549)Private sector products and services (June 2025)Market surveillance, fines
AODAOntario, CanadaWCAG 2.0 AAOntario organizations (50+ employees)Administrative penalties
Accessible Canada ActCanada (Federal)WCAG 2.1 AA (guidance)Federally regulated entitiesCRTC/CTA enforcement, penalties
Israeli Standard 5568IsraelWCAG 2.0 AAPublic websites and appsCivil lawsuits
JIS X 8341-3:2016JapanWCAG 2.0 AAGovernment websites (recommended)No enforcement (voluntary)
Chinese GB/T 37668-2019ChinaBased on WCAG 2.0Government websitesAdministrative guidance

Additional Non-WCAG Requirements

Some frameworks require more than WCAG conformance:

EN 301 549 Additional Requirements
ChapterRequirementBeyond WCAG
Chapter 5Closed functionality (kiosks, ATMs)Yes — no WCAG equivalent
Chapter 6Real-time text (RTT) communicationYes — no WCAG equivalent
Chapter 7Video capabilities (captions, audio description)Extends WCAG 1.2
Chapter 8Hardware accessibilityYes — physical product requirements
Chapter 10Non-web documentsMaps WCAG to document formats
Chapter 11Non-web softwareMaps WCAG to native applications
Chapter 12Documentation and support servicesAccessible help documentation
Chapter 13ICT providing relay or emergency servicesYes — no WCAG equivalent
European Accessibility Act Additions
  • Products: computers, smartphones, tablets, self-service terminals, e-readers
  • Services: e-commerce, banking, transport, telephony, audiovisual media
  • Microenterprises (<10 employees, <€2M turnover) exempt from service requirements
  • Deadline: June 28, 2025 for new products/services

VPAT / ACR Mapping

The Voluntary Product Accessibility Template (VPAT) maps to three standards:

VPAT EditionStandards Covered
VPAT 2.5 Section 508Revised Section 508 (WCAG 2.0 AA)
VPAT 2.5 EUEN 301 549 (WCAG 2.1 AA + Chapters 5-13)
VPAT 2.5 INTSection 508 + EN 301 549 + WCAG 2.x

Conformance levels in VPAT:

  • Supports — fully meets the criterion
  • Partially Supports — some functionality meets, some does not
  • Does Not Support — majority of functionality does not meet
  • Not Applicable — criterion is not relevant to the product

Accessibility Statement Requirements

W3C Model (Voluntary)
  • Conformance status (Fully conformant / Partially conformant / Non-conformant)
  • WCAG version and level targeted
  • Known limitations with workarounds
  • Assessment approach (self, external, automated tools)
  • Feedback mechanism with response commitment
  • Date of statement and last review
EU Model (Required for Public Sector)

All of the above, plus:

  • Disproportionate burden declaration (if applicable, with justification)
  • Link to national enforcement body
  • Annual review requirement
  • Date of last accessibility audit

Compliance Timeline Quick Reference

EventDateImpact
Section 508 RefreshJanuary 2018Adopted WCAG 2.0 AA for federal ICT
EU Web Accessibility DirectiveSeptember 2018 (new sites), September 2020 (existing)Public sector websites and mobile apps
ADA Title II WCAG 2.1 RuleApril 2026 (large), April 2027 (small)State/local government web content
European Accessibility ActJune 2025Private sector products and services
AODA Full ComplianceJanuary 2021Ontario organizations 50+ employees

Comments

Markdown supported