1. What is WCAG?
WCAG stands for
Web Content Accessibility Guidelines. It’s a set of internationally recognised technical standards developed by the World Wide Web Consortium (W3C) to make web content more accessible to people with disabilities.
WCAG is organised into three levels:
| Level |
Name |
What it means |
| A |
Minimum |
The baseline. Covers the most critical barriers. Required for any accessible website. |
| AA |
Standard ★ |
The widely adopted target. Covers most accessibility needs. Required by EU and Swiss law. This is our target. |
| AAA |
Enhanced |
The highest level. Goes beyond what most websites can fully achieve in every context. |
2. Our commitment
We are committed to making hotel-spider.com accessible to as many people as possible, including those who use assistive technology such as screen readers, voice navigation, or keyboard-only browsing.
Accessibility isn’t a one-time task for us — it’s part of how we build and maintain our website. We review our conformance regularly and address issues as we find them.
hotel-spider.com aims to conform to WCAG 2.1 Level AA. Where we fall short, we want to know about it — see Section 7 for how to tell us.
3. The four principles of accessibility
WCAG is built on four core principles — often remembered as POUR. Every accessibility criterion traces back to one of these:
| P |
Perceivable — Information must be presented in ways everyone can sense.– All images have descriptive alt text– Video content includes captions– Colour is never the only way to convey information– Text can be resized up to 200% without breaking the layout |
| O |
Operable — Everyone must be able to navigate and use the interface.– All functions work with a keyboard (no mouse required)– Navigation is consistent and logical– Users get enough time to read and interact with content– No content flashes more than three times per second |
| U |
Understandable — Content and controls must be clear and predictable.– Language is plain and jargon is explained– Forms have clear labels and helpful error messages– Pages behave consistently across the site– The page language is set correctly for screen readers |
| R |
Robust — Content must work across current and future technologies.– HTML is valid and follows web standards– Content works with common assistive technologies– No functionality depends on a single browser or device |
4. What we’ve done to meet WCAG 2.1 AA
Here is an overview of the accessibility measures we’ve built into hotel-spider.com:
| Area |
Status |
Notes |
| Keyboard navigation |
✓ Implemented |
All interactive elements are reachable and usable by keyboard alone |
| Skip navigation link |
✓ Implemented |
A skip link allows keyboard users to jump directly to main content |
| Alt text for images |
✓ Implemented |
All informative images have descriptive alt attributes |
| Colour contrast |
✓ Implemented |
Text meets the 4.5:1 contrast ratio for normal text (3:1 for large text) |
| Resizable text |
✓ Implemented |
Text scales to 200% without loss of content or functionality |
| Form labels and errors |
✓ Implemented |
All form fields have visible labels; errors are clearly described |
| Focus indicators |
✓ Implemented |
Keyboard focus is clearly visible at all times |
| Page language |
✓ Implemented |
HTML lang attribute is correctly set for screen reader compatibility |
| Consistent navigation |
✓ Implemented |
Navigation menus appear in a consistent location on every page |
| Video captions |
⚠️ In progress |
Captions planned for all video content; rolling out with new content |
| PDF accessibility |
⚠️ In progress |
Downloadable PDFs being reviewed for screen reader compatibility |
| Third-party content |
⚠️ Partial |
Some embedded third-party widgets may not fully meet WCAG 2.1 AA |
| AAA enhancements |
○ Aspirational |
We aim for some AAA criteria where practical, e.g. extended audio descriptions |
5. Known limitations
We aim for full WCAG 2.1 AA conformance, but we’re not quite there on everything yet. Here’s what we know about and are actively working on:
We’d rather be honest about gaps than claim perfect compliance. If you find something we haven’t listed here, please tell us — see Section 7.
Video captions
Captions are being added to all video content on the site. New videos are published with captions from launch. Older content is being updated progressively.
Downloadable PDFs
Some PDF documents available on the site were created before our accessibility review and may not be fully accessible to screen readers. We are reviewing and updating these. If you need an accessible version of a specific document, contact us and we’ll provide an alternative format.
Third-party widgets
We use some third-party tools on our website — for example, chat widgets, form builders, or embedded demos. We choose accessible providers where possible, but we cannot guarantee full WCAG 2.1 AA compliance for all third-party content. We’re actively monitoring these and raising issues with providers where needed.
Complex data tables
Some pages displaying product comparison data use complex table structures. We are improving these to ensure they work clearly with screen readers and are properly labelled.
6. Browser and assistive technology compatibility
hotel-spider.com is designed to be compatible with the following browsers and assistive technologies:
| Browsers (current and previous major version) |
Assistive technologies |
| – Google Chrome– Mozilla Firefox– Microsoft Edge– Apple Safari (macOS and iOS)– Samsung Internet (Android) |
– NVDA (Windows screen reader)– JAWS (Windows screen reader)– VoiceOver (macOS and iOS)– TalkBack (Android)– Keyboard-only navigation |
We don’t support Internet Explorer. If you’re using an older or less common browser and experience issues, switching to a modern browser should resolve most problems.
7. Feedback and getting help
If you encounter any accessibility barrier on hotel-spider.com — or if something doesn’t work with your assistive technology — please tell us. We want to know.
| Accessibility feedback |
accessibility@hotel-spider.com |
| General enquiries |
info@hotel-spider.com |
| Response time |
We aim to acknowledge all accessibility reports within 5 business days and provide a resolution or workaround within 30 days. |
What to include in your message
To help us fix the problem as quickly as possible, it’s useful to tell us:
- The page URL where you experienced the issue
- What you were trying to do
- What happened (or didn’t happen)
- The browser and assistive technology you’re using
Alternative formats
If you need any content from our website in an alternative format — for example, large print, audio description, or an accessible PDF — contact us at accessibility@hotel-spider.com and we’ll do our best to help.
8. Enforcement and regulatory context
Web accessibility is required or strongly recommended under several legal frameworks that apply to Hotel-Spider:
| Jurisdiction |
Applicable framework |
Our position |
| European Union |
European Accessibility Act (EAA) — Directive 2019/882, applicable to digital services from June 2025 |
We align with EAA requirements for our B2B digital services |
| Switzerland |
Behindertengleichstellungsgesetz (BehiG / LHand) and federal procurement guidelines referencing WCAG 2.1 |
We target WCAG 2.1 AA as our standard, consistent with Swiss accessibility guidance |
| India |
Rights of Persons with Disabilities Act 2016 (RPWD) — encourages accessible digital services |
We apply the same WCAG 2.1 AA standard globally |
If you feel we haven’t adequately addressed an accessibility complaint, you can escalate to the relevant national authority:
- Switzerland: Federal Office for Equal Opportunities of People with Disabilities (EBGB / BFEH) — ebgb.admin.ch
- EU member states: Your national authority responsible for enforcing the European Accessibility Act
- India: State Commissioner for Persons with Disabilities
9. How we review and maintain this
Accessibility is an ongoing commitment, not a box we tick once. Here’s how we keep it on track:
Regular testing
We test the website using a combination of automated tools (such as Axe, Lighthouse, and WAVE) and manual testing with screen readers and keyboard-only navigation. We run a full review at least once a year and whenever we make significant changes to the website.
Development standards
Our development team follows accessibility guidelines as part of the standard build process. New pages and features are reviewed for accessibility before launch.
Statement updates
This accessibility statement is reviewed and updated at least annually, or sooner if we make significant changes to the website or identify new issues. The “last updated” date at the top of this page reflects the most recent review.
Next full accessibility review: scheduled for Q1 2027 (or earlier if significant changes are made to the website).
