Accessibility statement for Chargewise

18 October 2026 · ANKYR+YRD LIMITED, Cayman Islands

This statement applies to the Chargewise app at app.chargewiseapp.net. It does not cover the watch apps (Pacing Face and Chargewise Sync).

How accessible Chargewise is

We want as many people as possible to be able to use Chargewise, on a bad day as well as a good one. You should be able to: use it with a keyboard alone; set text to 200% without anything being cut off; use light or dark mode and three colour schemes, each with readable contrast; and each button, switch and field has a name for screen readers, with messages announced. Plain words are used throughout.

What is not yet accessible

We have not yet tested Chargewise with a screen reader (VoiceOver on iPhone, TalkBack on Android): the names, roles and announcements are in place, but how they read aloud is unchecked.
Safari on iPhone and iPad is untested; our checks were made in Chrome on Android-sized screens.
Some parts were not reached in our checks: setting up a new account, a weekly review with content, and turning on notifications.
The sign-in emails were not checked.
The watch apps are not covered by this statement or by our checks.

Feedback and contact

If you find something you cannot use, or need part of Chargewise in another form, email support@chargewiseapp.net, saying which screen and which phone and browser. We aim to reply within 5 working days.

Enforcement

Chargewise is offered by a private company, not a public sector body, so the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 do not apply to it. If you are in Great Britain and are not happy with how we respond, the Equality Advisory and Support Service (EASS) handles complaints about accessibility under the Equality Act 2010.

Technical information about Chargewise's accessibility

ANKYR+YRD LIMITED is committed to making Chargewise accessible, following the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA.

Compliance status

Chargewise is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard: the problems the audit found have been fixed (the sign-in screen's email and PIN boxes are named for screen readers, and show their name until you type), but the parts listed under "What is not yet accessible" have not yet been tested, so full compliance can't be claimed.

What we are doing to improve accessibility

The next audit will be run with a screen reader (TalkBack and VoiceOver) and in Safari, and this statement will be updated with what it finds.

Preparation of this statement

This statement was prepared on 17 October 2026, from an audit of build 1.6.25 by the developer with axe-core 4.10.3 and manual checks (keyboard, focus, text at 200%, contrast, target size) in Chromium at phone widths. Its 20 findings were fixed in build 1.6.28 and re-checked the same way on 18 October 2026.