Our commitment
We want GoGeter to be usable by as many people as possible, regardless of ability, device or assistive technology. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the platform, and we treat accessibility as a continuous practice — not a one-off audit.
What we have built in
The following are baked into every release:
- Keyboard support — every interactive element is reachable and operable with a keyboard alone, with a visible focus ring;
- Screen-reader friendly — semantic HTML, ARIA labels where native semantics fall short, descriptive alt text on meaningful images;
- Colour and contrast — text meets AA contrast against its background; we never rely on colour alone to convey meaning;
- Resizable text — the layout reflows down to 320 px width and up to 200% zoom without losing functionality;
- Reduced motion — animations are dialled back automatically when your OS reports
prefers-reduced-motion; - Captions and transcripts — pre-recorded videos ship with captions and a transcript on the same page.
Known issues
We are transparent about where we are still catching up. Current known gaps (we are actively working on them):
- The embedded Google Map on listing pages is not fully operable with a screen reader — a static address and "Get directions" link is offered as a fallback.
- Some legacy review threads use heading levels that do not strictly cascade; we are refactoring as we migrate to the new components.
- A few older PDF brochures uploaded by businesses are not tagged for screen readers; we are scanning and re-tagging on a rolling basis.
If something blocks you that is not on this list, please tell us — see the "Report a barrier" section below.
Standards and testing
We test in three layers:
- Automated — axe-core runs in CI on every pull request and blocks regressions on the WCAG 2.2 AA rules it can detect.
- Manual — every new feature is walked through with keyboard only and with a screen reader (VoiceOver or NVDA) before release.
- Third-party — we commission an independent accessibility audit annually and publish the resulting report on this page.
Tools we recommend
If you find that GoGeter is hard to use with your current setup, these may help while we fix the underlying issue:
- Browser built-in zoom (
Ctrl/⌘++) to enlarge everything proportionally; - NVDA (Windows) or VoiceOver (macOS / iOS, built in) for screen-reader support;
- System-level high contrast or Dark Mode — our colours adapt to your OS preference where possible.
Report a barrier
Email accessibility@gogeter.com with:
- the URL or page name where it happened;
- what you were trying to do;
- what blocked you (the more detail, the faster we can fix it);
- your browser, OS and any assistive technology you use.
We will acknowledge within five business days. Priority-blocker fixes ship within the same week; longer pieces of work get a public ETA so you can track progress.
Beyond this page
This statement is a snapshot. Accessibility is a moving target — new content, new components and new browsers can introduce new issues. We re-audit at every major release and publish updates to the "Known issues" list above. If you would like to be notified when this page changes, drop us a note and we will add you to the list.