Crewlytics is built for people working on jobsites, in trucks, and in bright sunlight — conditions where accessible design helps everyone. This statement describes the accessibility features the app supports, where we stand on formal conformance, what is not done yet, and how to reach a human if something does not work for you.
1.What this covers
This statement applies to the Crewlytics mobile app for iOS and Android, and to this website at lantec.ai. Crewlytics is used by businesses and their staff; you typically access it through an account created by your employer.
2.Accessibility features
The app supports the following today:
- Screen readers — every interactive element carries an accessible name, role, and state for VoiceOver (iOS) and TalkBack (Android). This is enforced automatically: ten screen-reader lint rules run as errors across the whole codebase, so a control without proper accessibility information cannot be merged.
- Larger text — the app honours your device's text size setting (Dynamic Type on iOS, font scale on Android). Body text uses no fixed pixel sizes.
- Sufficient contrast — text meets a contrast ratio of at least 4.5:1 against its background (3:1 for large text), and meaningful icons, borders, and focus indicators meet at least 3:1. Every colour pair in the interface has been measured, not estimated.
- Never colour alone — status, selection, and validation are conveyed with an icon and text as well as colour, so the interface works with any form of colour blindness.
- Reduced motion — the app contains a single animation, and it is disabled automatically when you turn on Reduce Motion. There is no scaling, spinning, or peripheral motion anywhere in the interface.
- Spoken status changes — validation errors, async successes, and busy states are announced rather than only shown, so a screen-reader user is never left waiting on a silent screen.
- Predictable focus — dialogs trap focus deliberately and always release it, and focus order follows reading order.
- Voice entry is never the only path — every action that can be performed by voice can also be typed. Voice is offered as a convenience, not a requirement.
3.Conformance status
Crewlytics is designed and built to target WCAG 2.1 Level AA. We want to be precise about what that means today, because "accessible" is a claim that should come with evidence:
- Automated checks: complete and enforced. Ten of the eleven available React Native accessibility lint rules run at error severity across the entire codebase, plus automated contrast measurement and axe-core checks on the web surface. These block merges — they are not advisory.
- Manual screen-reader audit: in progress. Automated tooling proves that accessibility information is present and valid. It cannot prove that a whole workflow is comfortable to complete with VoiceOver or Voice Control. That verification is under way, screen by screen, and we will publish the results and a VPAT here when it is finished.
We would rather tell you an audit is in progress than claim a conformance level we have not finished verifying.
4.Known limitations
Things we know are not done yet:
- No dark interface. Crewlytics currently uses a light interface only. A dark theme is planned but not yet available, so the app cannot yet help users with light sensitivity in that way.
- Accessibility hints are not universal. Controls all have accessible names, roles, and states; supplementary hints — the longer "double tap to…" descriptions — are present in many places but not everywhere. Hints are optional under WCAG, and we are adding them as we revisit each screen.
- iPad layout. The current iOS release is built for iPhone. iPad support is planned for a future version.
5.Assistive technologies
Crewlytics is developed against VoiceOver on iOS and TalkBack on Android, on current and previous major OS versions. The website is developed against NVDA and VoiceOver in current browsers. If you use a different assistive technology and something does not work, please tell us — we would like to hear about it specifically.
6.Feedback and getting help
If any part of Crewlytics is difficult or impossible for you to use, we want to know. Email support.lantec@gmail.com with what you were trying to do, the device and assistive technology you were using, and what happened. We aim to respond within a few business days.
If you need an accommodation to complete a task in the app while we fix the underlying issue, say so in your message and we will work out a way to get it done.
7.Changes to this statement
We update this page as features ship and as audit results come in. The date at the top reflects the most recent revision.