Accessibility statement

Our accessibility commitment, known gaps, and how to tell us about a barrier.

Last updated 11 August 2026

We want Yebo to work for everyone, including people using a screen reader, a keyboard only, magnification, or a slow connection on an older phone.

What we aim for

We build to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. In practice that means:

  • Every form field has a visible label, and errors are announced, not just coloured
  • The whole site can be operated by keyboard, with a visible focus outline
  • Touch targets are large enough to hit comfortably
  • Text contrast meets AA, and we never rely on colour alone to signal something
  • Core pages, including the support form, work without JavaScript

Known gaps

  • Some older listing photos have no descriptive alternative text, because listers were not prompted for it when they uploaded
  • Map search depends on a visual map; if that is a barrier, use the filters on the properties page instead, which return the same results as text

Tell us about a barrier

If something blocks you, tell us what happened — the page, what you were trying to do, and the assistive technology you use. Accessibility reports go to the front of the queue, and we will tell you a workaround while we fix it.

Was this article helpful?

Still stuck?

Contact our support team and we will pick it up from here.

Contact support