Accessibility
Last updated:
NoCheck should be usable by everyone who keeps a vehicle running. This page says what the app does today, what it does not do yet, and how to reach us when something is in your way.
We would rather be specific than reassuring. Every claim below is something the app is built and tested to do; everything we have not verified is listed under What we do not claim yet, rather than left out. Where a rule has exceptions, the exceptions are printed beside it with their measurements — a rounded-up rule is the kind of thing that makes an accessibility page worth nothing.
What NoCheck supports today
Larger text
NoCheck follows your system text size, including the largest settings. Screens reflow rather than truncate: rows grow taller and labels wrap, and every component in the app is driven through an automated test at 200 % text size that fails on any overflow. Separately, each translation is length-budgeted for the controls that cannot grow — English is the shortest language we ship, so a button laid out against it would otherwise overflow in half the others.
Set it in your device’s own system settings — under Accessibility on iOS, under Display on Android. NoCheck picks it up and has no text-size setting of its own to keep in step with it.
Dark appearance
A complete dark theme, not a filter over the light one — every colour is drawn for its own background. It follows your system setting by default, and Settings → Preferences → Theme in the app overrides it in either direction.
Never colour alone
A vehicle’s maintenance status is never told by colour alone. Every status carries a written label — Overdue, Due soon, On track — and its own icon; the colour repeats that message, it never carries it. The same rule holds for the dashboard, the vehicle screen, and every list in between.
Reduced motion
When your system asks for reduced motion, NoCheck honours it. Loading placeholders stop shimmering entirely. A row’s swipe actions still move, but the slide is cut from 220 ms with a spring to 100 ms at a constant speed, and the “peek” animation that hints the tray exists is skipped altogether. We say this rather than “no animation” because it is not nothing — if a 100 ms slide is still a problem for you, we want to hear it.
Tap targets
Controls are 48 × 48 dp as a rule, even when the thing you see is smaller — a 7 dp status dot, a small icon button and a text link all have a finger-sized target behind them.
Four controls are deliberately smaller, and we would rather list them than round the rule up. They are compact by design, each one has a larger way to reach the same thing, and an automated test holds each at its measured size so none of them can quietly shrink further:
| Control | Painted size | The other way to the same action |
|---|---|---|
| Unit / mode toggle | 26 × 47.6 dp | Segments are wide and adjacent, so a miss lands on the neighbouring segment, never on nothing |
| “Log a service” header action | 22 × 113.7 dp | On the maintenance screen, the same action is a full 48 × 48 button in the header; on the vehicle screen, every maintenance row below it opens the same flow |
| “Update reading” pill | 38 dp tall | Tapping the card anywhere else opens the vehicle, where the same action is one row away |
| Backup upsell footer | 42 dp tall | The same screen offers it as a full row |
Flutter cannot register a tap outside the painted box, so these are real targets and not padded ones. If one of them is out of your reach, that is worth an email — the sizes are a design decision, not a law.
Screen readers
Interactive controls carry labels for VoiceOver and TalkBack, and no action in NoCheck can only be reached by swiping — every action a swipe reveals is also offered to a screen reader as a named row action, so VoiceOver and TalkBack never need the gesture.
🚨 Without a screen reader, one gesture has no equal. On most lists a long press opens the same menu the swipe reveals. On maintenance rows it does something else: it starts multi-select, so you can mark several services done at once. Deleting a maintenance item there is a swipe, or the row action a screen reader is given. If you can long-press but not swipe, and you are not using a screen reader, that one delete is currently out of reach. It is on our list.
Contrast where it matters most
Primary text measures 17.4:1 on the light theme and 15.1:1 on the dark one — both past the strictest WCAG level. Status labels — Overdue, Due soon, On track — sit at 10:1 or better on the light theme; on the dark theme the same labels measure 4.7:1 to 6.4:1, which clears WCAG AA but not the light theme’s margin, and we would rather print both numbers than the flattering one.
These are computed from the palette itself by a test that fails the build when any of them moves, so this page cannot quietly go stale — not sampled by eye.
What we do not claim yet
Sufficient contrast, as a whole
We deliberately do not declare Sufficient Contrast on the App Store, because it is not true everywhere yet. The secondary grey NoCheck uses for hints, captions and sub-lines measures 3.25:1 on the light theme — below WCAG AA’s 4.5:1 for small text. It is legible, it is never the only place a fact appears, and it is on our list. The dark theme does not have this problem.
A full screen-reader pass
Labels are in place, but NoCheck has not been through an end-to-end audit with VoiceOver or TalkBack by someone who uses one daily. Until it has, we will not say the app “supports VoiceOver” as though that were settled.
Braille displays, Switch Control and Voice Control
Untested. We have no reason to think they are broken, and no evidence that they work.
The standards we work to
- WCAG 2.2, level AA as the target. It is written for the web, so parts of it translate loosely to a native app; we treat it as the bar, not as a certificate we have been given.
- Apple’s Accessibility Nutrition Labels — we declare only the features the code and its tests support, which is why the list on our App Store page is shorter than it could be.
- Android’s accessibility guidance for tap targets, labels and text scaling.
This website
Every page of this site is held to a perfect Lighthouse accessibility score in continuous integration — a build that drops below it does not ship. That is an automated check and it does not replace a human one, but it does mean no release quietly regresses.
Tell us what is in your way
Write to support@nocheck.app. It helps if you can say:
- which screen you were on,
- which device and OS version,
- which assistive technology you were using, if any,
- and what you expected to happen instead.
We read every message. If something here is out of date or wrong, that is worth an email too — this page is only useful if it is honest.