Accessibility

The standard we aim for

We aim to meet WCAG 2.2 Level AA on this website and to follow the same ideas in the iOS and Android apps: perceivable, operable, understandable, robust. Aiming is not a certificate. If something fails, we want to know.

This website

Pages use semantic headings, a skip link to the main content, visible keyboard focus, and text that is not centered as a wall. Contrast on body text and on the teal action color is checked against AA. Motion is one thing — and it is off when the system asks for reduced motion.

Language is declared per page (English, Spanish, or Brazilian Portuguese), with a language switcher in the footer. Images of the app have descriptions. Sample data is labeled as fictional so a screen reader does not present Maya as a real child.

The app

The app follows the platform: Dynamic Type, VoiceOver, TalkBack, and the system color-scheme. Status is never color alone — "disputed" and "days left to respond" are words, not just a stripe. There is no hover-only action.

Biometric lock is optional and stays on the device. Turning it off is a labeled control, not a hidden gesture.

We know some flows are still denser than they should be — the export confirmation, in particular. That is on us to thin out, not on you to guess.

What this is not

We do not claim conformance with Section 508, EN 301 549, or a formal audit. When we have that, this page will say so.

Tell us

If a control has no name, if a heading is out of order, if a deadline cannot be read, or if anything else stops you: write to support@setstraight.app with the page or screen, the device, and what you were trying to do. A person reads that mail. We will answer, and we will say what we changed or why we have not yet.