A WCAG audit is a mandatory examination of a website or mobile application for compliance with digital accessibility standards for people with disabilities. Under the Act of 4 April 2019 on the digital accessibility of public sector bodies' websites and mobile applications, every public institution must update its accessibility statement annually, and the best time for a review and audit is by 31 March. If you run a public sector body's website, this article will show you why a regular WCAG audit is not only a legal requirement but also a real benefit for users.

The legal obligation arising from the Act

The Digital Accessibility Act requires public sector bodies to ensure their websites comply with WCAG 2.1 at level AA, and WCAG compliance is not optional but a legal obligation, ignoring which may have legal and reputational consequences. Under Article 11 of the Act, the accessibility statement must be reviewed and updated at least once a year, and in practice 31 March each year is indicated as the time for this review.

This applies to, among others, public offices, schools and local government educational institutions, which, as public entities, must guarantee that their websites are accessible to people with disabilities. It is worth remembering that, after two monitoring exercises, the Ministry of Digital Affairs may impose a fine of PLN 5000 for a missing statement, failure to update it or missing required elements, and persistent failure to fulfil the obligation may increase the fine to as much as PLN 10 000. Since 1 August 2024, new accessibility statements must be created in accordance with version 2.0 of the Technical Conditions, and older statements must be updated to this structure at the next review.

How to conduct a WCAG audit step by step

A comprehensive website accessibility audit is based on an evaluation method consistent with WCAG principles and combines automated tools with manual tests. For automated verification, it is worth using the W3C Validator, which analyses the correctness of HTML code for errors affecting accessibility, and WAVE, which highlights problems such as missing alternative text or poor contrast. Google Lighthouse, built into the Chrome browser, evaluates a website's performance, SEO and accessibility simultaneously, making it a good tool for an initial diagnosis

However, automated tools will not detect every barrier, so manual testing of keyboard navigation and checking the website with screen readers such as NVDA or JAWS, which simulate website use by blind people, are essential. Another important part of the audit is evaluating the interface structure: intuitive placement of elements, consistent messages and a logical heading hierarchy, which make it easier for people using assistive technologies to navigate the website. Regular testing after every website update helps ensure that new features have not introduced additional accessibility problems.

This also applies to educational platforms: schools in Poland required to comply with WCAG should first carry out an audit, ensure that they are using the current software version, correct the errors identified, and finally publish and annually update an accessibility statement.

Practical questions about a WCAG audit

Who has to carry out a WCAG audit?

The obligation applies to public sector bodies: public offices, schools, universities, cultural institutions and local government educational units, which must ensure their websites and applications comply with WCAG 2.1 at level AA.

What happens if I do not conduct an audit by 31 March?

Failure to update the accessibility statement or its required elements after two monitoring exercises may result in a fine of PLN 5000, or even PLN 10 000 in cases of persistent neglect.

Is an automated tool enough?

No: tools such as WAVE or Lighthouse detect only some problems, so a complete audit also requires manual tests using a keyboard and screen readers.

Does the statement have to be created from scratch every year?

Not always from scratch, but it must be reviewed and updated every year, and since August 2024, new statements must follow the version 2.0 structure.

If you are looking for comprehensive support in creating and maintaining websites that comply with legal requirements, it is worth addressing this as early as the website design stage.

Summary and next steps

A WCAG audit is not a one-off action but a recurring process that public sector bodies must repeat every year by 31 March to remain compliant with the Digital Accessibility Act. Regular verification helps avoid financial penalties, but above all it genuinely improves the website experience for people with disabilities. Do not wait for an inspection: check whether your website meets WCAG requirements today.