Published: Last updated:

WCAG and the European Accessibility Act

Accessibility has two faces. The Web Content Accessibility Guidelines (WCAG) by the W3C are the technical norm: with the four POUR principles and the conformance levels A, AA and AAA they describe when digital content is accessible. The European Accessibility Act (EAA, Directive (EU) 2019/882) is the legal act: it makes accessibility mandatory for certain products and services and has applied since 28 June 2025. Norm and law interlock, but they are not the same thing.

Two layers, cleanly separated

Anyone tackling accessibility quickly conflates two things that belong apart. One layer is a technical norm: a voluntary, vendor-neutral set of rules that defines when a website, an app or a document is accessible. The other layer is a legal act: a law that makes that accessibility binding for a defined scope and backs it with oversight and sanctions. The WCAG are the norm; the EAA is the law. This page describes the norm first, then the law, then the hinge between them, and finally the Swiss angle. The technical testing side, that is how accessibility is verified inside the development process, is covered by Quality Assurance.

The norm: WCAG by the W3C

The WCAG are developed by the World Wide Web Consortium (W3C) within the Web Accessibility Initiative (WAI). They are a W3C Recommendation, not a law; their binding force arises only because laws and contracts reference them. The current version is WCAG 2.2, published as a W3C Recommendation on 12 December 2024. Versions 2.0, 2.1 and 2.2 coexist; 2.2 is backwards-compatible and adds to the earlier success criteria without replacing them.

The scaffold of the WCAG is four principles, in short POUR:

  • Perceivable. Information and interface components must be presented so that users can perceive them, for example text alternatives for images or sufficient contrast.
  • Operable. Operation must be possible without a mouse, that is fully via keyboard and without timing traps.
  • Understandable. Content and operation must be understandable, with clear language and predictable behaviour.
  • Robust. Content must work reliably with current and future technology, in particular with assistive technologies such as screen readers.

Each principle breaks down into success criteria assigned to three conformance levels:

  • Level A is the baseline. If these criteria are violated, the content is simply inaccessible to some user groups.
  • Level AA is the practical target. It is the benchmark that most laws and procurement rules refer to.
  • Level AAA is the highest level. It is not fully attainable for all content and is therefore rarely required across the board.

The law: European Accessibility Act

The EAA is an EU directive that aims to unify the internal market for accessible products and services by aligning divergent national rules. Unlike the WCAG it is not a technical guideline but a legal act with a defined scope. It covers an explicit list, including computers and operating systems, smartphones, ATMs and ticketing machines, e-books, electronic commerce (e-commerce), consumer banking services as well as certain telecommunications and transport services.

The directive was adopted in 2019; its requirements apply, under Article 31 of the directive, since 28 June 2025. As an EU directive the EAA does not act directly but through the Member States' national transposition laws; detail rules such as transition periods or the exemption for microenterprises providing services follow from those national laws and the directive itself. Important for the distinction: the EAA does not write a specific WCAG version label into its legal text but requires accessibility functionally; the concrete technical yardstick is supplied by the downstream harmonised standard.

The hinge: EN 301 549

Between norm and law sits the European harmonised standard EN 301 549. It is the bridge that connects the functional law with the technical norm: according to the W3C, EN 301 549 adopts the WCAG for web content and extends them with requirements for software, documents and hardware. Which WCAG version is the yardstick depends on the context: for the Web Accessibility Directive, EN 301 549 v3.2.1 references WCAG 2.1 Level AA, whereas the W3C now cites WCAG 2.2 for the European Accessibility Act context. Meeting the harmonised standard satisfies the corresponding legal requirements (a presumption of conformity). This produces the chain shown below:

flowchart TD
    A["WCAG (W3C)<br/>POUR, levels A/AA/AAA"] --> B["EN 301 549<br/>harmonised EU standard"]
    B --> C["European Accessibility Act<br/>Directive (EU) 2019/882"]
    C --> D["national transposition laws<br/>of the EU Member States"]
    A --> E["Switzerland: BehiG<br/>+ WCAG as reference"]

The diagram deliberately separates the layers: on the left the technical norm (WCAG), in the middle the harmonised standard as translator (EN 301 549), on the right the legal act (EAA) with its transposition into national law. The Swiss line branches directly off the norm because it does not run through the EAA. The arrows show the direction of reference, not a chronological order.

The reach of an accessible offering

An accessible offering widens an organisation's reach and can at the same time travel beyond the national border. Domestically the governing law for this is the Disability Discrimination Act (BehiG), which regulates the equality of people with disabilities; its digital accessibility duties address the federal government and bodies close to the state and do not reach the EAA scope for the private sector. The WCAG serve as the recognised technical reference here; the Swiss specialist agency Access for All cites WCAG 2.1 at Level AA. Switzerland is not part of the EU internal market, so the EAA does not bind Swiss actors directly; an indirect effect nonetheless remains: a Swiss provider offering covered products or services in the EU market, for example through an e-commerce shop for EU customers, can fall within scope through the national transposition laws. This market-based reach structurally resembles the output-in-the-EU trigger that the EU AI Act page describes for AI; here, however, it is tied to the specific national transposition law and must be checked case by case. Where an accessible offering also processes personal data, data protection applies in parallel, and for an EU nexus the GDPR; the wider legal frame is collected in the standards hub.

Where accessibility breaks in practice

  • AAA as a misconception. Demanding Level AAA wholesale misses the point; AAA is not fully attainable for all content. AA is the dependable target.
  • Audit instead of process. A one-off conformance report goes stale with the next release. Accessibility is an ongoing part of Quality Assurance, not a final certificate.
  • Overlay tools. Bought-in overlay scripts promise conformance at the push of a button but do not fix the underlying defects and can even disrupt operation with assistive technology.
  • Wired in late at the CMS. Accessibility belongs in the templates and components of the content management system. An accessible CMS such as Contao takes a lot off the editorial workload; patching individual pages afterwards does not scale.

References

Related topics

  • Quality Assurance, the technical testing side that accessibility belongs in as a test dimension.
  • EU AI Act, a second EU legal act with market-based reach across the EU border.
  • GDPR, the data protection law that applies in parallel for personal-data offerings.
  • Standards, the standards hub with the wider legal and normative frame.

Ask AI

These links open external AI services, the conversation and its content are sent to their providers.