Accessibility statement

Subbo should be easy for everyone on site, on any phone. Here is where we stand, plainly.

The standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG 2.2) at level AA, for the Subbo app and this website.

Status: partly meets. We checked every level A and AA rule on 31 October 2026. Our own checks pass, but a disabled person using a screen reader has not tested Subbo yet, so we don't claim full conformance.

What you can do

How we check

Automatic accessibility tests run every time we change the code. Before each release we also walk every main screen in a real browser: keyboard only, zoomed to 400%, extra text spacing and 200% text.

What isn't right yet

  • Not yet tested by a screen reader user on iPhone (VoiceOver) or Android (TalkBack).
  • The worker app's 13 translated languages are our drafts. Native speakers are still checking them, so some wording may be unclear.
  • When you approve a payment, that step happens on your own bank's website or app. Its accessibility is up to your bank.
  • To stop money going to a wrong account, we ask you to type a worker's account number twice, and you can't paste the second one.

Tell us about a problem

If something in Subbo is hard to use, or you need information in another format, email us. Say which screen and what happened. We reply within 5 working days.

If you're not happy with our reply, you can contact the Equality Advisory and Support Service (EASS).

About this statement

Prepared on 31 October 2026 by checking every WCAG 2.2 level A and AA success criterion ourselves. We review it at least once a year and after big changes.

Free trialCIS calculator