Get the app

Accessibility

What we aim for, what we have tested and with what, what we know is still open, and how to tell us when something gets in your way.

Where we stand

TaperØff aims to meet WCAG 2.2 Level AA on this website and in the iPhone and Android apps. This statement covers TaperØff, made by Slipstitch Limited. We have not yet had an independent accessibility audit, and we have not yet finished testing the apps with a screen reader on a real phone. Both are listed below.

The website

Every page is checked automatically with axe, an open accessibility testing engine, against the WCAG 2.0 A and AA, 2.1 AA and 2.2 AA rules. Each page is checked in light and dark mode, with reduced motion on. A violation fails our test run. These checks run when a page loads. They do not test every state a page reaches after you use it, such as the calculator's results after you change a number.

The iPhone app

Apple's accessibility audit runs over the main screens: the plan and Now, cravings, your account, the paywall, the programme, and your journey. Each screen is checked at the default text size and again at the largest accessibility size. The audit looks for missing labels, text that is cut off, small tap targets and poor contrast. A finding is accepted only when it is a known limit of the system or a deliberate design choice, and the test says why.

Text grows with the Dynamic Type setting on the screens we audit. Animations that move things on screen stay still when Reduce Motion is on. We have not yet checked every animation in the app against that setting.

The Android app

Our Android checks cover 13 main screens, the paywall among them. They read each screen's accessibility tree and check that every control has a name TalkBack can read, that every control is at least 48 by 48 dp, that text is not cut off at a large font size, that no two controls sound the same, and that switches, checkboxes and tabs say what they are. The checks run as unit tests on our build machine. They do not run Google's Accessibility Test Framework on a phone, so they cannot see what a phone draws in the way it does.

The watches

The Apple Watch and Wear OS apps are not covered by the audits above. The Wear OS app has one automated check, on its page that asks for Plus.

What is still open

  • Screen reader passes on real phones. We have not yet worked through every screen with VoiceOver on iPhone and TalkBack on Android. Automated checks miss things a screen reader user hears, so this is the next thing we test.
  • The progress ring's number. On iPhone the number in the ring stops growing above a set text size, on purpose, so the ring keeps its shape. VoiceOver reads the full number.
  • The milestone picture. When you share a milestone, the card is a picture scaled to fit the sheet, so the text in it does not grow with your text size. VoiceOver reads its words.
  • The hour bars. The bars on the day's chart are narrower than the 44-point target Apple suggests. "See each log today" is the full-size way to reach the same logs.
  • The SOS button. On iPhone its label shrinks at the largest text sizes. A long press shows it at a larger size.
  • Contrast under blur. Text that scrolls under a blurred bar or the edge of a screen is not measured against what is behind it. Each pair of text and background colours is checked on its own.
  • Android motion. We have not yet checked the Android animations against the system setting that removes them.
  • Watches. As above, the watch apps are not in these audits.

Ask us for help

If something in TaperØff is hard to use with a screen reader, a large text size, a keyboard, switch control or voice control, email quit@taperoff.io. Tell us your phone and its system version, what you were trying to do, and what got in the way. We'll answer by email, fix what we can, and say plainly what we can't.

You can also ask for the information in this app in another form, and we'll say what we can provide. Nothing you send us about accessibility needs your account or your log.

Review

This statement was last reviewed on 1 November 2026. We'll update it when we run the next audit, when a finding above is fixed, or when a new screen is added to the apps.