skip to content

accessibility 10 min read

Accessibility statement: how to write one (template and example)

What is an accessibility statement, who has to have one and what should it contain? A practical step-by-step guide and a ready template to fill in.

An accessibility statement open on a laptop

An accessibility statement (deklaracja dostępności in Polish law) sounds official, but in practice it is a short, specific document on a website. Below I explain what it is, who has to have one and how to write it, with a ready template to fill in.

What an accessibility statement is

An accessibility statement is public information about whether a website or mobile app is digitally accessible. It also shows what still needs improving and how a user can report a problem.

In practice it is a short document on the website. It should say in plain language: which site it describes, what its accessibility status is, who is responsible for reports and what the procedure looks like when someone asks for accessibility to be provided.

Digital accessibility means that people with different needs can use the site. For example people who are blind, have low vision, are deaf, have limited mobility or use only a keyboard. Sounds technical? The meaning is simple: the site should work for people, in different situations.

Who has to have an accessibility statement and who will find it useful

An accessibility statement is required mainly from public sector bodies. Private companies usually have no such obligation under the ustawa o dostępności cyfrowej (the Polish digital accessibility act) of 2019, but sometimes they prepare similar information voluntarily or because of other regulations.

The obligation applies to government offices, schools, public institutions, local government units and some organisations that carry out public tasks, among others. If you work on a publicly funded project, run a website for an institution or serve an organisation closely tied to the public sector, check this subject carefully.

A private company can prepare a similar statement when it wants to show clearly how it takes care of accessibility. This makes particular sense for online stores, online services, medical practices, education, recruitment and services aimed at a wide audience.

Since 28 June 2025 some companies also have obligations under the Polski Akt o Dostępności (Polish Accessibility Act). For e-commerce this includes information on how the service meets the accessibility requirements. That is a separate subject from the accessibility statement for public sector bodies, although in practice the two documents can be similar.

What an accessibility statement should contain

The layout of an accessibility statement on a laptop screen

AI-generated image

A good accessibility statement is specific: what it covers, what state the site is in, what the known problems are and how they can be reported. It should be readable for the user, not written for an inspection.

In the statement you give the name of the entity, the address of the website or app, the date the site was published, the date of the last significant update and the date the statement was prepared or reviewed. You also add how accessibility was assessed: on the basis of an audit, a self-assessment, automated tests, manual tests or a combination of these methods.

A description of the accessibility status is needed. You can write that the site is conformant, partially conformant or non-conformant with the requirements. If there are errors, describe them in plain language. For example: some PDF files may be difficult for screen readers to read, some videos have no captions, selected form elements need improving.

The statement should include contact details for the person or unit responsible for accessibility. A public sector body also gives the procedure for reporting problems, information about the right to file a complaint, details of the architectural accessibility of its premises, information about a sign language interpreter and information about non-standard keyboard shortcuts, if there are any.

If the entity has a mobile app, it has to say where the app can be downloaded and give its accessibility statement. On a public sector website the statement should be reachable during ordinary navigation around the site.

How to write an accessibility statement, step by step

Writing an accessibility statement, notes and a laptop

AI-generated image

First establish whether you have a legal obligation or are preparing the statement voluntarily. The scope of the content and the level of formality depend on that.

Step 1. Define what the statement covers. Enter the specific website address, language version or app. The statement should describe a real site, not the whole activity of a company or institution.

Step 2. Check accessibility. Go through the site with a keyboard, check the forms, headings, contrast, alternative text for images, PDF files, multimedia and error messages. Automated tools help, but they do not see everything.

Step 3. Name the problems. Write in ordinary language. Instead of “non-conformance with criterion 1.1.1”, write “some images have no alternative descriptions, so a person using a screen reader may not get the full information”.

Step 4. Give a way to get in touch. Provide an email address, a phone number or a form. The user has to know where to report a problem and what information to give.

Step 5. Describe the procedure. For public sector bodies, include response deadlines, the option of providing alternative access and the complaint path. In a private company a simpler description is enough: we receive the report, we check the problem, we come back with an answer.

Step 6. Publish the document in a visible place. A link in the footer usually works best, because the user will find it from every subpage.

Step 7. Plan the review. Public sector bodies update the statement by 31 March each year and after changes that may affect accessibility. For a private company it is good to adopt a similar rhythm, because a site is alive: new content, plugins, forms and files keep arriving.

Accessibility statement template (sample text)

Treat the template below as a starting point. You will also find the official template for public sector bodies on gov.pl. Fill it in with real data and adapt it to your site.

Accessibility statement

[Name of entity] undertakes to ensure the digital accessibility of the website [website address] in line with the digital accessibility requirements.

This accessibility statement applies to the website [website address].

Date the website was published: [date].

Date of the last significant update of the website: [date].

Date the statement was drawn up: [date].

Date of the last review of the statement: [date].

Digital accessibility status

The website is [conformant / partially conformant / non-conformant] with the digital accessibility requirements.

Partial conformance results from the following problems: [describe the specific problems, for example PDF files, missing captions for videos, selected form elements, incomplete alternative descriptions of images].

We are working on removing these problems. If you need content in a different form, contact us.

Preparation of the statement

We prepared the statement on the basis of [a self-assessment / an accessibility audit / automated and manual tests / another method].

While checking the site we paid attention to keyboard operation, heading structure, readability of the content, contrast, forms, multimedia, downloadable files and how the site works with assistive technologies.

Keyboard shortcuts

The standard keyboard shortcuts of the browser can be used on the site.

If the site has non-standard keyboard shortcuts, describe them here. If it has none, say so directly.

Feedback and contact

You can report digital accessibility problems to [full name or name of department].

Email: [email address].

Phone: [phone number].

In your report, give the address of the page where the problem occurs, a short description of the problem and how to contact you back.

Handling of reports

We will respond to your report as quickly as possible. If we cannot remove the problem straight away, we will tell you how we plan to proceed or offer alternative access.

For a public sector body, describe here the procedure for a request to ensure digital accessibility and for a complaint. Also add information about the option of contacting the Rzecznik Praw Obywatelskich (the Polish Ombudsman).

Architectural accessibility

The premises of [name of entity] are located at [address].

Describe the entrance to the building, how to get there, parking, reception, lifts, toilets, whether an assistance dog can come in and other information important for people with disabilities.

Communication and information accessibility

Describe the availability of a Polish Sign Language interpreter, an induction loop, alternative forms of contact and other solutions that support communication.

If a given service is not available, say so directly.

Where to publish it and how to update it

Publish the accessibility statement where the user will really find it. Most often the best place is the footer of the site and a separate subpage with a simple address.

For public sector bodies the link to the statement should be reachable while navigating the site. Do not hide it deep in the terms and conditions, the news section or a PDF file. The statement itself has to be digitally accessible too.

Updating works in two modes. The first is a regular review, for public sector bodies by 31 March each year. The second is an update after larger changes to the site, for example after a template rebuild, a change of system, a new form, the launch of a store or the publication of a large number of files.

With every update, check the dates, the accessibility status, the list of known problems, the contact details and the procedures. It is a quick check that saves stress later.

The most common mistakes in an accessibility statement

The most common mistake is a statement detached from the real state of the site. The document says “everything is conformant”, while the form does not work from the keyboard, the PDF files are scans and the videos have no captions.

The second problem is language. An accessibility statement is meant to help the user. If it is written entirely in abbreviations, criterion numbers and official sentences, it stops doing its job.

A specific contact is often missing too. The address of the front office alone is often not enough. It is better to name a person, a department or a clear reporting path.

Another mistake is missing dates. Without the dates of publication, review and update it is hard to judge whether the document is current. And with accessibility that matters, because a site changes with every larger update.

Copying the template without filling in real data happens as well. Empty brackets, general sentences and statements made “by eye” come to light quickly. It is better to write less, but honestly.

FAQ

Does every company have to have an accessibility statement?

No. The classic accessibility statement from the 2019 act applies mainly to public sector bodies. A private company may have other information obligations, though, especially for online services and e-commerce.

Does an online store have to have an accessibility statement?

A private store on its own usually does not have to publish a statement like a government office does. Since 28 June 2025, however, some e-commerce services have been subject to the Polish Accessibility Act, so a store may be obliged to provide information about the accessibility of its service.

Can you write an accessibility statement yourself?

Yes, if you know the state of the site and understand the requirements. For a public sector website or a larger site it is better to rely on an audit, because some problems are hard to notice without tests.

How often should an accessibility statement be updated?

Public sector bodies review and update it by 31 March each year and after changes that may affect accessibility. For a company website a good rhythm is at least once a year and after larger changes to the site.

Does an accessibility statement have to be a PDF?

No. It is best published as an ordinary HTML subpage. That form is easier to find, to update and to read with assistive technologies.

What should you do if the site does not meet the accessibility requirements?

Say so clearly, list the known problems and give a way to get in touch. Then set a plan for the fixes. Honesty in the statement is better than a promise of full conformance with nothing behind it.

Filip Chrapek

Let's work together

What do you need?
Budget
When?

Prefer email? hi@philgood.dev