Your online shop has to be accessible by law. I find the barriers and fix them in the code.

WCAG 2.1 AA audits and remediation for shops and services in Germany, Austria and Romania. The European Accessibility Act has applied since 28 June 2025, and market surveillance and the first warning letters have started.

EU: European Accessibility Act. Germany: BFSG. Austria: BaFG. Romania: Legea 232/2022. The technical standard behind all four is EN 301 549, which means WCAG 2.1 level AA.

Illustration: a typical product page with four barriers marked. The product image has no text alternative, the search field has no label, the button text has a contrast of 3.3 to 1 instead of 4.5 to 1, and the wishlist icon button has no name.

Results of my study of 42 shop homepages

  • 42homepages audited on 15 September 2026: 24 in Romania, 18 in Germany
  • 37 of 42fail at least one WCAG 2.1 AA check that a scanner can detect
  • 100 %of the Romanian shops fail, and 72 % of the German ones
  • 4 issuescause 87 % of all failures: contrast, empty links, missing alt text, unnamed buttons

Automated checks find only part of the barriers, so these are lower bounds. Method, table and observations.

What the law asks of you

Three things every shop owner should know before the market surveillance letter arrives.

  • It has applied since 28 June 2025

    The European Accessibility Act covers online shops, banking, ticketing and transport, telecom and e-books. Existing sites get no general grace period; only contracts signed before that date have transitional rules.

    Micro-enterprises with fewer than 10 staff and under 2 million € turnover are exempt for services.

  • The bar is WCAG 2.1 AA

    The law points to EN 301 549, which points to WCAG 2.1 level AA: sufficient contrast, full keyboard use, names for every control, sensible structure, usable forms and zoom to 200 %.

    You also have to publish an accessibility statement.

  • Enforcement has started

    Germany: fines up to 100,000 € under § 37 BFSG, warning letters since August 2025, and the market surveillance office (MLBF) scanning shops from autumn 2026.

    Romania: ANPC, ADR and ANCOM supervise Law 232/2022. Austria enforces the BaFG.

How I work

Audit first, then fixes in your actual code, then a statement you can stand behind.

  1. Quick check, 3 working days

    Automated scan of your home, product and checkout pages plus a manual keyboard and screen-reader pass. You get a prioritised list and a fixed-price quote for the rest.

  2. Full audit, 2 weeks

    Every template against the WCAG 2.1 AA checklist: NVDA and VoiceOver, keyboard only, 200 % zoom, mobile. A report your developers can work from, and a draft accessibility statement.

  3. Fixes in code

    I implement the fixes in your theme or front end, Shopify, WooCommerce, Magento, Shopware or custom, as pull requests you can review. Each fix is re-tested.

  4. Statement and monitoring

    The accessibility statement goes live, a monthly scan watches for regressions, and every release gets a spot check.

Services and prices

Fixed prices where the scope is fixed, a quote where it depends on your code. All prices exclude VAT.

Four services with scope, delivery time and price
Detail Quick check Full audit Fixes in code Monitoring
Best for Knowing where you stand before you budget Shops and services that need a complete picture and a statement Getting to conformance without tying up your own team Staying conformant after every release
Included 3 key pages, automated and manual checks, prioritised list, quote Up to 10 templates, full WCAG 2.1 AA checklist, screen readers, keyboard, zoom, mobile, developer report, statement draft Implementation in your codebase as reviewed pull requests, re-testing, final statement Monthly automated scan, quarterly manual spot check, statement updates
Delivery 3 working days 2 weeks Depends on scope, typically 2 to 6 weeks Ongoing, cancel monthly
Price 490 € from 1,900 € from 2,500 €quoted after the audit 250 €per month
Action Book a quick check Request an audit Ask for a quote Ask about monitoring

Agencies: I also work white-label, audits and fixes delivered under your name.

What a finding looks like

Every issue in my reports names the rule, the impact, how many elements are affected, where they are, and the fix. This one is real, taken from a mid-size Romanian electronics shop in the study.

Read the full sample report or see six common barriers before and after.

Carousel buttons have no accessible name

Critical
WCAG 4.1.2 Name, Role, Valueaxe rule button-name9 elements
Found
The slider dots on the homepage are buttons containing an empty span. A screen reader announces “button” nine times with no indication of what each does.
Fix
Give each button a visible or visually hidden label, and mark the current one.
<!-- as found -->
<button class="owl-dot"><span></span></button>

<!-- fixed -->
<button class="owl-dot" aria-current="true">
  <span class="sr-only">Slide 1 of 9</span>
</button>
Daniel Butnar

Who you would work with

I am Daniel Butnar, a web developer in Brașov. I build with Next.js, React and plain HTML, and I have held my own sites to WCAG AA since before the law required it. I speak German, Romanian and English, so the audit, the statement and the developer hand-off arrive in your language, and I can talk to your agency directly.

I use automated tooling, including AI-assisted code review, to cover ground fast. Every finding in a report has been checked by hand, because scanners only find part of the picture and a report full of false positives wastes your developers’ time.

  • axe-core
  • NVDA
  • VoiceOver
  • Keyboard only
  • 200 % zoom
  • Chrome and Firefox
  • iOS and Android

Book a quick check

Send me the address of your shop. You get a reply within one working day, and the report within three.

Prefer e-mail? Write to daniel.butnar@gmail.com.

The form is delivered by FormSubmit; see the privacy page. No cookies are set.

I reply to this address.