Accessibility Statement

1. What this statement covers

This statement is published by Coverin Ltd and explains how accessible the Coverin Service is, what we have done so far, and what to do if you find something you cannot use.

It covers:

• the Coverin marketing and information website at coverin.app (the pages you can read without signing in, such as this one, our Privacy Policy and Terms of Service);
• the Coverin web app you use after signing in; and
• the Coverin mobile apps for iOS and Android.

This is a voluntary accessibility statement. Coverin Ltd is a private company and is not a public sector body, so the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 do not apply to us. We still publish this statement, and we still owe a duty under the Equality Act 2010 to make reasonable adjustments so that disabled people are not put at a substantial disadvantage. We take that duty seriously.

2. The standard we measure against

We measure Coverin against the Web Content Accessibility Guidelines (WCAG) version 2.1, Level AA. WCAG is the internationally recognised benchmark for digital accessibility. Level AA is the level UK organisations are generally expected to meet.

Accessibility is not a one-off task. We treat it as ongoing work, and we improve the product as we find and fix problems.

3. How accessible Coverin is

Coverin is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most of the Service meets the standard, but some content does not yet fully meet it. The known gaps are listed in Section 4.

What we have done

We have made the following specific improvements to the app:

• Text you can resize. Coverin now follows your device's text-size setting and stays usable when text is enlarged up to 200%. We removed very small text (anything below a readable floor) and made the weekly availability day picker reflow instead of clipping when text is at the largest setting.
• Stronger colour contrast. Small text that used our brand purple has been moved to a darker shade with a much higher contrast ratio, so it is easier to read for people with low vision. This covers form labels, button labels, chips, badges, and several specific labels across the dashboard, schools, earnings, availability, and onboarding screens.
• Screen-reader labels. Buttons, cards, list rows, attachment controls, chips, and other things you tap or click now announce a clear name and role to screen readers such as VoiceOver and TalkBack, instead of being silent or unlabelled. A chart on the dashboard now also has a short text description.
• Automated checks. We added an automated test that fails the build if a core interactive component loses its accessible label, so these improvements do not silently regress.

These improvements were verified by internal review and automated testing (see Section 7). They are real, specific changes; they do not mean every screen has been independently certified.

4. Known limitations

We know about the following areas that may not yet fully meet WCAG 2.1 AA. We are working on them. If one of these stops you doing something, contact us (see Section 5) and we will help you another way.

• The job map. The teacher map view uses an embedded Google Maps component whose markers and controls are not fully reachable by a screen reader. Every job shown on the map is also available in the job list and job feed, which is keyboard and screen-reader accessible, so no job is hidden behind the map. On the web app the map automatically falls back to the list view.
• Charts. Dashboard charts are visual by nature. The main dashboard chart has a short text alternative, but full data-table equivalents for every chart are not yet provided. The same numbers are available elsewhere in the Service as plain text.
• The marketing website. The public pages (this site) have had contrast and structure attention but have not yet had a full independent accessibility audit.
• Exported files. Data you export (the payroll CSV and the "download my data" file) is provided as plain, machine-readable data rather than a formatted accessible document. This is by design so the data is easy to open in other tools.
• Older screens. Some less-used screens may not yet have had the full screen-reader and contrast pass that the core flows have had.

5. Reporting an accessibility problem

If you find something on Coverin that you cannot use, or that is hard to use because of an accessibility barrier, please tell us. Your feedback genuinely helps us prioritise fixes.

• Email: support@coverin.app
• Post: Coverin Ltd, 66 Westbourne Road, West Bromwich, B70 8JX, United Kingdom

It helps us if you can include:

• what you were trying to do;
• which page or screen you were on (a link or screen name is ideal);
• the device, browser or app version, and any assistive technology you use (for example a screen reader); and
• what went wrong.

We aim to acknowledge your message within 5 working days and to give you a substantive response, or a clear plan and timescale for a fix, as soon as we can and normally within 20 working days.

6. Reasonable adjustments

Under the Equality Act 2010 we will make reasonable adjustments so that a disability does not put you at a substantial disadvantage when using Coverin. If a particular part of the Service is not accessible to you right now, contact support@coverin.app and we will work with you to achieve the same outcome a different way (for example, by carrying out an action with you or providing information in another format) while we fix the underlying issue.

7. How we test Coverin

The accessibility improvements described in this statement were checked by Coverin's own team, not yet by an external auditor. Our testing so far includes:

• reviewing colour-contrast ratios for small text against the WCAG thresholds and moving failing text to a higher-contrast colour;
• checking that the app remains usable with the operating-system text size increased up to 200%;
• adding accessible names and roles to interactive components so screen readers can announce them; and
• an automated test in our build that asserts core interactive components keep an accessible label, so the improvements do not regress.

We have not yet commissioned a full independent WCAG audit of the whole Service. This statement reflects an internal self-assessment. We will update it as our testing and the product develop.

8. If you are not happy with our response

If you contact us about an accessibility problem and you are not satisfied with how we respond, you can get free, independent advice and support about your rights under the Equality Act 2010 from the Equality Advisory and Support Service (EASS):

• Website: equalityadvisoryservice.com
• Telephone: 0808 800 0082

Because Coverin Ltd is not a public sector body, the enforcement route for public sector website accessibility (the Equality and Human Rights Commission under the 2018 accessibility regulations) does not apply to us. The Equality Act 2010 still does, and EASS can advise you on it.

9. Preparation of this statement

This statement was prepared on 17 May 2026 and last reviewed on 17 May 2026. It is based on an internal self-assessment of the Coverin Service carried out by Coverin Ltd.

We will review this statement when we make material accessibility changes, when a full audit is completed, and at least once a year.