Hungary · HU
Hungary accessibility law: Act LXXV/2018 + EAA explained
Hungary transposed the Web Accessibility Directive in 2018 and the EAA in 2024. Public-sector enforcement runs through DKÜ; consumer-facing services come under the joint enforcement of consumer-protection bodies and DKÜ. Hungarian-language accessibility statements are mandatory.
- Primary law
- 2018. évi LXXV. törvény
- In force from
- 28 June 2025
- Standard
- WCAG 2.1 Level AA via EN 301 549
- Enforcement
- Digital Government Agency (DKÜ)
Who has to comply
Public-sector since 2018; consumer services from 28 June 2025.
If your service reaches consumers in Hungary, EAA enforcement applies the same way it does to a domestic provider. The "country of consumption" rule means a Shopify store run from outside the EU but selling into Hungary is covered. There is no carve-out for non-EU sellers.
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Ü.
Digital Government Agency (DKÜ) runs the audits. They start with the largest covered services and move down. The first cycle of EAA audits in 2025–2026 will focus on visible non-compliance — missing accessibility statements, obvious WCAG violations on the homepage, lack of feedback channel — because those are cheap to detect. Deep technical audits come later.
Most enforcement starts with a complaint or a routine sweep. The first signal is usually a written notice giving you 30–60 days to remediate before fines kick in.
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
Frequently asked questions
Are Hungarian translations required?
Yes — the accessibility statement must be available in Hungarian even if the service itself is multilingual.
Accessibility law in nearby jurisdictions
Find every accessibility issue on your site in 60 seconds.
Free public scan. No card. AI-generated fixes for every issue we find.