Free mini check

European Accessibility Act · WCAG 2.1 AA

Find out in 48 hours if every customer can buy from your shop.

We test your webshop the way people with disabilities use it: keyboard only, with a screen reader, zoomed in. You get the real barriers with screenshots and a clear fix for each one.

Free and without obligation. No logins, no payment details.

Prefer to write yourself? ivan@everyonecanshop.com

Portrait of Ivan Raylyan

Your contact

Ivan Raylyan, Engineering & Delivery Manager

We test every page with AI support. Ivan personally reviews every finding before the report reaches you.

See a sample report

Mini check · example

3 barriers on the purchase path

  1. HighAdd to cart: keyboard focus not visibleWCAG 2.4.7
  2. HighColour options: images without textWCAG 1.1.1
  3. MediumQuantity field has no labelWCAG 1.3.1
Reviewed by Ivan Raylyan Delivered within 48 hours
Example: summary of a mini check
  • WCAG 2.1 AA · EN 301 549 · EAA
  • No logins or code access
  • Every report reviewed by a person
  • Fixed prices, from €490

Why this matters now

Since 28 June 2025 the European Accessibility Act applies to webshops that sell to consumers in the EU. Regulators have started checking, and most shops still have barriers on the way to checkout.

9 / 10

European homepages fail automated accessibility checks. Retail ranks last of 15 sectors.

Source: Digital Trust Index 2026

61%

of the largest Dutch shops tested by the regulator ACM did not let a customer using assistive technology place an order.

Source: ACM, March 2026

28.06.2025

The EAA applies to e-commerce. National authorities can demand fixes and impose penalties.

Source: Directive (EU) 2019/882

What waiting costs you

  • Customers who leave quietly

    If a button cannot be reached with the keyboard or a field has no name, a customer using assistive technology cannot finish the order. Most do not complain. They buy elsewhere.

  • Letters from the regulator

    National authorities can check your shop, ask for fixes within a deadline and impose penalties. The Dutch ACM has already tested large shops and published the results.

  • Warning letters in Germany

    If you sell to German customers: missing accessibility under the BFSG can also be challenged under competition law, for example with a formal warning letter (Abmahnung).

The good news: most barriers are small code changes once you know where they are.

This is what you receive

Every finding has the place, a screenshot, who is affected and exactly how to fix it. Your developers can start right away, without having to research anything.

Accessibility report · excerpt

Purchase path: product page

Shop
Dutch webshop (anonymised)
Standard
WCAG 2.1 AA / EN 301 549
Tested with
Keyboard, screen reader, 200% zoom
Reviewed by
Ivan Raylyan

Finding 1

Add to cart button: keyboard focus is not visible

Severity
High
WCAG
2.4.7 Focus Visible (AA)
Where
Product page, main buy button

What we saw

We moved through the page with the Tab key. The button receives focus, but its look does not change at all.

Product page section with a quantity field and an orange In winkelwagen (add to cart) button. The button has keyboard focus, but nothing shows it.

Who is affected

Customers who use a keyboard instead of a mouse, for example because of a motor impairment or after a hand injury. They cannot see which element is active and cannot safely add the product to the cart.

How to fix

Add a clearly visible focus style for keyboard users. :focus-visible leaves the look for mouse users unchanged.

.add-to-cart:focus-visible {
  outline: 3px solid #13212c;
  outline-offset: 3px;
}

Finding 2

Colour options are images without a text alternative

Severity
High
WCAG
1.1.1 Non-text Content (A)
Where
Product page, colour selection

What we saw

The colour swatches are images without an alt attribute.

Screen reader announces
"image", "image", "image"
After the fix
"Moss green", "Ocean blue", "Sand"

Who is affected

Blind and low-vision customers using a screen reader. They hear only "image" three times and cannot choose a colour, so they cannot order.

How to fix

Give every option image a short alt text that names the colour.

<img src="moss.jpg" alt="Moss green">

Finding 3

Quantity field and its buttons have no name

Severity
Medium
WCAG
1.3.1 Info and Relationships (A), 4.1.2 Name, Role, Value (A)
Where
Product page, quantity selector

What we saw

The field has no label, and the minus and plus buttons only contain a symbol.

Screen reader announces
"button", "edit text, 1", "button"
After the fix
"Decrease quantity", "Quantity, 1", "Increase quantity"

Who is affected

Screen reader users. They hear an unnamed edit field and two unnamed buttons, and have to guess what they do.

How to fix

Connect a label to the field and give both buttons an accessible name.

<label for="qty">Quantity</label>
<button aria-label="Decrease quantity">-</button>
<input id="qty" type="number" value="1">
<button aria-label="Increase quantity">+</button>

Finding 1 comes from a real check of a Dutch webshop, anonymised. Findings 2 and 3 show typical issues in the same format. A full audit covers up to 8 pages and every finding is in this format.

What we check

We follow the path a real customer takes: find a product, choose options, add to cart, go to checkout.

  • Keyboard path to checkout

    Can every step be done without a mouse, and is it always visible where the focus is?

  • Screen reader names

    Do buttons, images, product options and fields announce what they are?

  • Contrast and zoom

    Is text readable for people with low vision, and does the page still work at 200% zoom?

  • Forms and errors

    Are fields labelled, and are errors explained in a way everyone can understand?

  • Mobile

    Does the purchase path work on a phone, including zoom and screen orientation?

  • Accessibility statement

    The EAA asks you to explain how your service meets the requirements. We draft it for you.

Packages and prices

Start free. Pay only if the mini check shows it is worth it. Fixed prices, no hourly billing.

Start here

Mini check

Free no obligation

See what blocks your customers before you spend anything.

Delivered within 48 hours

  • 2-3 real barriers on your purchase path
  • Screenshots, who is affected, how to fix
  • Reviewed by Ivan personally
  • No logins, no code access, no payment details

No obligation: afterwards you decide if you want more, or not at all.

Get my free mini check

Recommended

Full audit

from €490 one-off, fixed price

The complete picture and a fix list your developers can work through.

Delivered within 5 working days

  • Up to 8 key pages: home, category, product, cart, checkout
  • Keyboard-only and screen reader checks
  • Desktop and mobile
  • Prioritised fix list with WCAG references and code examples
  • Draft accessibility statement
Ask for a full audit

Re-test

€200 one-off

Proof that the fixes work.

  • After your developers fix the issues
  • Every finding checked again
  • Updated report you can show

Monitoring

€79 per month

Stay accessible after every release.

  • Monthly check of your key pages
  • Alert when a release breaks something
  • Short quarterly summary

Prices for business customers, excluding VAT (reverse charge within the EU).

How it works

  1. Send your URL

    Use the form or one email with your shop address. That is all we need.

  2. Free mini check

    Within 48 hours: the most important barriers with screenshots and fixes.

  3. Full audit, if you want it

    Within 5 working days: the complete report and fix list.

  4. Fix and re-test

    Your developers fix, we confirm it works.

Portrait of Ivan Raylyan

Ivan on LinkedIn

Your contact: Ivan Raylyan

Engineering & Delivery Manager · Bucharest, Romania

I lead engineering and delivery across several IT projects, from product development to outsourcing. I started in QA: manual testing first, then test automation with Selenium, Cypress and Pytest.

For more than 6 years I have worked on SaaS products in compliance-heavy fields: legal, regulatory and financial tech. There, every finding needs evidence and every release has to hold up. We bring the same discipline to your shop.

At EveryoneCanShop we use AI agents for the repetitive work. For your audit that means AI-assisted testing covers every page quickly, we walk the purchase path step by step with the keyboard, check what a screen reader announces for every button, image and field, and I personally review every finding and every report before it goes out.

You get the speed of automated testing and the judgement of someone who has run releases and quality for years.

In short

  • Engineering & Delivery Manager
  • Started in QA: manual testing, then Selenium, Cypress, Pytest
  • 6+ years in compliance-heavy SaaS
  • Works with AI agents every day

Why not an agency or a widget?

An honest comparison of the three usual options.

Classic agency audit

Price
€1,500-5,000 per audit
Time
Often several weeks
Fixes the code?
Yes, if your developers implement the report
What you get
A detailed report, often very long

Overlay widget

Price
Monthly subscription
Time
Installed in minutes
Fixes the code?
No, the code underneath stays the same
What you get
A toolbar on top of your shop

EveryoneCanShop

Price
Fixed price, from €490
Time
5 working days
Fixes the code?
Yes, your developers get an exact fix list
What you get
Prioritised findings with screenshots, WCAG references and code, reviewed by a person

Questions

Does the EAA apply to my shop?

It applies to businesses that sell to consumers in the EU. Microenterprises providing services are exempt: fewer than 10 employees and an annual turnover or balance sheet total of up to €2 million. If you are above that, it most likely applies. This is not legal advice.

How do you test without access?

We visit your public shop like a customer: browse, choose a product, add it to the cart and go through checkout up to the payment step. We use the keyboard, a screen reader, zoom and automated checks. Nothing to install, no logins, no code access.

Is our data safe?

We only see what every visitor sees. We never place real orders: we stop before payment. We do not need customer data, passwords or admin access. Our own site uses no cookies and no tracking.

Will an accessibility widget solve it?

No. Widgets change how a page looks, but they do not fix the code underneath: unnamed buttons, keyboard traps and unlabelled fields stay. Regulators look at what customers can actually do.

What do you need from us?

Only your shop URL. If you want, tell us which pages matter most to you.

Do you fix the issues?

Usually your developers or agency fix them, using our report: every issue comes with the place, a screenshot and what to change. Afterwards we re-test.

What if you find nothing?

Then you get that in writing, with what we tested, at no cost. On real shops this is rare: in the ACM test, 61% of the largest Dutch shops blocked ordering with assistive technology.

Is the report a legal certificate?

No. It is a professional test against WCAG 2.1 AA, the technical standard behind EN 301 549 and the EAA. It shows where you stand and what to fix first.

Know where you stand in 48 hours

Send your shop URL. You get the first real barriers with screenshots and fixes, free and without obligation.

Your contact: Ivan Raylyan, Engineering & Delivery Manager

Free and without obligation. No logins, no payment details.

Prefer to write yourself? ivan@everyonecanshop.com