Poland's digital accessibility act in 2025: who it covers and what it changes
Since 28 June 2025 Polish digital accessibility law also covers businesses: e-commerce, banks, telecoms. Check who it applies to and how to prepare.
Digital accessibility law in Poland now works on two tracks. Since 2019 the ustawa o dostępności cyfrowej (the Polish digital accessibility act) has covered the websites and apps of public sector bodies, and since 28 June 2025 selected obligations also apply to businesses. That second track comes from the act of 26 April 2024, which implements the European Accessibility Act.
What the digital accessibility act is and why 2025 is a turning point
AI-generated image
In practice this is a change for many owners of online stores, service platforms and companies that sell to consumers online. Until now, digital accessibility rules were associated mainly with government offices, schools, cultural institutions and local authorities. Since 2025 the subject has reached business as well.
What is it about in plain terms? A website, store, app or online service should work so that people with different needs can use it too: people who are blind, have low vision, are deaf, have limited mobility, cognitive limitations or a temporary difficulty, for example after a hand injury. Accessibility does not end with a bigger font. It covers the whole process: from finding a product, through the form, to payment and order confirmation.
For public sector bodies, the digital accessibility act (act of 4 April 2019) means an obligation to have accessible websites, mobile apps and accessibility statements. For businesses, the new 2024 act sets requirements for selected products and services, including e-commerce. That is why 2025 is a turning point: accessibility stopped being a subject for public administration only.
Who the digital accessibility act covers in 2025
AI-generated image
Public sector bodies have had obligations for years, and since 28 June 2025 they have been joined by selected businesses that offer products or services to consumers. Most often this concerns e-commerce, financial services, telecommunications, e-books and some passenger transport services.
If you run an online store, sell services online or let a customer conclude a contract through a website or app, it makes sense to check your obligations straight away. E-commerce services are described broadly in the act: they are services provided at a distance, by electronic means, at the consumer’s request, with a view to concluding a contract. In plain terms: the customer visits the site, picks a product or service, goes through the basket or a form and buys.
The new rules also cover retail banking, selected financial services, telecommunications, access to audiovisual media services, the distribution of e-books and selected services related to passenger transport, for example electronic tickets and travel information. On the product side they include computers, smartphones, tablets, payment terminals, cash machines, ticket machines and e-book readers.
There is also an important exclusion for the smallest service providers. The act does not cover services offered or provided by microenterprises, meaning companies that employ fewer than 10 people on annual average and have an annual turnover or balance sheet total of up to the equivalent of EUR 2 million. That does not mean accessibility is worth skipping. An accessible store is usually more convenient for all customers, and fixes built in from the start cost less than a rebuild after the fact.
What requirements have to be met
Put simply: a website, store or app should be perceivable, operable, understandable and robust. In practice the technical reference point is WCAG 2.1 at level AA and the EN 301 549 standard, especially for websites, apps and digital services.
These four principles sound official, but they translate into ordinary work on a website. Perceivable means the user can take in the content in different ways. An image should have alternative text, a video should have captions, and information cannot rely on colour alone. If a form error is shown only with a red border, some people will not notice it.
Operable is about how things work. The site has to be usable with a keyboard, without a mouse. That applies to menus, filters, forms, the basket, modals, consents, booking calendars and payments. If a customer cannot reach the “Buy and pay” button with the Tab key, the purchase path is a problem.
Understandable means clear messages and predictable behaviour. A field label should say what you expect: “Email address”, “Phone number”, “Postcode”. An error should explain what to correct, not just show “Invalid data”. In an online store the delivery, payment and account registration forms matter most.
Robust means working with assistive technologies, for example screen readers. What counts here is correct HTML structure, headings in a logical order, form labels, button names, status messages and no keyboard traps. Good accessibility often starts in the code, although the user sees it as ordinary convenience.
Deadlines: when the rules apply from
For new products and services covered by the act, the cut-off date is 28 June 2025. From that day, new services and products within the scope of the act should meet the accessibility requirements.
There are transition periods, though, which deal with older contracts and solutions that were already in use. Contracts for offering or providing services that were concluded before the act came into force can continue unchanged until they expire, but no longer than until 28 June 2030. This matters for subscription services, framework agreements and longer contracts.
Until 28 June 2030 a service provider can also use products that do not meet the requirements, if it used them earlier to provide services of the same kind. A separate provision applies to terminals: they can be used until the end of their economic life, but for no more than 20 years from when they were first put into use.
For businesses the practical conclusion is simple. It does not pay to design new builds “the old way”. If you are rebuilding a store, checkout, booking form or app now, accessibility should go into the brief, the Figma design, the code and the tests. Fixing it after launch usually takes more time, because it touches the look, the content, the components and the logic.
What the penalties are for lack of accessibility
Lack of accessibility can lead to supervisory action and administrative penalties. The authority can call on a company to take corrective action, demand documents, ban the service from being offered and, as a further step, impose a fine.
For e-commerce services the supervisory authority is the minister responsible for digital affairs, and the whole system also includes the President of the Management Board of PFRON (the State Fund for Rehabilitation of Disabled Persons), other market surveillance authorities and customs authorities. For financial, telecommunications or transport services, other institutions may be responsible, depending on the scope of the act.
The mechanism does not work only “from the top down”. Anyone can file a notification that a product or service does not meet the accessibility requirements. In practice a problem can come out of an inspection, a customer complaint, a user report or a lack of cooperation when explanations are requested.
A separate procedure applies to public sector bodies. A user can request that a website, an app or one of their elements be made digitally accessible. The public body should respond without undue delay, as a rule within 7 days, and when that is not possible, give a longer deadline and the reason for the delay.
The penalty is one thing. The other cost is often more everyday: abandoned baskets, phone calls from customers, orders corrected by hand, forms that some people cannot send. Business does not like surprises. Accessibility helps to limit them.
How to prepare a website or store for the act’s requirements
The best start is an accessibility audit of the most important paths, followed by fixing the site in stages. You do not have to take the whole site apart straight away, but you do have to know where a user can get stuck.
In an online store the first path is usually: landing on the site, search or a category, the product page, the basket, delivery, payment and order confirmation. For services it will be, for example, a contact form, booking an appointment, buying a consultation, downloading a document, logging in to an account or paying online. For a public sector body there is also the accessibility statement, documents, the BIP (Biuletyn Informacji Publicznej, the public information bulletin), case forms and content published regularly.
An audit should check both the code and real use. Automated tools will catch some of the errors, for example missing alternative text, contrast problems or incorrect labels. They will not check everything, though. Someone has to go through the site with a keyboard, look at the focus order, read the error messages, check the forms and make sure the basket does not fall apart when the text is enlarged.
Then comes the fixing stage. First the things that block a purchase or contact: an inaccessible menu, forms without labels, errors without a description, elements that cannot be operated with a keyboard, button contrast that is too low, unreadable payment messages. Then content, documents, multimedia and less visited subpages. This order gives a quick result where the user really needs things to work.
Documentation matters too. Public sector bodies need an accessibility statement and need to keep it updated. Businesses covered by the act should have public information about the accessibility of the service, usually in the terms and conditions or an equivalent document, and should be able to show what action they have taken. If a service does not meet the requirements, fixes have to be planned and, in specific cases, the relevant authority informed.
What remains at the end is maintenance. The law treats digital accessibility as an obligation, but in practice it is a process. A new banner, plugin, form, payment method or checkout rebuild can break something that used to work well. That is why accessibility is worth checking with every larger change, not once every few years.
FAQ: the digital accessibility act
Since when has the digital accessibility act applied to businesses?
Since 28 June 2025. From that date, new products and services listed in the act of 26 April 2024 have to meet the accessibility requirements. Contracts concluded earlier have transition periods, until 28 June 2030 at the latest.
Do microbusinesses have to meet the act’s requirements?
Services offered by microenterprises (fewer than 10 employees on annual average and up to EUR 2 million in turnover or balance sheet total) are excluded from the act. Accessibility still pays off, though: an accessible store is more convenient for all customers.
What technical standard has to be met?
The reference point is WCAG 2.1 at level AA and the EN 301 549 standard. In practice that means alternative text, keyboard operation, sufficient contrast and understandable error messages, among other things.
What are the penalties for an inaccessible website or store?
The supervisory authority can call for corrective action, demand documents, ban the service from being offered and impose an administrative fine. Anyone can file a notification about inaccessibility, including a customer.
Does the act apply to every website?
No. It covers the websites and apps of public sector bodies (the 2019 act) and specified products and services of businesses (the 2024 act), including e-commerce, banking, telecommunications and e-books. An ordinary brochure site of a microbusiness is not subject to these rules.