Accessibility
Statement last reviewed August 4, 2026 · covers crinkle.dev and the Crinkle beta app
The short version: we aim for WCAG 2.1 Level AA, we build with keyboards, screen readers, and reduced motion in mind, and when something falls short we want to hear about it and fix it: support@crinkle.dev.
Our target
We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA for this website, and we apply the same standard as the goal for the Crinkle app as it matures through beta.
What we do today
- Motion is optional. Every animation on the site, from the typing demos to the scroll effects, respects the system "reduce motion" setting and renders its full content statically instead.
- No JavaScript, no problem. The site's content is fully readable with scripts disabled.
- Semantic structure. Pages use real headings, landmarks, lists, and labels so assistive technology can navigate them; decorative graphics are hidden from screen readers.
- Contrast. The default palette keeps text at or above AA contrast against its backgrounds, in both the dark and light looks.
- Keyboard access. Interactive controls on the site (navigation, sign-in dialog, buttons) are reachable and operable by keyboard, and the sign-in dialog manages focus and closes on Escape.
- In the app, appearance options include light and dark themes and multiple color styles, and plain-language reporting is a design principle throughout.
Known limitations
Honesty over polish, here as everywhere:
- The animated demonstrations (team conversation, run telemetry) are illustrative visuals; their full text is available to assistive technology, but the "typing" presentation itself is visual by nature.
- The Crinkle app is beta software under heavy development; we have not yet completed a full accessibility audit of every screen, and some complex views (diff review, live activity feeds) still need work for screen-reader users. This is on the roadmap before any paid release.
Compatibility
The website is built to work with current versions of major browsers and their built-in and common assistive technologies. It does not require a mouse, precise gestures, or a specific orientation.
Feedback and enforcement
If you hit a barrier on the site or in the app, email support@crinkle.dev with the page or screen and what went wrong; we treat accessibility reports like bug reports, which is to say seriously. If you are in the European Union and believe we have not met our obligations, you may also contact your national market surveillance authority.