Imagine a potential customer visiting your company’s website. They are interested in what you offer, want to check the details, and would like to send an inquiry. The problem is that they cannot navigate the menu using a keyboard. The form does not tell them which field needs to be corrected. The text is difficult to read, and important information is presented only in an image that cannot be read using their assistive technology.
Does this user have a chance of becoming your customer?
Digital accessibility is about situations like these. It is not merely a technical issue or an add-on to a graphic design. It is a way of designing and developing websites so that more people can independently find information, understand it, and take the actions they need.
The topic has also taken on significant legal importance. Since 28 June 2025, the Polish law implementing the European Accessibility Act, known as the Polish Accessibility Act (PAD), has been in force. It covers certain products and services, including e-commerce services. This does not mean, however, that every company website is subject to the same obligations.
It is therefore worth distinguishing between three issues: accessibility as an element of good design, legal requirements for certain services, and the real business benefits of removing barriers.
1. Digital accessibility — what does it actually mean?
Digital accessibility means designing and creating content, interfaces, and features so that people with different abilities and needs can use them.
This is not just about people who are blind or deaf. Barriers can also affect people:
-
with mobility limitations who cannot comfortably use a mouse;
-
with low vision who need to enlarge text or require adequate contrast;
-
who are blind and use screen readers;
-
with cognitive difficulties or problems concentrating;
-
with color vision deficiencies;
-
who are older, for whom small interface elements, complicated navigation, or unclear messages can pose a significant obstacle.
It is worth remembering that users’ needs are not constant. Someone may have a temporary limitation in the use of one hand, use a website in bright light, operate a phone with one hand, or have difficulty reading small text on a screen.
Accessibility does not mean creating a separate, simplified version of the internet. The goal is to make a website’s essential features usable in different ways.
2. Why is accessibility also a business issue?
Website owners usually assess their sites in terms of appearance, speed, how they present their offering, and how effectively they attract customers. Accessibility is connected to all of these areas.
Imagine an online store where the button to proceed to payment is visible but cannot be activated with a keyboard. Or a contact form that indicates an incorrect field only by turning it red, without giving the user clear information about the problem.
From a designer’s perspective, this may seem like a minor detail. For some users, it is a barrier that makes it impossible to complete a task.
Accessibility issues can affect, among other things, the ability to:
-
view an offer;
-
find a product;
-
compare options;
-
add a product to the cart;
-
fill in a form;
-
create an account;
-
make a payment;
-
contact a company.
If a user cannot get through one of these steps, even an attractive offer or a well-planned advertising campaign will not help.
Accessibility does not guarantee increased sales, but removing barriers can enable more people to use a website effectively. Equally importantly, many accessibility improvements also make websites more comfortable to use for people who do not have diagnosed impairments.
3. The Polish Accessibility Act — who is covered by the law?
This is a point that deserves particular attention, as the new rules are often oversimplified.
The Polish Accessibility Act is the Act of 26 April 2024 on ensuring that certain products and services comply with accessibility requirements for economic operators. It implements into Polish law Directive (EU) 2019/882 of the European Parliament and of the Council, or the European Accessibility Act (EAA).
The provisions have applied since 28 June 2025. They cover the groups of products and services specified in the Act, including telecommunications services, consumer banking, e-books, certain transport services, and e-commerce.
Does every website have to be accessible under the PAD?
No. This is a very important distinction.
The mere fact that a website is online does not automatically mean it is subject to all the requirements of the Polish Accessibility Act.
For e-commerce, the Act applies to services offered or provided remotely, through websites or mobile devices, electronically, and at the individual request of a consumer, for the purpose of concluding a contract.
In practice, this can include not only a typical online store, but also other services and ways of concluding contracts online. The Ministry of Digital Affairs’ official guidance refers, among other things, to the online sale of products and services.
However, not every company website, business card site, or informational website should automatically be equated with an e-commerce service covered by these rules. What matters is the nature and scope of the service provided, not simply whether a website exists.
Important exemption: microenterprises
The PAD exempts services offered or provided by microenterprises.
This means that it is not possible to conclude, without checking the company’s status and the nature of the service, that every online store has the same obligations. Applicability should be assessed on the basis of the relevant provisions and the definition of a microenterprise.
The Act also provides for other specific exemptions, including those concerning certain maps and content that is neither funded, created, nor controlled by the economic operator in question.
Takeaway: before beginning work to ensure compliance with the PAD, determine whether the specific company and service are actually covered by the Act. Decisions should not be based on the blanket claim that “from 2025, every website must comply with WCAG.”
4. What obligations may apply to an e-commerce service provider?
If a given e-commerce service is covered by the PAD, the service provider has obligations relating to ensuring accessibility and providing certain information.
These include the obligation to make information available to consumers about the service offered and provided, the information necessary to use it, and how the service meets accessibility requirements.
The Ministry of Digital Affairs indicates that this information should be publicly available in written or electronic form and may be included in the terms and conditions of service or another equivalent document.
The Act also provides for obligations relating to the assessment of service conformity. If a service provider finds that an e-commerce service does not meet accessibility requirements, they must immediately notify the Minister of Digital Affairs, indicating, among other things, the identified non-compliances and corrective measures.
This shows that accessibility is not just a matter of adding a few elements to a website once. For services covered by the regulations, it also requires an appropriate organizational approach and ongoing compliance.
This is not legal advice or an individual assessment of a particular store. The scope of obligations should be determined based on the current wording of the Act and the nature of the service provided.
5. Seven common barriers on websites and online stores
Even if a website is not directly subject to PAD obligations, it is worth checking it for common accessibility issues. Below are examples that are practically relevant to designing and using websites on a day-to-day basis.
1. Text with insufficient contrast
Light gray text on a white background may look subtle and elegant, but it can be difficult to read. A similar problem occurs with text placed over images, colored backgrounds, or gradients.
It is worth checking the contrast between text and background rather than judging it solely by how the design looks on a designer’s monitor.
2. Website use by mouse only
Not every user can or wants to use a mouse. Navigation, menus, buttons, and forms should be operable using a keyboard.
In practice, it is worth checking whether users can move through the most important elements of a page using the Tab key, activate them, and understand where they are in the interface.
3. Forms that are not properly designed
Forms are among the most important elements of business websites. They are how users submit inquiries, register accounts, order products, and provide data.
Problems arise when:
-
fields do not have proper labels;
-
required information is indicated by color alone;
-
error messages are unclear;
-
the user does not receive a clear confirmation after submitting the form;
-
the order for moving between fields is illogical.
An accessible form should not only look right, but also clearly communicate what it expects from the user and how to fix any errors.
4. Images without appropriate descriptions
An image may convey important information that is not included in the text. If a user relies on a screen reader, they may not receive this information if the image does not have appropriate alternative text.
This does not mean that every decorative image needs a detailed description. For images that are purely decorative, the appropriate solution may be to omit them from screen reader output.
The key is to distinguish the purpose of an image and convey information where it actually matters.
5. An unclear heading structure
Headings help users understand a page’s structure and quickly find the section they need. They should be organized logically rather than chosen solely based on font size.
It is also important to mark up elements correctly in the code. Text that looks like a heading visually is not always a heading from the perspective of assistive technologies.
6. Interface elements that are difficult to use on mobile devices
Buttons that are too small, insufficient spacing between elements, or dialog boxes that are difficult to close can make a website hard to use.
This issue affects not only people with mobility impairments. Anyone using a phone with one hand, making less precise movements, or using a device in inconvenient conditions may encounter similar difficulties.
7. Multimedia without appropriate alternatives
A video containing important information but no captions may be inaccessible to people who are deaf or hard of hearing. In turn, material in which important information is conveyed only visually may need an additional form of description.
The way alternatives are prepared depends on the type of material and the information it conveys. It is not enough to automatically add any captions—they should accurately represent the relevant content.
6. WCAG, EN 301 549, and the Polish Accessibility Act—how do these terms differ?
Discussions about digital accessibility often mention the abbreviations WCAG, EN 301 549, EAA, and PAD. However, these terms do not mean exactly the same thing.
EAA - European Accessibility Act
This is Directive (EU) 2019/882 of the European Parliament and of the Council on the accessibility requirements for certain products and services. It establishes the legal framework at European Union level.
PAD - Polish Accessibility Act
This is a Polish act of 26 April 2024 that implements the requirements of the EAA Directive into national law. Among other things, it specifies the scope of products and services covered by the regulations and the obligations of economic operators.
WCAG - Web Content Accessibility Guidelines
These are W3C guidelines on the accessibility of web content. They describe, among other things, the principles of perceivability, operability, understandability, and compatibility of content and interfaces.
The current W3C recommendation is WCAG 2.2. The guidelines cover a wide range of user needs and are a useful point of reference when designing, auditing, and developing websites.
EN 301 549
This is a European standard on accessibility requirements for information and communication technology products and services. The Ministry of Digital Affairs website identifies version V3.2.1 from 2021 as the applicable version of the standard for accessibility requirements for e-commerce services.
It is worth noting this distinction: WCAG 2.2 should not automatically be equated with all PAD legal requirements. WCAG is a set of guidelines for web content, whereas legal requirements and relevant technical references must be assessed in the context of the specific service and regulations.
7. How to check the accessibility of a website
An accessibility audit should combine technical analysis with testing real-world website-use scenarios.
It is not enough to open a website in a browser and conclude that everything looks right. Nor is it enough to run a single automated tool and treat its results as full confirmation of compliance.
In practice, it is worth checking several areas.
Keyboard Accessibility Test
Disconnect your mouse and try to complete the most important tasks on the website:
-
open the menu;
-
go to a selected subpage;
-
launch the search function;
-
fill in a form;
-
select a product;
-
complete the checkout process.
Pay attention to whether you can see which element is currently active and whether the order in which you move between elements is logical.
Contrast and Readability Check
Check the text, buttons, labels, icons, and form elements. Pay special attention to content placed over images and elements that change their appearance when hovered over or focused.
Screen Reader Test
It is worth checking whether the most important elements are read correctly by assistive technologies. Does the user know where they are? Do they understand what a button does? Are they notified of form errors?
This helps identify problems that are not visible during ordinary browsing.
Checking Forms and Purchase Processes
Do not limit your tests to the homepage. Check the entire user journey, especially the points where users need to take a specific action.
For an online store, it is worth going through product search, variant selection, the cart, the order form, and payment. For a service website, test the journey from finding an offer through to sending an inquiry.
Automated Testing Tools
Automated tools can detect some problems, such as missing labels, certain structural errors, or insufficient contrast.
However, they do not detect every barrier. They cannot fully assess whether an image’s alternative text is meaningful, whether the information is presented in a clear order, or whether users can actually complete a task.
Therefore, automated testing should be one part of an audit, not its only method.
8. Is Installing an Accessibility Plugin Enough?
This is one of the most common myths.
Tools are available on the market that offer additional panels allowing users to change text size, contrast, spacing, or how the page is displayed.
These features may help some users, but they do not automatically fix errors in the code, document structure, or interface functionality.
If a button does not have an accessible name that a screen reader can read, a form does not communicate errors, and a menu cannot be operated with a keyboard, a contrast adjustment panel alone will not solve these problems.
Accessibility should be considered during a website’s design and implementation, not treated as an overlay added at the very end.
9. How Should You Improve the Accessibility of an Existing Website?
If a website is already up and running, that does not mean it needs to be redesigned from scratch immediately. Many problems can be fixed as part of planned modernization work. The scope depends, however, on the website’s architecture, code quality, components used, and the scale of the issues identified.
A structured process is a good place to start.
Stage 1. Defining the scope
First, determine whether the website or service is subject to specific legal requirements. If so, establish which parts of the service and user journeys need to be assessed.
Stage 2. Audit
Next, analyze the website for accessibility barriers. It is worth checking not only the homepage, but also page templates, forms, search, menus, interactive elements, and key processes.
Stage 3. Prioritizing issues
Not all errors are equally significant. Start with barriers that prevent or substantially hinder users from completing basic tasks, such as contacting you, registering, or making a purchase.
Stage 4. Implementing fixes
The work may involve changes to code, HTML structure, CSS styles, interface components, forms, content, and multimedia.
Stage 5. Retesting
Once changes have been implemented, the corrected elements should be checked again. It is worth testing not only individual components, but also entire user journeys.
Stage 6. Maintaining accessibility
A website does not remain accessible automatically forever. New subpages, updates, content published by editors, and changes to components can introduce new barriers.
That is why it is worth incorporating accessibility into design standards, content publishing processes, and tests carried out as the website is developed.
10. Accessibility as Part of Good UX and Technical Quality
Accessibility and UX should not be treated as two separate worlds.
Well-designed navigation, clear messages, a logical information order, sufficient contrast, and predictable interface behavior help a wide range of users.
This does not mean that every design decision should lead to a simplified appearance. Modern design, animations, complex layouts, and custom components can coexist with accessibility, provided they are designed and implemented correctly.
The key is to ensure that the visual layer does not limit users’ ability to use the website’s features.
At Web24, we view a website as a combination of UX/UI design, information architecture, code, content, and technology. That is why accessibility should be considered at the solution planning stage, rather than only when there is a need to fix a finished product.
Summary: An Accessible Website Is One People Can Actually Use
Digital accessibility is not merely a formal requirement or a passing trend. It concerns the fundamental purpose of a website: enabling users to find information and complete the task they need to perform.
For services covered by the Polish Accessibility Act, this also entails specific legal obligations. Their scope depends on the type of service, the status of the entity, and the exemptions provided for in the Act. That is why the first step should be a thorough assessment of the situation, rather than automatically assuming that the same rules apply to every website.
Regardless of legal obligations, it is worth checking whether the website can be conveniently used with a keyboard, whether forms are understandable, whether content is readable, and whether key features work with assistive technologies.
A good website does more than look good. It gives users the opportunity to benefit from what it offers.
If you are planning a new website, online store, or application, accessibility should be considered from the outset of the design process. If your website is already up and running, start with an audit and identify which barriers make it hardest to use.
This approach benefits both users and the quality of the digital product itself.



