Skip to main content
Sector Guide

Accessibility compliance for Hospitality & Travel

Accessibility compliance for hospitality and travel platforms

Regulatory context

Hospitality and travel digital services fall within EAA scope through multiple pathways. Booking engines and reservation platforms constitute e-commerce services under Article 2. Transport-related travel services (flights, rail, transfers) are directly covered as transport services. Online travel agencies (OTAs) and accommodation platforms are in scope as e-commerce intermediaries. EN 301 549 incorporating WCAG 2.1 Level AA is the applicable standard for all web and mobile interfaces. EU Passenger Rights regulations across air, rail, and bus transport add sector-specific accessibility requirements. The Package Travel Directive (2015/2302) requires that pre-contractual information be provided in an accessible manner. Hotels and accommodation providers in public sector or publicly funded properties may also fall under the Web Accessibility Directive.

Common issues Lumi finds in hospitality & travel websites

Booking engine and reservation flows

Hotel and flight booking engines involve date pickers, room or seat selectors, guest detail forms, and payment flows. Date range pickers are among the most consistently inaccessible components on the web - they rarely support keyboard navigation or announce selected dates to screen readers. Multi-room and multi-leg booking flows compound the complexity.

Property listing and detail pages

Accommodation listings with photo galleries, amenity lists, room type comparisons, and availability calendars frequently have inaccessible image carousels with missing alt text, amenity icons without text labels, and room comparison interfaces that rely on visual layout alone to convey differences.

Map-based search and location interfaces

Interactive maps showing hotel locations, nearby attractions, transport links, and area guides are almost universally inaccessible. Users need text-based alternatives - searchable location lists, distance-from-landmark information, and neighbourhood descriptions that don't require map interaction.

Guest review and rating systems

Review sections with star ratings, category scores, review text, and management responses frequently use visual-only rating indicators (filled stars, colour-coded scores) without text alternatives. Review filtering and sorting controls are often custom components lacking keyboard support.

Loyalty program and account dashboards

Loyalty program interfaces showing points balances, tier status, reward catalogues, and booking history use progress bars, tier badges, and visual status indicators that convey no information to screen readers. Points earning and redemption flows must be fully accessible.

Multi-language and currency switching

Travel platforms serving international audiences use language and currency selectors that are frequently built as custom dropdowns without proper ARIA markup. Content that changes based on locale selection must announce the change, and the switching mechanism itself must be keyboard accessible.

Hospitality & Travel-specific challenges

Hospitality and travel platforms face accessibility challenges driven by the richness of the browsing and booking experience. Travellers rely heavily on visual content - property photos, maps, and virtual tours - all of which need meaningful alternatives. Booking flows are complex multi-step processes involving date selection, room or seat choice, add-ons (meals, transfers, insurance), guest details, and payment. Third-party integrations are pervasive - channel managers, payment processors, map providers, review aggregators, and loyalty platforms all inject content that the primary site doesn't fully control. Seasonal promotions, flash sales, and dynamic pricing create constantly changing content that must remain accessible. Mobile usage is exceptionally high in travel, making mobile accessibility critical.

Compliance timeline

The EAA is enforceable from 28 June 2025 for new hospitality and travel services. Existing digital services have until 28 June 2030. Transport-related services are directly covered under the EAA's transport provisions. EU Passenger Rights regulations are already in force for air, rail, bus, and waterborne transport. OTAs and booking platforms operating across multiple EU markets face enforcement in each member state.

Check your hospitality & travel site now

Lumi scans against WCAG 2.2 and EN 301 549 using five scanning engines - free, no signup required.

Frequently asked questions

Does the EAA apply to hotel booking websites?

Yes. Hotel booking platforms constitute e-commerce services under the EAA and must meet EN 301 549 accessibility requirements. This covers the entire booking journey - from property search and listing pages through room selection, guest details, and payment.

Are online travel agencies covered by the EAA?

Yes. OTAs operating in the EU market fall within scope as e-commerce intermediaries. The booking flow, search and filter interfaces, property listings, payment processing, and post-booking management must all be accessible.

Do hotel websites need accessible map alternatives?

Yes. WCAG 2.1 Level AA requires that information conveyed through visual means has text alternatives. Interactive maps must be supplemented with accessible alternatives - text-based location descriptions, address information, distance from landmarks, and directions that don't depend on visual map interaction.

What accessibility requirements apply to travel loyalty programs?

Loyalty program digital interfaces must meet EN 301 549 as part of the overall service. Points balances, tier status, reward browsing, and redemption flows must be accessible. Visual status indicators (progress bars, tier badges) need text alternatives that screen readers can announce.

Related resources

Last reviewed: April 2026. Content is reviewed quarterly for accuracy.

Get accessibility insights in your inbox

WCAG guides, scanner updates, and industry news. No spam.