Every week we check your site against WCAG 2.2 AA and explain each issue in plain words: what shoppers run into, how serious it is and how to fix it on your platform.
The cart button has no name
A shopper using a screen reader only hears “button” and cannot tell that it adds the product to the cart.
How to fix it in Shopify
In the product template, give the icon button the text “Add to cart”, visible or as an aria-label.
button-nameWCAG 4.1.2EN 301 549 9.4.1.2
Standards we check against
Clients in the EU increasingly ask for proof that a site is accessible. Here is what has changed.
28 June 2025
the date from which the European Accessibility Act applies to online shops and other B2C services in the EU
Source: Directive (EU) 2019/882
10 of 47
online shops had accessibility violations in checks by the Czech inspectorate ČOI in Q2 2026
Source: ČOI, August 2026
5,000+
website accessibility lawsuits were filed in the US in 2025, about 70% of them against online shops
Source: UsableNet, 2025 report
There are no confirmed EAA fines for shops yet. We are not here to scare you, but to show what to fix first.
Start with a free check of one page. No sign-up, about a minute.
The first page has a summary and the three most important issues. Then come instructions for your platform and an appendix for your developer.
The weekly check compares before and after and tells you if new issues appear after a site update.
The report is built automatically from a library of rule cards. Each card answers the site owner’s questions; the technical details are in the appendix.
The issue in plain words and how many times it appears on the site.
Critical, serious, moderate or minor, so it is clear where to start.
Which shoppers run into the issue and how it stops them from buying.
Instructions for Shopify, WooCommerce, PrestaShop or Shoptet.
The WCAG 2.2 and EN 301 549 criterion, the element selector and a code snippet.
Clients in Germany or Poland ask about the EAA, and nobody has time to write reports in their language. We check their sites every week and prepare reports under your brand.
First find out whether the law applies to you. If it does, the report shows what to fix first.
The EAA applies to you if the answer to all three questions is “yes”
We also work with Ukrainian companies selling in the EU and with contractors for government websites (ДСТУ EN 301 549:2022). Contact us
Automated tools find only some of the issues, between a third and a half by different estimates. That is why we do not promise “full compliance”, but offer regular monitoring and clear priorities.
| Pandus | Overlay widget | Manual audit | |
|---|---|---|---|
| Finds the cause in the site’s code | Yes | No | Yes |
| Tells the owner what to fix first | Yes | No | Partly |
| Checks the site every week | Yes | No | No |
| Tests keyboard use, content and checkout flows | No | No | Yes |
| Promises compliance with “one line of code” | No | Yes | No |
In 2025 the FTC ordered accessiBe to pay $1 million over claims that its widget makes sites WCAG-compliant. Why overlays do not work
Monthly subscription with no long contract. Pay by card or by invoice in hryvnia or euro.
$39 per month
$149 per month
$79 one-off
No. It is an automated check, not a full audit and not legal advice. It finds a subset of WCAG 2.2 AA issues; the rest can only be found with manual testing, for example with a keyboard and screen readers.
Not necessarily. It covers specific consumer services, such as e-commerce, and it exempts micro-enterprises that provide services. Our three-question filter helps you check.
No. We do not add a widget to your site or promise a “one-line fix”. We find the issues in your code and content and explain how to fix them in your platform’s code or theme.
English, Ukrainian, German, Polish, Czech, Romanian and Russian. Agencies can issue reports under their own brand.
No. We check pages the same way a visitor sees them in a browser. There is nothing to install.
One page, about a minute, no sign-up. You get the three most important issues with explanations.