Website Accessibility Testing in Latvia
EAA and EN 301 549 audits for Latvia, with evidence on every finding.
The short answer for Latvia
Being a small market changes nothing here. Latvia carries the same two European rules as every other member state. The Web Accessibility Directive has bound public sector bodies since June 23, 2021, against EN 301 549, which carries WCAG 2.1 AA inside it. The European Accessibility Act then reached consumer-facing services on June 28, 2025, and that is the date most businesses in Latvia are actually behind.
Both were transposed into national law, which is where the detail lives. Latvia has its own act, its own supervisory body and its own penalties, and we are not going to guess at their names on a services page. What does not vary is the technical standard. It is EN 301 549 either way, and that is what an audit answers.
So here is what we do about it. We work your Latvia site against all 55 WCAG 2.2 A and AA rules by hand, then a professional blind screen-reader user runs your real journeys while we record where they stop. WCAG 2.2 covers everything EN 301 549 asks for and more, so one audit answers both directives with room to spare. Every finding arrives with its screenshot and the fix that closes it.
Which law lands on you in Latvia
European Accessibility Act (EAA)
- Standard
- Annex I, EN 301 549 (includes WCAG 2.1 AA)
- Where it stands
- Applies since Jun 28, 2025
- Who it binds
- The private sector
- Reaches sellers based abroad
- Yes, wherever you are established
- What non-compliance costs
- National fines, orders to fix, market restrictions
- Main application date
- Jun 2025
- EU member states
- 27
- Web standard in EN 301 549
- 2.1 AA
- Employee cap for the exemption
- <10
The EAA dates, 3 of them
- Jun 28, 2025The main application date: covered products placed on the market and covered services provided to consumers are in scope from this date. Exceptions and transition rules can change the picture for specific cases
- Jun 28, 2030The end of two transition arrangements. Products lawfully in use to provide a similar service before June 28, 2025 can continue until this date, and pre-existing service contracts can run until they expire, but no later than June 28, 2030
- 20 years maxSelf-service terminals have a separate allowance: a member state can let terminals lawfully in use before June 28, 2025 serve out their economic life, up to a maximum of 20 years after entry into use
Web Accessibility Directive (EU) 2016/2102
- Standard
- EN 301 549 V3.2.1, which carries WCAG 2.1 AA
- Where it stands
- Fully in force since Jun 23, 2021
- Who it binds
- The public sector
- Reaches sellers based abroad
- Not by itself
- What non-compliance costs
- National enforcement body, annual monitoring, published results
- Through EN 301 549 V3.2.1
- 2.1 AA
- Mandatory statement blocks
- 7
- Monitoring by your member state
- Annual
- Last application date, now passed
- 2021
The Web Accessibility Directive dates, 5 of them
- Sep 23, 2018Transposition deadline: member states had to have the directive in national law, and had to name their monitoring and enforcement bodies
- Sep 23, 2019Applies to websites published on or after September 23, 2018. Intranet and extranet content published on or after September 23, 2019 is in scope too
- Sep 23, 2020Applies to every other public sector website
- Jun 23, 2021Applies to mobile applications. The last of the three application dates
- Feb 12, 2022EN 301 549 V3.2.1 becomes the harmonised standard behind the presumption of conformity, which puts WCAG 2.1 AA at the center of it
Inside an audit for a site in Latvia
Start with the honest part. The audit is the same in Latvia as it is anywhere, because WCAG does not change at a border. What changes is which law is watching and what it costs to fail, and the section above settles that.
The work itself runs in three passes. A machine finds the failures a machine can prove. A human works every one of the 55 A and AA rules by hand. Then a professional blind screen-reader user opens your real journeys and tries to finish them, the way your customers would. Every finding arrives with its screenshot and the fix that closes it, drawn from our free library of 432 guides.
None of the reference sits behind a form, either. Every number below counts pages you can go and read right now, free, whether you ever buy an audit or not.
- A and AA rules we check
- 55
- Techniques and failures
- 432
- ACT test rules
- 90
- ARIA roles documented
- 94
- Terms in the glossary
- 131
- Checklists to work from
- 9
- A free 10-page scan that finds what a machine can prove, before you spend anything
- Paid audits at fixed prices on the pricing page, $499 for 10 pages in 5 business days, $1,499 for 25 in 10
- The exact deliverable, free to read, as the sample report
The honest limit
And an audit is evidence, not a legal opinion. We tell you what fails, who it stops, and what closes it. Whether that satisfies a regulator or a court in Latvia is a question for your lawyer, and we would rather say so than pretend otherwise.
Straight answers for Latvia
My site is in Latvia. Does that change what you test?
No. WCAG is the same standard everywhere, so the testing is identical wherever you are. What changes is which law is watching and what failing it costs, and that is what the law section on this page settles.
What law am I actually answering to in Latvia?
EAA and Web Accessibility Directive are the ones that reach Latvia first, and each has its own page here covering what it asks for, who it lands on, and how it gets enforced. Sell into more than one market and more than one of them can reach you at the same time.
Should I be publishing an accessibility statement here?
At least one of the laws that reaches Latvia names an accessibility statement, so plan on publishing one. Our free generator writes it from what the audit found, so the page says what actually works today rather than what you hope works.
What am I paying, and what turnaround do I get?
A Rapid Audit is $499 for 10 pages, with the report in 5 business days. A Standard Audit is $1,499 for 25 pages in 10 business days. Once your team has fixed things, the re-audit is half price within 3 months.
Who does the human half of the testing?
Yes, on every audit. A professional blind screen-reader user opens your real journeys and tries to finish them, and we write down where they stop. That is the pass no scanner can run.
Related on this site
The reading behind the law that reaches you in Latvia, and the guides that turn it into work your team can do.
Regions and cities we test in Latvia
Accessibility testing in other countries
Show all 48
- Denmark
- Norway
- Switzerland
- United Kingdom
- United States
- Canada
- Austria
- Belgium
- Bulgaria
- Croatia
- Cyprus
- Czechia
- Estonia
- Finland
- Greece
- Hungary
- Lithuania
- Luxembourg
- Malta
- Poland
- Portugal
- Romania
- Slovakia
- Slovenia
- Sweden
- Argentina
- Colombia
- China
- Hong Kong
- Taiwan
- Saudi Arabia
- Qatar
- United Arab Emirates
- Iceland
- Liechtenstein
- Australia
- New Zealand
- Japan
- South Korea
- India
- Israel
- Brazil
Find out where your site stands in Latvia
Run the free scan. Read the sample report. Order the audit when you want the humans on it, and what lands is a report your developers, your lawyer or a regulator in Latvia can act on.