Accessibility
Last updated: 7 September 2026
Our commitment
We want divin.ai to be usable by everyone, including people who use a screen reader, navigate by keyboard only, or rely on their browser's zoom or high-contrast settings. We're a small team, and we won't pretend we've reached full conformance with any accessibility standard, but it's something we actively work on rather than treat as an afterthought.
What we've done so far
- Button and link text colors are checked against WCAG AA's 4.5:1 contrast minimum, not just chosen because they looked fine.
- Menus, the mobile navigation, and FAQ accordions are built with native HTML disclosure elements, so they work with a keyboard and a screen reader without needing JavaScript to function at all.
- Form fields that don't have room for a persistent visible label (like the quick-add fields in your dashboard) still carry a real accessible label, not just placeholder text.
- We run automated checks against our own codebase before each release to catch the specific mistakes above if they ever get reintroduced.
What we haven't done yet
We haven't commissioned a full accessibility audit against WCAG 2.1 AA or any other formal standard, and we can't yet claim conformance with one. Some pages, especially newer ones, may not have been checked as thoroughly as others. If you run into something that doesn't work well with the tools you use, we'd genuinely like to know, see below.
Third-party content
When you subscribe to a plan, you're taken to a payment page hosted by Stripe at
checkout.stripe.com.
We don't control the accessibility of that page; Stripe publishes its own
accessibility information separately.
Report an accessibility issue
If you're having difficulty viewing or using any part of divin.ai, or you've noticed something that isn't accessible, please email us at [email protected] with "Accessibility" in the subject line, and describe the page and the issue you ran into. We read every message and take it into account.
Changes to this page
We'll update this page as our accessibility work progresses, and update the "Last updated" date above when we do.