Legal
Accessibility statement
Effective May 20, 2026
Crescence is committed to making the marketplace usable for everyone. We target conformance with WCAG 2.2 Level AA and treat accessibility issues with the same urgency as functional bugs. This statement is effective on the date above and is reviewed at least quarterly.
What we do
- Every UI surface is keyboard-navigable. We do not ship interactive components that require a mouse.
- Every interactive element passes axe-core in our automated test suite. We treat axe failures as build-blocking.
- Color contrast meets WCAG AA on text and meets AA-large on supporting copy. Our design tokens are tuned to keep this true by default.
- Every form field has an explicit label. Validation errors are announced to screen readers via
aria-live. - Animations honor
prefers-reduced-motion. With OS reduced motion enabled, no animation longer than 0 ms plays. - Touch targets are at least 44x44 px on viewports below the medium breakpoint.
Where we know we still have work
- Real screen-reader walks against VoiceOver (macOS Safari) and NVDA (Windows Chrome) - the findings file lands at
docs/a11y/screen-reader-walk.mdper ROADMAP section 7.5.22 and is updated on every major release. - The Maia streaming surface (live token-by-token rendering) introduces motion that is technically excluded from reduced-motion rules. We are exploring a static-after-N-chars mode for the reduced-motion path.
Requesting an accommodation
If something does not work for you, please email accessibility@crescence.co. We acknowledge requests within 1 business day and aim to resolve within 10 business days. If a fix cannot happen in that window, we provide an alternate path so you can complete the task.
Audit cadence
We run automated accessibility checks on every pull request and conduct a manual full-platform audit at least every six months. The audit report is published internally and gates the next release.