The toolkit is built for product and design teams, and we want it to be usable by everyone on those teams, whatever their abilities. Accessibility isn’t a finishing step here; it’s part of how the product is designed and built.
What we aim for
We build to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA: the standard most widely used to make web content usable with keyboards, screen readers, magnification, and other assistive technologies.
Conformance status
The toolkit is partially conformant with WCAG 2.1 AA: it meets most of the criteria, and we’re actively closing the gaps below. This statement is based on an internal self-evaluation carried out on 29 July 2026.
What we’ve done
- Structured pages semantically: clear landmarks (header, main, footer) and a logical heading order.
- Made every interactive control reachable and operable by keyboard, with visible focus indicators.
- Given form fields visible, persistent labels, and made validation errors announced to assistive technology.
- Checked colour contrast so text meets AA against its background, and added a scrim so navigation stays legible over imagery.
- Respected the system “reduce motion” setting: animations hold still for people who prefer that.
- Given meaningful graphics text alternatives, and hidden purely decorative visuals from assistive technology.
- Kept layouts responsive so content reflows and stays usable when zoomed.
Known limitations
We know some parts aren’t fully there yet, and we’re working on them:
- Some text set over the hero imagery is still being tuned to guarantee contrast in every lighting condition.
- A few interactive components (such as the FAQ) don’t yet announce every state change to screen readers as fully as we’d like.
- The FAQ tabs use a simplified pattern; complete arrow-key navigation is on our list.
- Some embedded third-party flows (payment via Stripe, scheduling via Calendly) are outside our direct control.
What’s coming
- Ongoing manual testing with screen readers (VoiceOver, NVDA) and keyboard-only navigation.
- Completing the outstanding ARIA patterns and contrast tuning above.
- A formal accessibility re-check before each significant release.
Tell us what you find
If any part of the toolkit is hard to use, we want to hear about it. It genuinely helps us improve. Email support@jcerejo.com with what you were trying to do and where it broke down. We’ll respond, and where we can, provide the content another way while we fix it.