Hungary accessibility law: Act LXXV/2018 + EAA explained

Who has to comply

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

Hungary is a mid-sized Central-European market where cross-border e-commerce, especially from neighbouring EU sellers, is significant. Under the EAA implementing act, a foreign store reaching Hungarian consumers is covered on the country-of-consumption basis. The specific catch is language: the accessibility statement must be available in Hungarian even when the service itself is multilingual, so cross-border sellers who publish only an English statement are non-compliant on that point alone.

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, Hungary requires the following operational items, which auditors check first because they are simple to verify:

• EN 301 549 / WCAG 2.1 AA

• Hungarian-language accessibility statement

• Annual self-assessment

Penalties and how enforcement actually works

Administrative fines per the EAA implementing law; corrective orders by DKÜ.

Hungary's Digital Government Agency (DKÜ) oversees the public-sector regime, while consumer-facing enforcement is shared with the consumer-protection authorities. The approach is complaint- and inspection-driven with administrative fines and corrective orders issued through DKÜ. Annual self-assessment is expected of covered operators, and because enforcement is jointly run with consumer-protection bodies, a foreign seller's accessibility gap can be pursued as part of a broader consumer-rights inspection rather than in isolation.

Practical first steps for a Hungary 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 (Hungary regulators expect this discoverable)

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

• Re-scan after every major release; track regressions