Back to Blog

Legal Compliance

Hotel Website Accessibility and the EU Accessibility Act: The Booking-Engine Trap

Your hotel homepage can be flawless while the one flow that takes money — your booking engine — is unusable for a blind guest. That gap is exactly what the EAA regulates, and where complaints land.

9 June 2026

13 min read

Ravid, Webply

Also in:

EN

DE

Why hotels are more exposed than they think

If one sector systematically underestimates its EAA exposure, it is hospitality. The mental model is "we are a hotel, not an online business." The law does not read it that way.

The EAA (Directive (EU) 2019/882) regulates e-commerce services — defined in Article 3(30) as services provided at a distance, by electronic means, at the individual request of a consumer, with a view to concluding a consumer contract. A hotel's direct booking engine — a calendar, a rate, a card field, a "Confirm booking" button — is a textbook e-commerce service. A tourist reserving and paying for a room at a distance is concluding a consumer contract. The hotel's physical nature is irrelevant; the online booking flow is the regulated service.

If you want the full map of which business types are in or out of scope, we wrote one: Who does the EAA actually cover?. This post is the hospitality deep-dive.

The booking engine is where compliance actually lives — and fails

Here is the uncomfortable part. The booking engine — the single most important commercial flow on the whole site — is almost always a third-party widget: SiteMinder, Cloudbeds, Mews, Little Hotelier, a channel-manager iframe, or a booking-engine plugin. And that widget is exactly where accessibility failures concentrate.

A hotel can have a flawless, hand-built marketing site and still fail the EAA entirely, because the one flow that takes money was never tested. AudioEye's 2025 Digital Accessibility Index scanned over 53,000 pages across more than 1,600 travel and hospitality websites and found the average hospitality page carried about 85 accessibility violations, including roughly 27 images with no alt text. Booking and reservation pages — dense with date pickers, dropdowns, and payment fields — are where the worst of those cluster.

These are the failure modes a real screen-reader or keyboard user hits on a typical hotel booking flow:

Every failure mode in our checkout-first e-commerce guide applies to a hotel booking engine — a booking flow is a checkout.

"But it's the vendor's widget" doesn't move the obligation

The most common hotelier objection, and the most dangerous one. Under the EAA, the service provider concluding the consumer contract is responsible — and on your direct booking engine, that is you, not SiteMinder or Mews. The widget being third-party software changes who you should push to fix it; it does not change who a regulator or complainant comes to.

So treat booking-engine accessibility as a procurement requirement, not an act of faith:

• Ask your booking-engine vendor for a written WCAG 2.1 AA / EN 301 549 conformance statement (an accessibility conformance report, sometimes called a VPAT). If they cannot produce one, that silence is your answer.
• Test the live embed on your own domain, not the vendor's polished demo. Configuration, your theme, and your CSS can break accessibility the vendor "supports" in principle.
• Put accessibility in the contract at renewal. Channel managers and booking engines compete hard for hotel business — conformance is a fair thing to demand.

Two more things hoteliers routinely miss:

Booking.com and Expedia don't cover you. The OTA is its own in-scope e-commerce service — but your own direct booking engine, the one you push hard to avoid OTA commissions, is your own service on your own legal hook. You cannot outsource your way out of your own checkout.

Kiosks and TVs are also in scope — and the exemption is narrower there. The EAA covers products, not only websites. Lobby self-check-in kiosks and card-payment terminals carry their own accessibility requirements, and modern interactive hotel-room TVs / IPTV systems can fall in scope when they provide access to audiovisual media, booking, or e-commerce-style guest services. Critically, the microenterprise exemption applies to services, not products — a small hotel that is exempt for its website is still on the hook for a check-in kiosk it deploys.

Are small hotels exempt? The microenterprise math

There is one real off-ramp for in-scope services: the microenterprise exemption. A service provider is exempt from the EAA's service obligations only if it has fewer than 10 employees AND annual turnover (or balance-sheet total) of €2 million or less — both conditions, at the same time.

This is where small hotels get it wrong. A boutique hotel with 6 staff but €2.4M in annual room revenue is not a microenterprise — the turnover threshold alone removes the exemption, regardless of headcount. Seasonal and family-run properties cross €2M turnover far more often than they cross 10 employees, so many that "feel small" are in scope. And remember: the exemption never covers products like kiosks and terminals, and it disappears the moment you cross either threshold, with no grace period.

If you are genuinely under both lines, write the figures down now. "We believed we were exempt, here is the headcount and turnover at the time" is a far stronger position than reconstructing it after a complaint.

The enforcement clock — and why hospitality is next

The EAA has applied since 28 June 2025, and it has teeth in all 27 member states. No headline hotel fine has landed yet — most authorities are giving businesses time to fix barriers first — but the machinery is live, and two things make hospitality a near-term target:

• Market-surveillance authorities are widening their audits in late 2026 to sectors they haven't yet touched — and hospitality is explicitly on that list. Travel and accommodation booking are named e-commerce categories in EU guidance, which makes them easy, obvious audit candidates.
• Private enforcement is already running. In Germany, law firms began sending warning letters (Abmahnungen) within weeks of the law taking effect, using competition-law mechanisms. France filed the first EAA-specific lawsuits in November 2025 — and every one was about a checkout, not a homepage.

Penalty ceilings vary widely by country, so the exposure depends on where your guests and your establishment sit:

Figures are indicative ceilings from national transpositions, not expected fines. For the full country-by-country breakdown see our EAA fines guide and the 2026 fines explainer.

The honest hotel checklist

If you run a hotel with a direct booking engine, here is the order of work that actually reduces risk:

1. Scan the booking flow, not the homepage. Point an automated WCAG 2.1 AA scan at the actual reservation steps — date selection, room choice, guest details, payment. That is the regulated surface, and the one most "we ran a scan" efforts skip.
2. Keyboard-test and screen-reader-test the booking engine. Try to complete a real booking using only the Tab/Enter keys, then with a screen reader (VoiceOver or NVDA). The worst failures — focus traps, dead date pickers, silent errors — are the ones automation only partly catches.
3. Get a conformance statement from your booking-engine vendor. Make WCAG 2.1 AA / EN 301 549 conformance a contract condition at renewal. The widget is theirs to fix; the obligation is yours.
4. Publish an accessibility statement. The EAA requires one, and several countries fine specifically for its absence. Use our EU accessibility statement template.
5. Don't forget physical products. If you deploy check-in kiosks or payment terminals, they carry their own (microenterprise-exempt-proof) obligations.

The point is precision, not panic. The homepage redesign is not where your risk is — the booking engine is. Fix the flow that takes money, document your statement and your microenterprise position, and you have addressed the part of the EAA that actually bites a hotel.