Costa Rica
- Legal frameworkLaw 7600 and Directive 036-MTSS-MICITT
- Technical referenceWCAG 2.1 AA (2024 guidelines reference WCAG 2.2)
- Key pointPublic sector institutions must make their websites and digital services accessible.
Compliance and standards
Legal and regulatory compliance in digital accessibility.
We use international technical standards as a reference to help organizations understand their obligations and reduce barriers.
Last updated: November 2026
Regional overview
United States
- Legal frameworkADA (Titles II and III) and Section 508
- Technical referenceWCAG 2.1 AA (ADA Title II) · WCAG 2.0 AA (Section 508) · VPAT
- Key pointState and local governments must comply with the ADA Title II rule by April 26, 2027 (50,000+ population) or April 26, 2028 (smaller entities).
Canada
- Legal frameworkAccessible Canada Act (ACA) and AODA (Ontario)
- Technical referenceWCAG 2.0 AA (AODA) · CAN/ASC-EN 301 549
- Key pointFederal and provincial frameworks apply to public bodies and many private organizations.
Europe
- Legal frameworkEuropean Accessibility Act (EAA) and EN 301 549
- Technical referenceWCAG 2.1 AA through EN 301 549
- Key pointThe EAA has applied since June 28, 2025 to covered products and services, including e-commerce, banking and transport.
VPAT / ACR
A VPAT describes a product’s accessibility conformance and, after an assessment, can become part of an Accessibility Conformance Report (ACR). It is especially relevant in B2B sales and public procurement, where accessibility evidence is requested.
This is not legal advice
This page is a general summary for information purposes. Obligations depend on each jurisdiction, product and organization, and laws change. Consult a lawyer for your specific case. See our terms of use.
WCAG as a common technical baseline
Unified strategy
Designing to WCAG 2.1 or 2.2 AA can provide a common technical baseline, but legal compliance depends on the jurisdiction, product, organization and applicable obligations.
Continuity
Accessibility should be built into the whole lifecycle: design, development, QA, launch, maintenance and retesting.
Frequently asked questions
Does an accessibility statement protect me from lawsuits?
Not by itself. A public statement can demonstrate good faith, but it does not replace an accessible product.
Does an automated accessibility overlay make a site legally compliant?
No. Overlay tools do not replace source-code fixes, DOM structure or testing with assistive technologies.
How often should compliance be validated?
Accessibility is an ongoing process. Review after major redesigns, new functionality and periodically.