Accessibility audits and remediation

Digital accessibility lets people use your services with a keyboard, a screen reader or enlarged text. We test websites, apps and documents against WCAG 2.1 AA and EN 301 549, find the barriers and remove them. We work with companies as well as national and local government bodies.

An audit followed by the fixes

The audit shows where users get stuck, why it happens and what needs to change. We rank the work by priority, so the problems that get in people's way most are fixed first.

Then we fix the templates, components, forms and content in your content management system, so each problem is solved at its source rather than page by page. Once the fixes are in, we test again.

We test what real users do

We try out navigation, signing in, forms and other key functions on your website or mobile app the way people really use them, with a keyboard, the NVDA and VoiceOver screen readers or enlarged text. Automated tools are backed up by manual testing, because some problems only show up when a person uses the page.

Documents, the accessibility statement and your editors

We remediate the PDFs and other documents published on your site. We draw up the accessibility statement and help you keep it up to date. For public bodies we also prepare the annual simplified assessment and retest the site after significant changes.

We train your content editors to write headings, links and image descriptions that help people find their way, so new content does not undo the fixes.

Build accessibility in from the start

We help you write accessibility requirements into the technical specification or tender for a new website or system, and check they have been met before the work is accepted. When we build the site ourselves, accessibility is part of the design and code from the start, so problems are fixed before they reach users.

How we work

Sample and scope

We agree on the sample to test, for example the most visited pages, the main e-services, forms, documents and the mobile app.

Testing

We test every page in the sample against the WCAG 2.1 AA criteria with automated tools, the keyboard, the NVDA and VoiceOver screen readers and enlarged text.

Report

We write a report that gives, for every issue, the WCAG criterion, the impact on users, the priority and a specific recommended fix.

Fixes

We fix the issues ourselves or, if another developer maintains the site, give them precise instructions and answer their questions.

Retest and statement

We verify the fixes, prepare the accessibility statement and agree when the next review will take place.

Make your website more accessible

Send us the site address and the most important things users need to do on it. We'll prepare a proposal for the audit and fixes. We reply within one working day.

Request an audit

What Cabinet Regulation No. 445 requires

Cabinet Regulation No. 445 of 14 July 2020, on how institutions place information on the internet, transposes the EU Web Accessibility Directive (EU) 2016/2102. Institutions must make their websites and mobile apps perceivable, operable, understandable and robust, publish an accessibility statement and keep it up to date, and complete a simplified assessment each year by 22 December. The statement must be based on a documented assessment, such as the institution's own simplified assessment or an independent external audit.

Monitoring results are public

The Ministry of Smart Administration and Regional Development regularly monitors the accessibility of state and municipal websites and mobile apps and publishes the results. In the 2025 monitoring, the most common problems concerned image alt text, keyboard access and colour contrast, while users of the mobile apps tested could complete fewer than half of the test tasks. If an institution does not respond properly to a user's accessibility complaint, the user can turn to the Ombudsman.

The standards we test against

We test against WCAG 2.1 AA and version V3.2.1 of the harmonised European standard EN 301 549, which institutions' accessibility statements refer to. The new version of the standard, V4.1.1, published in September 2026, is based on WCAG 2.2, so in new projects and fixes we already take the WCAG 2.2 criteria into account.

Accessibility in our projects

For Riga Municipality we built the Youth Digital Embassy. The open tender required accessibility to WCAG 2.1 AA. The accessibility tools are part of the site itself, not an external plugin, and visitors can enlarge text up to 150%, change the spacing and contrast and stop motion.

We have also audited, assessed or improved accessibility on the websites of the State Fire and Rescue Service, the Latvian Council of Science and a Ministry of Finance campaign, on balso.riga.lv and on georiga.eu, Riga's geospatial data portal.

Frequently asked questions

Is an automated check or an accessibility toolbar enough?
No. Automated tools find only some of the problems, and a toolbar or plugin does not fix errors in a page's code, structure or content. That is why every audit also includes manual review, keyboard navigation and screen reader testing.
What must an accessibility statement contain?
The statement follows the template in Annex 2 of Cabinet Regulation No. 445 and must be based on a documented assessment. It states the level of compliance, the content that is not accessible and why, the alternatives available, the feedback procedure and the Ombudsman's contact details. The link to it goes in a visible place, such as the page footer.
Do the requirements apply to documents too?
Yes. EN 301 549 also applies its accessibility requirements to documents published on a website. We check their structure, headings, tables and image descriptions, remediate the most important documents and train staff to create accessible documents from the start.
Can you fix a website built by another company?
Yes. We work with WordPress, Drupal and other systems. If another developer maintains the website, our report gives them specific instructions for each fix, and we retest once the fixes are in.
How long does an audit take?
It depends on the size of the sample, the number of e-services and forms, and whether documents and a mobile app also need testing. We set out the timeline and scope in our proposal once we have looked at the website.

Related services