Accessibility statement

Our commitment

The people who use Teammate App are on sites, wards, farms and factory floors, often in difficult conditions and on small screens. Accessibility is not a compliance exercise for us — a form that cannot be completed is a record that does not exist.

What an accessibility audit involves

This section is here because the page cannot be finished without one. An audit is not a scan; it is four things:

1. 1.Automated testing across representative pages and screens — catches roughly a third of issues (contrast, missing labels, heading order). Cheap, fast, insufficient on its own.
2. 2.Manual keyboard and screen reader testing of real task flows — completing a form, raising an incident, navigating the menu — on named combinations such as NVDA with Firefox, VoiceOver with Safari, and TalkBack on Android.
3. 3.Assessment against WCAG 2.2 Level AA, criterion by criterion, producing a list of passes, failures and not-applicables.
4. 4.A written report listing each failure, where it occurs, its severity, and what fixing it requires.

Typically half a day to two days of specialist time for a platform this size, or a staged approach: audit the five highest-traffic flows first. The output fills the two blank sections below and gives you a defensible statement rather than an aspirational one.

The standard we work to

We work towards WCAG 2.2 Level AA for both this website and the platform. We do not claim conformance, because conformance has not yet been independently tested. Confirm whether to also reference the NZ Government Web Accessibility Standard — relevant if you are selling to government agencies

What we have done

• Colour contrast checked against AA thresholds for text and interface elements.
• Keyboard operability for navigation, forms and dialogs.
• Visible focus indicators rather than suppressed browser defaults.
• Respect for the reduced-motion preference — animation is suppressed when the operating system asks for it.
• Semantic headings, labelled form fields, and alternative text on meaningful images.
• Touch targets sized for gloved hands on mobile.

Known limitations

This list should be uncomfortable to publish. That is how you know it is real. It must come from the audit, not from guesswork.

• Limitation 1 — from audit
• Limitation 2 — from audit
• Limitation 3 — from audit
• Third-party components not under our control — list them

Assistive technology we test with

List the screen reader, browser and platform combinations actually tested. If none have been formally tested, say exactly that — it is more credible than a vague claim.

How to report a barrier

1. 1.Email support@teammateapp.com describing what you were trying to do and what stopped you.
2. 2.Tell us the page or screen, and the device, browser and assistive technology if you know them.
3. 3.We will acknowledge and tell you what we can do and when.
4. 4.If we cannot fix something quickly, we will offer an alternative way to complete the task.

Alternatives available now

• Any form in the platform can be completed by a supervisor on behalf of a worker, with the worker recorded as the subject.
• Records can be exported for review outside the interface.
• Our support team can walk through any task by phone.

Review cycle

This statement will be reviewed annually and after any significant release, once the initial audit is complete.