WCAG Compliance & Digital Accessibility Laws Worldwide

What WCAG is

WCAG (Web Content Accessibility Guidelines) is a technical standard from the W3C’s Web Accessibility Initiative that explains how to make digital content accessible for people with disabilities. WCAG is organised under four principles – Perceivable, Operable, Understandable, Robust – with testable Success Criteria at Levels A, AA, and AAA. Most laws and procurement rules worldwide aim for Level AA.

WCAG 2.2 Level AA at a glance

WCAG 2.2 became an official web standard on 5 October 2023. It keeps almost all of WCAG 2.0 and 2.1, adds nine Success Criteria, and retires 4.1.1 Parsing. Notable new Level AA items include:

• 2.4.11 Focus Not Obscured (Minimum): keyboard focus must not be hidden by fixed or sticky UI.
• 2.5.7 Dragging Movements: provide a simple pointer alternative to dragging.
• 2.5.8 Target Size (Minimum): ensure minimum size or spacing for interactive targets.
• 3.3.8 Accessible Authentication (Minimum): allow sign-in without cognitive tests; support copy–paste and password managers.

Tip: If you meet WCAG 2.2 AA, you also meet 2.1 and 2.0 by design. Use the latest version to future-proof work.

United Kingdom: Equality Act 2010 & PSBAR 2018

Equality Act 2010: organisations that provide goods or services must make reasonable adjustments so disabled people are not placed at a substantial disadvantage. This applies to websites and apps. The Act does not hard-code a technical standard, but WCAG 2.2 AA is the accepted benchmark for demonstrating reasonable steps.

Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 (PSBAR): UK public sector websites and apps must meet WCAG and publish an accessibility statement describing conformance and known issues.

European Accessibility Act (EAA) & 2025 updates

The EAA harmonises accessibility requirements for specific consumer products and services across EU member states, including e-commerce, e-books, banking, telecoms, transport ticketing and information, and self-service terminals such as ATMs and ticket machines.

• Enforcement: began on 28 June 2025. Each member state enforces via national law with its own procedures and penalties.
• Scope: non-EU companies offering in-scope services in the EU are included; some micro-enterprises may be exempt.
• Standards link: organisations typically reference EN 301 549 (historically mapping to WCAG 2.1), with updates expected to align with WCAG 2.2. Building to WCAG 2.2 AA is a practical way to stay ahead.

United States: ADA and current web rules

• ADA Title II (state and local government): a final rule issued in April 2024 requires conformance to WCAG 2.1 AA for web content and mobile apps, with compliance windows of two or three years from 24 April 2024 depending on entity size.
• ADA Title III (private sector): no single federal technical standard is mandated, but the DOJ recognises ADA obligations for websites and apps, and many settlements and courts look to WCAG 2.1/2.2 AA as the yardstick.

Practical checklist for global accessibility compliance

Strategy & governance

• Adopt a policy committing to WCAG 2.2 Level AA for web and mobile.
• Publish and maintain an accessibility statement with contact details for reporting issues.
• Include accessibility in procurement and contracts – in the EU, ensure vendors meet EN 301 549.

Design

• Meet colour contrast ratios, support text resizing, and show visible focus rings.
• Do not obscure keyboard focus with sticky headers or overlays.
• Ensure adequate target size/spacing; provide non-drag alternatives.
• Use clear headings, labels, and meaningful link text; keep navigation and help consistent.

Development

• Use semantic HTML; apply ARIA only when necessary.
• Ensure all controls are operable with a keyboard and have programmatic names.
• Provide text alternatives for images, captions and transcripts for media.
• Allow accessible authentication – support copy-paste and password managers.

Content & forms

• Write in plain language; provide clear instructions and error messages.
• Avoid asking users to re-enter information already provided in the same process.

Testing

• Combine automated scans with manual testing and assistive technology checks.
• Test keyboard-only, screen readers, magnification, and mobile orientation.
• Track issues and prioritise fixes by severity and user impact.

Operations & evidence

• Keep audit logs, decisions, and remediation plans to evidence reasonable adjustments.
• Offer an accessible feedback channel and respond promptly.
• Train designers, developers, editors, and product owners at least annually.

Quick law-by-law action points

• UK Equality Act 2010: demonstrate reasonable adjustments by conforming to WCAG 2.2 AA, documenting decisions, and offering alternative formats on request; public sector must also meet PSBAR and publish an accessibility statement.
• EU EAA (from 28 June 2025): confirm if your products/services are in scope; align builds and procurement with EN 301 549 and WCAG 2.2 AA; prepare to evidence conformity to the relevant national authority.
• US ADA: for public sector, plan to WCAG 2.1 AA per DOJ timelines; for private sector, target WCAG 2.2 AA to reduce legal risk and improve usability.

FAQs