skip to content

accessibility 13 min read

Online store accessibility: WCAG and the EAA in e-commerce

Store accessibility has been an EAA requirement since 2025 (WCAG). Check who it applies to, which barriers block a purchase and how to bring a store into compliance.

Online store accessibility: WCAG and the EAA in e-commerce

Store accessibility means a customer can view a product, add it to the basket and place an order even when they use a screen reader, a keyboard instead of a mouse, high magnification, or have a temporary difficulty using the site. What counts is real buying, from the first click to the order confirmation.

What online store accessibility is

What online store accessibility is

AI-generated image

In practice, online store accessibility concerns the whole purchase path. The home page, product listing, product page, basket, checkout, payment, customer account, terms and conditions, transactional emails and contact form should work in an understandable and predictable way.

WCAG helps turn this subject into specific technical requirements. Put simply: content should be possible to notice, the interface possible to operate, messages possible to understand, and the code possible to read for browsers and assistive technologies. For a store that means, among other things, correct field labels, visible keyboard focus, sensible headings, alternative text on photos, adequate contrast and clear error messages. I explain this in more detail in the introduction to web accessibility (WCAG).

E-commerce accessibility is also a business matter. If a customer cannot choose a product variant, read the sale price, correct an error in a form or get through payment, the store loses the order. Sometimes that customer reports the problem. Sometimes they just leave.

The EAA and Polish law: since when a store has to be accessible

The EAA and Polish law: since when a store has to be accessible

AI-generated image

The EAA, the European Accessibility Act (Directive 2019/882), took effect in Poland through the ustawa o zapewnianiu spełniania wymagań dostępności (the act on ensuring that accessibility requirements are met, Dz. U. 2024 poz. 731), which came into force on 28 June 2025. For e-commerce it covers e-commerce services provided to consumers, which means typical online stores selling online.

The Polish act names e-commerce directly as one of the services covered by the accessibility requirements. The definition concerns services offered or provided at a distance through websites and mobile devices, by electronic means, at the individual request of a consumer, with a view to concluding a contract. For a store owner that sounds technical, but the meaning is simple: if a customer can buy a product through your site, the subject probably applies to you.

In e-commerce the requirements focus especially on the elements that lead to a transaction. A store should provide accessible information about products and services, if such accessibility information has been supplied by the responsible party. The functions connected with identification, security, payments and payment services should be accessible too. That means logging in, registration, confirming details, going through the basket and paying for the order.

The act also provides for supervision and penalties. For e-commerce services the supervisory authority is the minister responsible for digital affairs. A fine can reach up to ten times the average monthly salary for the previous year, with a cap of 10% of turnover from the previous financial year. So this is more than a formality in the terms and conditions.

Who it applies to and who is exempt (microbusinesses)

The obligations apply to stores offering e-commerce services to consumers, with the exception of services provided by microenterprises. A microenterprise is a company that employs fewer than 10 people and has an annual turnover or annual balance sheet total of no more than EUR 2 million.

The exemption for microbusinesses does not mean the subject can be put aside completely. First, a company’s status can change. Second, store accessibility affects sales and customer service regardless of the statutory threshold. Third, some companies work with larger partners, marketplaces or institutions that may require a certain level of accessibility in the contract.

If you are close to the threshold or are not sure whether the exemption covers your particular sales model, check it with your accountant or a lawyer. On the technical side it is sensible to improve the store in stages anyway, starting with the places where the customer makes a decision and pays.

The most common accessibility barriers in stores

The most common problems are not hidden deep in the code. They usually show on the basic path: product, basket, customer details, payment and order confirmation.

Stores on WooCommerce and Shopify often repeat similar barriers. A button looks like a button, but has no name for a screen reader. A form shows an error in red, but does not say what needs correcting. A discount popup takes over the focus and cannot be closed with the keyboard. A product variant is available only by clicking with a mouse. The sale price is visually clear, but in the code it comes in an order that confuses a user of assistive technologies.

Product page and photos

The product page should give the customer all the information needed to decide. That covers the name, price, variants, availability, photos, description, reviews, delivery costs and the add to basket button.

Product photos need good alternative text, but not every image has to be described in the same way. A decorative thumbnail can have an empty alt. A photo that shows the colour, texture, connector layout or condition of the product should get a description that carries that information. If you sell clothes, “dress” is not enough. It is better to describe the cut, the colour and the detail that affects the choice.

Galleries can be a problem too. The user should know which photo is active, be able to switch between photos with the keyboard and not lose their place on the page after closing the enlarged view. If the variant “black, size M” changes the photo and the price, that change should be understandable without looking at the screen as well.

Basket and completing the order (checkout)

The basket and checkout are places where a small barrier quickly becomes a lost sale. The customer has already decided, so the store should lead them calmly through their details, delivery, payment and acceptance of the terms.

The most common problems are fields without labels, errors shown only after the form is submitted, messages such as “invalid data” that do not point to a field, a basket session that is too short, an unreadable price summary and forced actions that cannot be done with a keyboard. In the checkout you also need to watch external payment modules, Paczkomat (InPost parcel locker) pickers, pickup point maps and invoicing plugins. These are frequent sources of problems, because the store looks consistent while part of the process runs on someone else’s component.

A well prepared checkout lets you go through the whole process with a keyboard. The focus is visible, the order of the fields makes sense and errors are described in text. The customer knows how much they will pay, which delivery method they chose and what will happen after they click the order button.

Forms, filters and search decide whether the customer finds the product and enters their details correctly. In store accessibility this is one of the most important areas to check by hand.

Filters should have readable labels, a selected state and keyboard operation. If the product list refreshes automatically after a size is chosen, the user should be told that the results have changed. Search should have a name, a sensible hint and a message for no results. A placeholder in the field does not replace a label, because it disappears once text is typed and is often read poorly by assistive technologies.

With forms, precision counts. The “Phone” field should say which format is accepted, if the store requires one. Marketing consents should be separated from the consents required to fulfil the order. An error message should point to the problem and how to fix it, ideally next to the specific field.

How to check your store’s accessibility (a quick audit)

A quick audit lets you find the biggest barriers without rebuilding the whole store. It does not replace a full WCAG audit, but it gives a good answer to the question of where a customer can get stuck.

Start by going through the purchase path without a mouse. Use Tab, Shift+Tab, Enter, Space and Esc. Check whether you can see where you are on the page, whether you can open the menu, choose a variant, add a product to the basket, change the quantity, go to the checkout and come back without losing data. If the focus disappears somewhere or you have to click with a mouse, you have a specific point to fix.

Then check contrast and magnification. With the page zoomed to 200% the content should still be readable, with no horizontal scrolling in typical places and no buttons covered up. Pay attention to prices, promotion labels, error messages, button text and footer links.

The next step is a screen reader. On macOS you can use VoiceOver, on Windows NVDA. You do not have to run an expert test straight away. It is enough to check whether the headings lead you through the page, the buttons have understandable names, the forms say what they expect, and the messages after adding to the basket are read out.

Finally, run automated tools, for example WAVE or an accessibility scanner in the browser. Treat the result as a hint. An automated tool will find some of the problems, such as missing labels or weak contrast, but it will not judge whether a photo description actually helps someone buy the product.

How much it costs to bring a store into compliance

The cost depends on the state of the store, the number of templates, the platform, the theme, the plugins and the checkout. First you have to check what really does not work, because two stores on the same platform can need a completely different scope of work. For comparison, it is worth looking at how much an online store itself costs. Accessibility is part of the same budget.

The smallest scope is a quick audit and fixes for the obvious barriers: contrast, field labels, alternative text, focus, error messages, heading order, button names. In a well maintained store some of these changes can be made without changing the design.

A larger scope appears when the problem sits in the theme, the page builder, a Shopify app or WooCommerce plugins. If the product filter, a popup, the Paczkomat picker or the payment is not accessible, sometimes you have to replace the component, write your own fix or limit the feature that blocks the purchase. That is no longer a cosmetic change.

Bringing a store fully into compliance usually includes an audit, a report with the errors, design and development fixes, tests after the changes go live and documentation of the changes. In larger stores there is also work on several page types: listing, product page, basket, checkout, customer account, blog, sales landing page, information page and emails. The more custom elements, the more testing.

The most sensible way to price store accessibility is in stages: first the diagnosis, then the fixes that are critical for buying, and at the end the remaining views and a maintenance process, so that new banners, apps and features do not undo the result after a month.

Where to start

Start with the places that affect the purchase: product page, basket, checkout, payment and forms. That is where store accessibility most closely connects legal requirements, customer experience and sales.

The first step is to write down the paths a customer has to go through. For a simple store these will be: finding a product, choosing a variant, adding to the basket, entering details, choosing delivery, payment and order confirmation. For a B2B store there may also be logging in, individual prices, a request for a quote or a recurring order. If you are only just starting an online store, plan accessibility from the beginning. Fixing it later costs more.

The second step is a quick manual audit. Go through these paths with a keyboard, with magnification and with a screen reader. Note the places where an action cannot be done, where it is not clear what happened, or where the message is too general. These will be the highest priority errors. If your legal situation requires it, an accessibility statement can help too.

The third step is deciding what you fix straight away and what you plan for a larger change to the store. If the checkout does not work with a keyboard, do not wait for a redesign. If the problem is the descriptions of hundreds of photos, set the rules and fix them in batches, starting with the bestsellers and the products with the most traffic.

E-commerce accessibility is best treated as part of maintaining the store. A new banner, a new plugin, a new delivery method or a change of payment provider can introduce a barrier. That is why, after a one-off audit, you need simple rules for the team: how to add photos, how to write button labels, how to check forms and when to test changes before publishing.

FAQ

Does my online store have to be accessible?

If you run e-commerce for consumers, most probably yes. Since 28 June 2025 the EAA and the Polish act have required it. Microenterprises are the exception. If a customer can buy a product through your site, assume the subject applies to you and check the details.

Does a microenterprise have to meet the accessibility requirements?

E-commerce services provided by microenterprises are exempt. A microbusiness means fewer than 10 people and an annual turnover or balance sheet total of up to EUR 2 million. The status can change, though, and accessibility helps you sell anyway, so it is worth improving the store in stages.

What are the penalties for an inaccessible store?

The act provides for supervision and fines: up to ten times the average monthly salary, with a cap of 10% of the previous year’s turnover. For e-commerce services, supervision is carried out by the minister responsible for digital affairs.

How can I quickly check my store’s accessibility?

Go through the purchase path without a mouse (Tab, Enter, Esc), turn on magnification to 200% and test the key views with a screen reader (VoiceOver or NVDA). At the end, run an automated scanner. It will not replace a full audit, but it will show where a customer gets stuck.

Where do I start with adapting a store to WCAG?

With the places where the customer pays: product page, basket, checkout and forms. Do a quick manual audit, fix the barriers that are critical for buying, plan the rest in stages and make accessibility part of the store’s regular maintenance.

Filip Chrapek

Let's work together

What do you need?
Budget
When?

Prefer email? hi@philgood.dev