Estonia accessibility law: PIA + EAA explained

Who has to comply

Public-sector since 2018; consumer services from 28 June 2025.

Estonia is the EU's most digitally advanced small state, where e-government and online services are near-universal and consumer expectations of digital quality are high. Under the EAA-implementing legislation extending the Public Information Act, a foreign store selling to Estonian consumers is covered on the country-of-consumption basis. An Estonian-language accessibility statement is expected, and Estonia's digitally literate consumers are quick to notice and report obvious accessibility failures.

What the law actually requires

The technical baseline is WCAG 2.1 Level AA via EN 301 549. EN 301 549 references WCAG 2.1 Level AA in full and adds a few requirements specific to mobile apps and documents. Beyond the technical bar, Estonia requires the following operational items, which auditors check first because they are simple to verify:

• EN 301 549 / WCAG 2.1 AA

• Estonian-language statement

Penalties and how enforcement actually works

Administrative penalties under EAA implementation.

Enforcement runs through the Ministry of Economic Affairs and Communications, extending Estonia's long-standing public-sector accessibility posture to covered private services. Estonia's approach is centralised and complaint-driven, backed by administrative penalties under the EAA implementation. Given the country's mature digital-government culture, the regulator is comfortable with technical evaluation, but the practical first-cycle focus still falls on visible failures and the presence of a proper Estonian-language statement.

Practical first steps for a Estonia site

If you are starting now and want to land before enforcement, run an automated audit, fix the high-impact issues (contrast, labels, keyboard, focus), publish an accessibility statement, and set up a feedback inbox. That sequence covers 80% of what auditors look for in a first sweep.

• Run a baseline scan to know your current score

• Fix critical and serious issues in priority order — these are the ones cited in complaints

• Publish a public accessibility statement on a stable URL (Estonia regulators expect this discoverable)

• Add a feedback channel and answer within the country-specified window

• Re-scan after every major release; track regressions