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.
Digital accessibility
The websites and mobile apps of state and municipal institutions must work for everyone, including people who use a screen reader, only a keyboard or enlarged text. CreateIT assesses accessibility against WCAG 2.1 AA and the EN 301 549 standard, fixes the issues found, prepares the accessibility statement required by Cabinet Regulation No. 445 and helps keep it up to date.
What the service covers
Accessibility audit
We test your website or mobile app against the WCAG 2.1 AA and EN 301 549 criteria, combining automated tools with manual review, keyboard navigation and screen readers.
Remediation
We fix templates, components, forms and content in your content management system, so each problem is solved at its source rather than page by page.
Accessibility statement
We prepare the statement using the template in Annex 2 of Cabinet Regulation No. 445, base it on a documented assessment and help you keep it up to date.
Annual review
We prepare the simplified assessment that institutions must complete each year by 22 December, and retest the website after significant changes.
Documents and content editors
We check and remediate the PDFs and other documents published on your website, and train content editors to write alt text, headings and links that work for every user.
Procurement requirements
We help you include accessibility requirements in the technical specification for a new website or system, and check that they have been met before the work is accepted.
How the work runs
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 on websites we maintain, or give your developer 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.
When was your institution's website last tested?
We reply within one working day.
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.
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 plug-in 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
- Website takeover and maintenance We take over WordPress, WooCommerce and Drupal sites and custom-built websites and web systems from other developers, even when the previous team can no longer be reached.
- Security audit A cybersecurity (IT security) audit helps you understand which controls you actually have in place, where they are not working well enough and which weaknesses pose the greatest risk.
- Mobile apps We build mobile apps for customers, for staff and for digital products.