Accessibility

Accessibility Statement

JungleBnB wants every visitor to be able to read the directory, use the stay finder and reach a listing, whatever device or assistive technology they use. This page says what we build to, what is in place, where we know we fall short, and how to tell us when something does not work.

The standard

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA across junglebnb.com. The site is a static, server-rendered directory with no accounts, forms or payments, which keeps most of the harder criteria out of scope, and we treat the remaining ones as a build requirement rather than an afterthought.

What is in place

01Semantic HTML with one H1 per page, ordered headings, landmarks for header, navigation, main content and footer, and a logical reading order.

02Descriptive alt text on every meaningful photograph, and empty alt on decorative images.

03Full keyboard operation: every link, button and filter chip is reachable with Tab and activated with Enter or Space, with a visible focus state.

04Text that scales with browser zoom to 200 percent without loss of content, and a base font size of 19 pixels.

05Colour contrast of at least 4.5:1 for body text on the ivory and forest-green backgrounds, and colour is never the only carrier of meaning; the When To Go grid also labels each cell in text.

06Fonts self-hosted on this domain, no third-party trackers before consent, and no content that flashes.

Known gaps

The stay pages link out to Airbnb and to hosts' own websites. Those pages are run by other companies and we cannot vouch for their accessibility. Some landscape photographs on destination pages are described only at the level of the place shown rather than every detail in the frame. Scroll-triggered fade-in animations run on most pages; they respect the operating-system "reduce motion" setting, and if any remain a problem we would like to know.

Tell us

If any part of this site is hard to use, email hello@junglebnb.com with the page address and what happened. We reply within five working days and fix what we can in the next build. This statement was last reviewed on 4 September 2026.