European Accessibility Act: Color Contrast Requirements

Under the European Accessibility Act, color contrast compliance means meeting EN 301 549, which adopts WCAG 2.1 Level AA: at least 4.5:1 for normal text, 3:1 for large text, and 3:1 for icons, controls and meaningful graphics. Those obligations have applied across the EU since 28 June 2025.

This guide is general information, not legal advice.

How the EAA reaches your color choices

The EAA is Directive (EU) 2019/882. It sets functional accessibility requirements for products and services sold to EU consumers and leaves the technical detail to harmonised standards. The standard for ICT is EN 301 549, whose web chapter (9) and software chapter (11) copy WCAG 2.1 Level AA almost verbatim. Meet EN 301 549 and you are presumed to meet the EAA; the contrast criteria are 1.4.3 (text), 1.4.11 (non-text) and 1.4.6 is not required.

Coverage is by sector, not by company size alone: e-commerce sites and apps, consumer banking, transport ticketing and information, e-books and readers, telecoms, and the operating systems and devices people use to reach them. A US SaaS company selling subscriptions to EU consumers is in scope. Micro-enterprises offering services are exempt. Each member state names its own enforcement body and penalties, so check the national transposition where you sell.

The United Kingdom is not bound by the EAA, but UK sellers into the EU are. Domestically, the Equality Act 2010 requires reasonable adjustments, and the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 require public bodies to meet EN 301 549 / WCAG 2.1 AA and publish an accessibility statement. Same numbers again.

The exact WCAG numbers

• 4.5:1 for normal text (Success Criterion 1.4.3, Level AA).
• 3:1 for large text: 14pt (about 18.66px) bold, or 18pt (24px) regular.
• 3:1 for UI components and meaningful graphics such as icons, input borders, focus rings and chart lines (1.4.11, Level AA, added in WCAG 2.1).
• 7:1 and 4.5:1 at Level AAA (1.4.6); not required by any of the laws discussed here.
• Logos and purely decorative text are exempt; disabled controls are exempt.

Real pairs, measured

Mistakes that fail EN 301 549 audits

• Cookie consent banners with low-contrast "reject" links, the first thing every EU auditor opens.
• Dark-mode themes designed after the light theme and never measured separately.
• Checkout progress indicators where the current step is shown by color only.
• Mobile apps tested on the web build only; chapter 11 applies to native apps too.
• Yellow or light-orange brand colors used behind white text at under 2:1.

Enforcement and what auditors actually test

Each member state transposed the EAA into national law and named a market surveillance authority. Those authorities can request a conformity assessment, order corrective action and, under national law, impose penalties; the scale varies by country, so check the transposition where you trade. Consumers and disability organisations can also complain directly. In an assessment, testers run automated tools first, and contrast failures are the bulk of what those tools find, so a measured contrast report shortens the whole process.

The EAA also requires an accessibility statement describing how the service meets the requirements. Listing your measured text and background pairs in that statement is the simplest way to show the contrast criteria are handled, and it is the same evidence UK public bodies must publish under the 2018 regulations.

Choosing EAA-safe brand colors

Yellow, orange and light blue brand colors are the usual trouble: they cannot carry white text and often cannot carry dark text at 4.5:1 either. The fix is role assignment, not a rebrand. Use the bright color for backgrounds behind dark text that has been measured, for icons at 3:1, and for large headings; derive a darker shade of the same hue for links and small text. For dark mode, measure the dark theme separately; a gray that passes on white rarely passes on near-black. Keep one documented pair per role and reuse it across web, iOS and Android, since EN 301 549 chapter 11 covers native apps with the same numbers.

Edge cases

• Cookie and consent dialogs are in scope; the reject option must be as readable as accept.
• Text on images and gradients: test against the extreme pixels or add a solid overlay.
• Placeholders count as text; disabled controls are exempt.
• Logos are exempt; brand colors used as link text are not.
• Micro-enterprise exemption applies to services only, and only while you stay under the thresholds.

How to check your site

1. List every text style and its background: body, secondary, links, buttons, placeholders, footer, error and success states, dark mode if you have one.
2. Paste each pair into the contrast checker. It reports the ratio and AA/AAA status for normal and large text.
3. For pairs that fail, keep the hue and move only the lightness until the ratio passes. The palette generator shows tints and shades of your brand color so you can pick the nearest passing one.
4. If the brand colors came from a logo or mockup, pull the exact values with the image extractor rather than eyeballing them.
5. Check icons, borders and focus rings against their adjacent colors for 3:1.
6. Record the results. A dated table of pairs and ratios is the evidence an auditor, regulator or opposing counsel will ask for.

Because the EAA is enforced per country, keep one measured contrast report for the whole product and attach it to your accessibility statement. The same report satisfies the UK public-sector regulations and the ADA in the US.