Awwwards
404media is now part of Awwwards. Find our studio profile and work there.

Since 28 June 2025 Austrian online shops and booking sites must be accessible. Who falls under the BaFG, who is exempt, and a practical checklist to fix your site.
Christoph SpeiserProject lead & salesShort answer: under Austria's Accessibility Act (Barrierefreiheitsgesetz, BaFG) your website must be accessible if consumers can conclude a contract online through it, for example in an online shop or a booking system, and your company is not a micro-enterprise. The law has applied since 28 June 2025, the practical standard is WCAG 2.1 AA (via EN 301 549), and fines go up to €80,000. A brochure site with a contact form is usually not covered.
Since the law came into force we have been asked one question more than any other: "Does this apply to me?" The honest answer is that many small company websites in Austria are not covered at all, while many shops that think they are fine are not.
This guide explains who is affected, what "accessible" means in practice, what you have to publish, who checks it and what it typically takes to fix an existing site. It is not legal advice; for borderline cases, ask the WKO or a lawyer. But it should let you judge where you stand in ten minutes.
The BaFG is Austria's implementation of the European Accessibility Act (EU Directive 2019/882). It sets accessibility requirements for certain products (such as computers, smartphones, ATMs, ticket machines, e-readers) and certain services, and it has applied to new products and services since 28 June 2025.
For websites the relevant part is the services. The aim is simple: people with disabilities (for example blind people using a screen reader, people who can't use a mouse, people with low vision or cognitive impairments) should be able to buy, book and sign up online like everyone else. Public bodies were already covered by a separate law, the Web-Zugänglichkeits-Gesetz; the BaFG now extends similar duties to private companies.
The law covers a closed list of services. For most businesses the decisive one is "services in electronic commerce": services provided electronically, on a consumer's request, with a view to concluding a consumer contract via a website or mobile app. In plain terms, that covers:
Not covered are B2B-only websites, and websites that only present a company and invite enquiries without a contract being concluded online. A tradesperson's site with a contact form, an architect's portfolio or a doctor's site without online sales is generally outside the scope.
| Your website | Covered by the BaFG? |
|---|---|
| B2C online shop, company with 10+ staff | Yes |
| Hotel with online booking and payment | Yes, unless micro-enterprise |
| Course provider selling tickets online | Yes, unless micro-enterprise |
| B2B shop for trade customers only | No |
| Company website with contact form, no online contract | Generally no |
| Micro-enterprise (under 10 staff, max. €2m) with online shop | No, exempt for services |
| Manufacturer of covered products (any size) | Yes, product rules apply |
Micro-enterprises that provide services are exempt from the service requirements. Under the BaFG a micro-enterprise employs fewer than 10 people and has an annual turnover or annual balance sheet total of no more than €2 million.
Three points people often miss:
There are also transition periods: services that use products already in use before 28 June 2025 may continue until 27 June 2030, and contracts concluded before that date may run until they expire, for at most five years. A new or relaunched shop does not benefit from these.
The BaFG itself describes requirements in general terms: perceivable, operable, understandable, robust. Compliance with harmonised European standards creates a presumption of conformity, and for websites that standard is EN 301 549, which refers to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA. In practice, WCAG 2.1 AA is the benchmark everyone works with. WCAG 2.2 adds a few criteria and is a sensible target for anything built new.
WCAG AA has around 50 success criteria. The ones that cause most failures on real shops and booking sites:
| Area | What WCAG 2.1 AA requires | Typical failure |
|---|---|---|
| Contrast | Normal text 4.5:1, large text 3:1 against the background | Light grey text on white, white text on photos |
| Keyboard | Everything usable without a mouse, visible focus | Menus, filters or cookie banners only work by click |
| Images | Meaningful alt text; decorative images hidden | Product photos without alt text, icons as images |
| Forms | Visible labels, clear error messages | Placeholder instead of label, errors only in red |
| Structure | Real headings, lists, landmarks | Headings that are just bold text |
| Zoom and mobile | Usable at 200 % zoom and 320 px width | Content cut off, horizontal scrolling |
| Media | Captions for video with sound | Product videos without subtitles |
| Checkout | Every step usable with a screen reader | Payment widget or date picker not readable |
One warning from experience: so-called accessibility overlays, scripts that add a toolbar with "accessibility mode", do not make a site compliant. They don't fix missing labels or a checkout that can't be used with a keyboard, and they sometimes get in the way of screen readers. Accessibility has to be in the code.
Yes, in substance. Service providers must provide the information listed in Annex 3 of the BaFG and make it available in an accessible form. That covers a general description of the service, explanations needed to understand how it works, and a description of how the service meets the accessibility requirements. In practice this is usually published as an accessibility statement (Barrierefreiheitserklärung).
The law allows it in the terms and conditions or in another document. The WKO recommends a separate, easy-to-find page, for example linked in the footer next to the imprint and privacy policy, rather than hiding it in the T&Cs. A good statement contains:
Market surveillance lies with the Sozialministeriumservice, centrally organised at its Upper Austria office. It can check websites on its own initiative, and consumers can report violations to it. If a service doesn't comply, the provider is asked to fix it; if that doesn't happen, the authority can impose fines.
The maximum fines under § 36 BaFG are graded by violation and company size:
| Violation | Large companies | SMEs and micro-enterprises |
|---|---|---|
| Product or service not meeting the accessibility requirements | up to €80,000 | up to €50,000 |
| Conformity procedure, documentation, labelling | up to €40,000 | up to €25,000 |
| Record-keeping, information and cooperation duties | up to €16,000 | up to €10,000 |
Fines are the last step, not the first. The bigger practical risk is losing customers who can't complete a purchase, and the cost of an emergency fix under time pressure.
You can do a first check yourself in an hour. It won't replace a full audit, but it shows whether you have a small or a big problem:
Automated tools find roughly the technical part of the problems; keyboard and screen-reader tests find the rest. If points 1, 2 or 10 fail, the checkout is effectively closed to some of your customers.
It depends on how the site was built far more than on its size. Honest rules of thumb:
| Starting point | Typical effort |
|---|---|
| Modern custom site, clean code, a few issues | Small: contrast, labels, alt texts, focus styles |
| Shop system with a well-maintained theme | Medium: theme fixes, checkout check, statement |
| Old theme with many plugins, page builder | High: often cheaper to rebuild the templates |
| Third-party booking or payment widget | Depends on the provider: ask them for their conformity status |
The cheapest moment is a relaunch: if accessibility is part of the design and the component library from day one, it costs little extra. So when you plan a new website or shop, put contrast, keyboard use and the checkout on the brief from the first workshop, not on the list for after launch. If you are planning a relaunch anyway, read how to relaunch without losing SEO and what a website costs in Austria. Ask about funding too: the federal digitalisation funding has ended, but regional programmes may fit. Status and alternatives: our funding article.
Even then, most WCAG basics (contrast, readable text, clear forms, keyboard use) make a site better for everyone and are increasingly what Google's own quality checks such as Lighthouse look at. It's rarely wasted effort.
We check your website or shop against the key WCAG 2.1 AA criteria and tell you plainly what has to change and what it takes. Book a free strategy call and get a fixed quote.
Only if consumers can conclude a contract online through it, for example in a shop or booking system, and your company is not a micro-enterprise. A site that presents your business and has a contact form is generally not covered.
Since 28 June 2025. Services using products already in use before that date may continue until 27 June 2030, and older contracts may run until they expire, for at most five years.
The BaFG refers to harmonised standards; for websites that is EN 301 549, which points to WCAG 2.1 level AA. WCAG 2.2 is a sensible target for anything built new.
Micro-enterprises providing services: fewer than 10 employees and an annual turnover or balance sheet total of no more than €2 million. Manufacturers of covered products are not exempt, whatever their size.
Up to €80,000 for large companies and up to €50,000 for SMEs if a service doesn't meet the requirements; lower maximums apply to documentation and information duties. The Sozialministeriumservice enforces the law.
No. Overlays add a toolbar but don't fix the underlying code: missing labels, keyboard traps or an inaccessible checkout remain. Accessibility has to be built into the templates.

More lessons from our projects in Vienna.
Websites • • 9 min read
Patryk WisniewskiWebsites • • 9 min read
Patryk WisniewskiWebsites • • 8 min read
Christoph Speiser
Tell us about your project. Christoph gets back to you personally.
Christoph Speiser, Project lead & sales