CarStack is built by a small team, and accessibility is part of how we build rather than a pass we make at the end. This statement says what we are aiming for, what is in place, where we currently fall short, and how to reach a person who can fix something.
1. Where we are
CarStack is pre-launch, built by a two person team. This statement is written before an independent audit rather than after one, so it describes commitments and an approach, not a certified result.
Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C on 5 October 2023 and updated 12 December 2024, applied to native mobile interfaces through the iOS and Android accessibility APIs.
We are not claiming conformance to it today. We have not been independently audited, and we will not describe ourselves as conformant until we have been. When that audit happens, this page changes to say what it found.
2. How we are building
Accessibility is handled in the design system rather than screen by screen, which is the only approach that works at our size.
- Type and spacing are defined as scalable tokens, so text respects the size the reader has chosen at the system level instead of being pinned to fixed values.
- Color pairings are decided once, at the token level, and checked for contrast there, so a combination that passes is correct everywhere it is used rather than needing a per screen audit.
- Color is not the only carrier of meaning. Status, verification, and validation states pair color with a label, an icon, or both, so they survive a color filter or a grayscale display.
- No action depends on a gesture. Anything you can do by swiping a card in Stacks can also be done by tapping a labeled control.
- Deal Mode does not require the map or location services. Arrival can be confirmed by tapping a button instead of relying on geofence detection, so the flow works without reading a map, seeing a pin, or granting location access.
- Motion respects the system Reduce Motion setting.
We are building toward full VoiceOver and TalkBack support, correct focus order, labeled form fields with announced errors, and touch targets at or above the platform minimum. Where a screen is not there yet, we would rather you tell us than discover it in a report we wrote about ourselves.
3. What we have not done yet
- No independent third party accessibility audit
- No formal screen by screen conformance testing against WCAG 2.2 AA
- No published VPAT or conformance report
- No testing with users who rely on assistive technology, which is the gap we most want to close before launch
If you use assistive technology and would be willing to try CarStack and tell us where it fails, email hello@mycarstack.com. We will pay for your time.
4. Known limitations
We would rather name these than let you find them.
| Area | Limitation | Status |
|---|---|---|
| Seller photos | Generated descriptions come from listing data and may not describe damage, wear, or a specific angle accurately | Sellers can write their own; improving the generated ones |
| Story video | Stories are seller recorded and most have no captions | Caption prompts at upload are planned |
| Nitro | Replies stream in, and screen readers may announce partial text before a reply finishes | Planned: announce only completed replies |
| Deal Mode map | The map conveys position visually. Arrival can be confirmed without it, but the text equivalent is less detailed | Planned: a fuller non visual equivalent |
| Signature capture | Signing the bill of sale requires drawing on screen, which is difficult or impossible with some assistive technologies | Until a non drawing path ships, email hello@mycarstack.com and we will complete the document with you |
| Window sticker scanning | Depends on framing a document in the camera, which is hard without usable vision | Manual entry is available for every field the scanner fills |
| Third party content | Identity verification runs inside Didit's own SDK, which we do not control and have not evaluated | Verification is optional and never required to browse, list, or message |
5. Compatibility
CarStack is built with React Native, so it uses the platform's own accessibility layer rather than a custom one. That means VoiceOver, Voice Control, TalkBack, Switch Access, external keyboards, bold text, increased contrast, reduced transparency, and color filters all act on the app through the same APIs they use everywhere else on your device.
We have not yet completed a formal test pass against each of those. If one of them behaves badly, that is a bug we want reported, not expected behavior.
We support the current and previous major versions of iOS and Android.
6. Tell us what is broken
If something on CarStack is hard or impossible for you to use, tell us. This is the fastest way anything gets fixed.
Email: hello@mycarstack.com
In app: More, Send Feedback
Tell us what you were trying to do, the screen you were on, the assistive technology and version, and your device and OS version if you can. A report with none of that is still worth sending.
We read every report and reply to a real person, not a queue. We aim to acknowledge within a few business days and to tell you either the fix or an honest timeline. If something cannot be fixed quickly we will find you another way to finish what you were doing.
7. Legal context
CarStack is a service offered to the public in the United States, and we treat Title III of the Americans with Disabilities Act as applying to it. WCAG 2.2 Level AA is the standard we hold ourselves to in the absence of a specific technical regulation for private mobile apps.
This statement describes our commitments and our current state. It is not a warranty that every part of the Service conforms to any standard at any given moment.
8. Keeping this current
We review this statement whenever we ship a significant change and at least every six months, and we update it after our first independent audit. The known limitations table is maintained as part of that review, not left to age.
First published: September 8, 2026
Last reviewed: September 8, 2026