Legal

Accessibility statement

What is in place, what is not yet verified, and how to tell us when something blocks you. Written from our actual audit record rather than an aspiration.

Last updated: 4 August 2026 · Applies to: taskbithr.com and the TaskBit application

1. Our commitment

TaskBit is used by frontline workers on their own phones, often quickly and in poor conditions. If somebody cannot see their shift, book leave or clock in, the software has failed at its job. We target WCAG 2.1 Level AA for the web application and this website.

2. Conformance status

Partially conformant with WCAG 2.1 Level AA. Partially conformant means some parts do not yet fully conform. We are stating this rather than claiming full conformance, because a full automated and assistive-technology audit has not yet been completed — see section 5.

SurfaceStatus
taskbithr.com (this website)Built to the same standards; semantic landmarks, skip link, keyboard-operable navigation, reduced-motion support, and colour tokens checked for contrast in light and dark themes
Web applicationPartially conformant — a manual source-level audit has been completed and its findings fixed; an automated audit is outstanding
Mobile staff appNot yet formally assessed

3. What is in place

  • Structure — a skip link to main content, landmark regions, a labelled primary navigation and a single h1 per page.
  • Keyboard — interactive controls are native buttons and links rather than click-only elements, with a visible focus ring throughout. Click-only handlers found during the audit were converted.
  • Names and labels — form fields carry associated labels, icon-only controls carry aria-label, and decorative icons and emoji are hidden from assistive technology.
  • Dialogs — modal dialogs declare role="dialog" and aria-modal, move focus on open, trap Tab, and close on Escape or an outside click.
  • Tables — header cells use scope, and empty action or photo headers carry screen-reader-only text.
  • Colour — text tokens were retuned to meet the 4.5:1 body-text ratio in both light and dark themes. One undefined token that rendered white-on-white was found and fixed.
  • Motionprefers-reduced-motion is respected; animation and scroll reveals are disabled when requested.
  • Themes — the interface follows your system light or dark preference rather than forcing one.

4. Known gaps

These are open, and we would rather list them than let you discover them:

  • Drag-and-drop rota building has no keyboard-accessible equivalent for moving a shift by dragging. Assignment is possible through the shift editor, but the drag interaction itself is pointer-only. This is our highest-priority accessibility fix.
  • Live regions — asynchronous results such as save, lock and publish are not consistently announced to screen readers.
  • Form-label sweep — labels were spot-checked across the main pages rather than swept across every screen.
  • Focus order in some menus and panels has not been verified end to end.
  • The mobile staff app has not had a formal accessibility assessment.
  • Screen-reader testing with VoiceOver, NVDA and TalkBack has not been carried out.

5. How we assessed this

The current position comes from a manual, source-level audit of the main application pages and shared components, with colour-contrast ratios computed by hand from the design tokens. Every issue it found was fixed.

An automated audit with axe-core has not been run, and no assistive-technology testing has been carried out. We are saying so explicitly because a partial audit reported as a full one is worse than no claim at all — particularly for contrast, which cannot be evaluated without real rendering. Completing an axe run across the main screens, and testing with screen readers, is planned work.

Assessment date: 18 July 2026. This statement was prepared on 4 August 2026.

6. Report a barrier

If something in TaskBit stops you working, tell us and we will treat it as a defect, not a request:

  • Email support@taskbithr.com with the page, what you were trying to do, and the assistive technology you use if any.
  • We aim to acknowledge within 2 working days and to give you a fix or a workaround, with a date, within 10 working days.
  • If you are an employee whose employer uses TaskBit, you can contact us directly — you do not have to go through them.

If you are not satisfied with our response, you can escalate to the Equality Advisory and Support Service in the UK, or your national equivalent.