Hotel and B&B websites: what 608 Irish sites show
Published
A hotel website has one main job: getting guests to book. If a guest can’t fill in your booking form, they can’t stay with you. This guide covers what our research found on Irish hotel and B&B websites. It explains what the European Accessibility Act likely means for you, and what to fix first.
In a nutshell
- 91% of 608 Irish hotel and accommodation websites we tested had a serious or critical accessibility failure.
- Form fields without labels were far more common here than in our other studies. That’s the booking form.
- There’s no 2030 grace period for hotel websites or booking engines.
- A hotel with 10 or more staff that takes bookings and payment online is likely covered by the Act. Many B&Bs will be exempt as microenterprises.
What we found
In our study of Irish hotel and accommodation websites, 91% of 608 had at least one serious or critical failure. By type:
- B&Bs and guesthouses: 95% of 131
- other accommodation: 91% of 205
- hotels: 88% of 272
Our study checks homepages only, and automated checks find roughly a third of problems. Booking pages often sit on another page or another website, so we didn’t test most of them.
What fails most
This table shows the share of sites failing each check: all 608 sites, then hotels (272), B&Bs and guesthouses (131) and other accommodation (205).
| Problem | All | Hotels | B&Bs | Other |
|---|---|---|---|---|
| Hard-to-read text | 72% | 71% | 71% | 73% |
| Links with no name | 57% | 60% | 60% | 52% |
| Images with no description | 26% | 27% | 27% | 24% |
| Maps and widgets with no title | 19% | 15% | 25% | 19% |
| Form fields without labels | 16% | 17% | 22% | 11% |
| Zoom turned off | 9% | 6% | 8% | 15% |
| Buttons with no name | 6% | 9% | 3% | 4% |
Booking forms
16% of the 608 sites had a form field without a label. In our study of local services, like dentists and restaurants, it was 4%. The likely reason is the booking box on the homepage: check-in date, check-out date, number of guests.
A label tells people what goes in each box. Without one, a screen reader just says “edit text”. The guest has to guess whether it wants a date, a name or a number of rooms.
B&Bs and guesthouses had the highest rate, at 22% of 131. They also had the most embedded maps and widgets with no title, at 25%. For a small B&B, that’s guests who can’t book, or can’t find you. Most B&Bs are likely microenterprises, so the European Accessibility Act likely doesn’t require these fixes. But the guests are the same either way.
The 2030 myth
You may have heard that hotel booking engines have until 2030 to comply. That’s not what the Irish rules say.
There are some transition rules in Regulation 38 of the Irish rules (S.I. No. 636/2023):
- Service providers can keep using products they already used, until 28 June 2030.
- Service contracts agreed before 28 June 2025 can run until they end, for five years at most.
- Self-service terminals can stay in use for up to 20 years.
The first point is the one people get wrong. “Products” here means physical things. The CCPC, which checks e-commerce, says it “does not refer to intangible items, such as websites or mobile apps”. You can read that on the CCPC’s page about what the Act means for businesses.
So there’s no 2030 grace period for your website. A booking engine is part of how your website works, not a physical product, so the same goes for it.
The contract rule is different, and narrower. If you have questions about a specific contract, ask a solicitor.
Your booking engine
Most hotels use a booking engine from another company. It might sit in a box on your page, or open on the supplier’s website.
The Irish rules leave out third-party content that is “neither funded, developed by, or under the control of” the business (Regulation 3(4)(d)). A booking engine you pay for and put on your own website is likely funded by you. So it’s likely not left out. It depends on the facts, but don’t assume the booking engine is someone else’s problem.
You can’t fix the supplier’s code yourself. But you can ask them about it. Send them these questions:
- Do you have accessibility documentation for your booking engine?
- What have you tested it against? WCAG 2.1 AA, or EN 301 549?
- Can a guest book from start to finish using only a keyboard?
- Has it been tested with a screen reader?
- What known problems are there, and when will they be fixed?
Keep their answers. They’ll help with your accessibility statement, and they show you’ve asked.
Then run our free scan again on any page where the booking engine appears.
Who’s covered
The European Accessibility Act covers e-commerce: services where customers can buy online. A hotel taking bookings and payment on its website is likely to count.
Microenterprises providing services are exempt. A microenterprise has fewer than 10 people, and turnover or balance sheet of €2 million or less.
So, in general:
- A hotel with 10 or more staff that takes bookings and payment online is likely covered.
- Many B&Bs and guesthouses will be microenterprises, and so likely exempt from the service rules.
- A website that only shows rooms and a phone number likely isn’t an e-commerce service at all.
It depends on the facts of your business. Our guide to the microenterprise exemption helps you check, and our guide to the European Accessibility Act in Ireland explains who’s covered.
Your accessibility statement
Covered businesses have to publish information about how their service meets the rules. Most people call this an accessibility statement.
Only 9% of the 608 hotel and accommodation websites (55 sites) linked to one from their homepage.
We also counted which sites sell online. Our test was narrow: a shop platform, or products for sale on the homepage. Only 30 of the 608 passed it, so many hotels that take bookings won’t be among them. Of those 30, none linked to an accessibility statement.
If you’re covered, our guide to accessibility statements explains what to put in one, with a template. Ask your booking engine supplier for their part.
Describe your building too
Website accessibility isn’t the only access information guests need. Many want to know about steps, lifts, parking and accessible rooms before they book.
Fáilte Ireland’s guidance on the Access Welcome Guide puts it well: “Provide clear, factual details on your website and booking channels.” Put that information in text on your website, not in a PDF or photo.
What to fix first
- Your booking form. Every box needs a visible label, like “Check-in date”. Test it yourself: click on the label, and the cursor should jump into the box. Our guide to labelling the boxes on your forms shows how.
- Maps and booking widgets. Give each one a clear title, like “Map to the hotel” or “Check availability”. Our guide to fixing embedded content shows how.
- Room photos. Give each one a short description, such as “Double room with a view of the harbour”. Our guide to writing alt text has examples.
- Colour contrast. Pale text over a photo of your view is hard to read. Our guide to fixing colour contrast shows how to check.
- Links and buttons. Icon links and arrow buttons on photo sliders need a readable name. See our guides to fixing empty links and fixing buttons with no name.
- Zoom. Let guests pinch to zoom on their phones. Our guide to letting people zoom has the fix.
How Ireland compares
Irish hotels aren’t alone. QualiBooth, an accessibility testing company, published a 2026 report on hospitality websites across Europe. It used automated checks too, and found plenty of room to improve. Pages listing rooms and properties were among the weakest.
Run our free scan to see where you stand.
This isn’t legal advice. For exactly how the rules apply to your business, talk to a solicitor or the relevant regulator.