Lithuania · LT
Lithuania accessibility law: PSIR Act + EAA explained
Lithuania transposed the Web Accessibility Directive in 2018 and the EAA in 2024, with monitoring carried out under the public-sector information resource management framework.
- Primary law
- Viešojo sektoriaus informacinių išteklių valdymo įstatymas
- In force from
- 28 June 2025
- Standard
- WCAG 2.1 Level AA via EN 301 549
- Enforcement
- Ministry of the Economy and Innovation
Who has to comply
Public-sector since 2018; consumer services from 28 June 2025.
Lithuania is a small, digitally advanced Baltic market where online public and private services are widely used. Under the EAA-implementing act, a foreign store selling to Lithuanian consumers is covered on the country-of-consumption basis. A Lithuanian-language accessibility statement is expected, and sellers who treat the three Baltic states as one market should note Lithuania is a separate jurisdiction with its own language and enforcement body.
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, Lithuania requires the following operational items, which auditors check first because they are simple to verify:
EN 301 549 / WCAG 2.1 AA
Lithuanian-language statement
Penalties and how enforcement actually works
Administrative penalties per EAA-implementing act.
Enforcement runs through the Ministry of the Economy and Innovation, building on the public-sector monitoring established under the information-resource-management framework. Lithuania's approach is centralised and largely complaint-driven, with administrative penalties under the EAA-implementing act. As a small but digitally mature administration, its first enforcement cycle is likely to emphasise clearly detectable failures and the adequacy of the Lithuanian-language statement before moving to deeper technical assessment.
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 Lithuania 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 (Lithuania regulators expect this discoverable)
Add a feedback channel and answer within the country-specified window
Re-scan after every major release; track regressions
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.