Accessibility

How we build Gollo to work for everyone, and how to tell us when it doesn't.

Everyone should be able to find and book a tour.

Accessibility isn't an afterthought — it's part of how we design and build. This page describes what Gollo does today to support travellers with disabilities, the standards we're working toward, and how to tell us when we've fallen short.

What we build for today

Across the Gollo website and mobile app, we build with:

Semantic HTML — headings, buttons, links, lists, and landmarks are the real HTML elements, not styled divs. Screen readers can parse the page structure directly.
Keyboard navigation — every interactive element (buttons, links, form fields, modals) can be reached and operated with a keyboard alone. Modals close with the Escape key.
Focus indicators — visible focus rings on every interactive element so keyboard users always know where they are.
Alt text on images — tour photos, host avatars, and interface icons carry descriptions or are marked decorative when they don't add information.
Labelled controls — form fields, icon-only buttons, and dialog headings have text labels for screen readers.
Colour contrast — text meets or exceeds WCAG 2.1 AA contrast targets against its background.
Responsive layouts — pages reflow to zoom levels up to 200% without content loss or horizontal scrolling.

Standards we're working toward

Our target is Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. This is the standard referenced by the Australian Disability Discrimination Act 1992 and the European Accessibility Act.

We haven't yet completed a formal third-party audit against WCAG 2.1 AA. When we do, we'll publish the result here — including any non-conformances and our timeline to close them.

Known gaps

Being honest matters more than looking polished. Today, we know Gollo:

Does not yet honour the "reduce motion" system preference. Video-heavy surfaces (reels feed, hero animations) play by default. This is on the roadmap.
Has not been formally tested with screen readers (VoiceOver, TalkBack, NVDA, JAWS) by users of those tools. Our internal testing catches structural issues, but nothing replaces feedback from people who use assistive tech daily.
Video content in reels does not currently carry captions. Adding creator-supplied captions is planned.
Some third-party components (Stripe checkout, Cloudflare Turnstile, Mapbox map) have their own accessibility postures that we don't fully control.

If you hit any of these — or something we haven't listed — please tell us.

Tell us about a barrier

If any part of Gollo blocks you from booking, hosting, or getting what you need — a form field you can't reach, an image without alt text, a modal that traps focus, anything — please report it.

In-app: Help & Support → Bug report, and mention "accessibility"
Email: support@gollo.co with "Accessibility" in the subject
We reply within 24 hours

Include the page URL, the device and browser you're using, and any assistive tech (screen reader, magnifier, voice control). The more detail, the faster we can reproduce and fix.

Alternative ways to book

If you can't complete a booking on the website or app for accessibility reasons, contact support and we can complete the booking for you. This is not a scalable substitute for accessibility — it's a bridge while we fix the underlying issue.

Feedback shapes the roadmap

Every accessibility report is logged, triaged, and used to prioritise the roadmap. Reports from users of assistive tech carry the most weight because they surface issues internal testing misses.

Last updated: 3 August 2026

What we build for today

Across the Gollo website and mobile app, we build with:

Semantic HTML — headings, buttons, links, lists, and landmarks are the real HTML elements, not styled divs. Screen readers can parse the page structure directly.

Keyboard navigation — every interactive element (buttons, links, form fields, modals) can be reached and operated with a keyboard alone. Modals close with the Escape key.

Focus indicators — visible focus rings on every interactive element so keyboard users always know where they are.

Alt text on images — tour photos, host avatars, and interface icons carry descriptions or are marked decorative when they don't add information.

Labelled controls — form fields, icon-only buttons, and dialog headings have text labels for screen readers.

Colour contrast — text meets or exceeds WCAG 2.1 AA contrast targets against its background.

Responsive layouts — pages reflow to zoom levels up to 200% without content loss or horizontal scrolling.

Standards we're working toward

We haven't yet completed a formal third-party audit against WCAG 2.1 AA. When we do, we'll publish the result here — including any non-conformances and our timeline to close them.

Known gaps

Being honest matters more than looking polished. Today, we know Gollo:

Does not yet honour the "reduce motion" system preference. Video-heavy surfaces (reels feed, hero animations) play by default. This is on the roadmap.

Has not been formally tested with screen readers (VoiceOver, TalkBack, NVDA, JAWS) by users of those tools. Our internal testing catches structural issues, but nothing replaces feedback from people who use assistive tech daily.

Video content in reels does not currently carry captions. Adding creator-supplied captions is planned.

Some third-party components (Stripe checkout, Cloudflare Turnstile, Mapbox map) have their own accessibility postures that we don't fully control.

If you hit any of these — or something we haven't listed — please tell us.

Tell us about a barrier

In-app: Help & Support → Bug report, and mention "accessibility"

Email: support@gollo.co with "Accessibility" in the subject

We reply within 24 hours

Include the page URL, the device and browser you're using, and any assistive tech (screen reader, magnifier, voice control). The more detail, the faster we can reproduce and fix.