Accessibility statement.

Travel and meeting people should work for everyone. We design and build Greety to be usable by people with vision, motor, cognitive, and hearing differences, and we test against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA — the standard referenced by the European Accessibility Act, the US ADA, and Singapore’s digital accessibility code.

• Keyboard navigation — every interactive element is reachable and operable via Tab + Enter + Arrow keys.
• Visible focus rings on all focusable elements, with 3:1 contrast against the background.
• Screen reader support tested against NVDA, JAWS, VoiceOver (macOS + iOS), and TalkBack.
• Reduced-motion support via the prefers-reduced-motion media query — animations are disabled or simplified for users who request it.
• 4.5:1 minimum contrast on body text, 3:1 on large text and UI components.
• Resizable text up to 200% without breaking layout.
• Alt text on every photo in the host browse grid, plus auto-generated descriptions for user-uploaded media.
• Captions on every video — host intro videos, tutorial walkthroughs, marketing footage. Auto-captions reviewed by a human.
• Form labels and error messages linked programmatically, never colour-only.

The following areas don’t yet hit AA. We’re working on them.

• The map (MapLibre GL canvas)on city pages isn’t fully keyboard-navigable. We provide a parallel text-list view via the “List view” toggle on every map page.
• Live chatauto-scroll behaviour can disorient screen-reader users. We’re shipping an opt-out toggle in June 2026.
• User-uploaded video alt textisn’t mandatory yet — host-uploaded videos may lack captions until the host adds them. We’ll auto-generate fallbacks in Q3 2026.
• Older host profile photosuploaded before March 2026 may have missing or generic alt text. We’re backfilling these.

Greety conforms to WCAG 2.2 Level AA with the known limitations listed above. We use Deque axe in CI on every PR and run a quarterly audit by an external accessibility consultancy.

We are not currently certifying AAA conformance. AAA-level requirements (sign language interpretation, extended audio descriptions, 7:1 contrast) are reviewed for individual surfaces but not platform-wide.

Tested and working on:

• NVDA + Firefox / Chrome (Windows)
• JAWS + Chrome (Windows)
• VoiceOver + Safari (macOS, iOS)
• TalkBack + Chrome (Android)
• Dragon NaturallySpeaking voice control (Windows)
• Switch control (iOS, macOS)

Found something inaccessible? We want to fix it fast. Email accessibility@greety.online with:

• The page URL.
• What you were trying to do and what got in the way.
• Your assistive technology + browser combination.

We aim for a first response within 5 business days and a fix or workaround within 30 days for blockers. Non-blocking issues land in the next quarterly accessibility sprint.

• WCAG 2.2 — Web Content Accessibility Guidelines (W3C)
• EN 301 549 — European harmonised accessibility standard
• Section 508 — US federal government accessibility standard
• Singapore IMDA Digital Accessibility Code

Related: community standards · other contact options.