Accessibility

We target WCAG 2.1 Level AA on this site and on the platforms we build. That covers keyboard operability, visible focus, color contrast, semantic structure, meaningful alternative text, resilient zoom and reflow, and respect for reduced-motion preferences.

We treat AA as the floor rather than the finish line. Where a pattern is technically conformant but still awkward to operate with a keyboard or a screen reader, we change the pattern.

Accessibility is part of the work, not a pass at the end.

• Semantic headings and landmarks, with a single main region per page, so screen readers can navigate structure.
• A skip link, a logical tab order, and a visible focus ring on every interactive element.
• Contrast checked against the deep navy palette rather than assumed, including muted text and form placeholders.
• Motion tied to prefers-reduced-motion, so the ring-to-particles animation and section transitions never block content.
• Forms with real labels, required fields marked in text as well as symbol, errors described next to the field and summarized at the top, and focus moved to that summary on a failed submit.
• Multi-step flows that announce the current step, expose progress to assistive technology, and never rely on color alone to indicate state.
• Tap targets sized for touch, and layouts that reflow to 320px without horizontal scrolling.

Keyboard-only passes on every new page, automated checks during development, and manual review of headings, labels, and focus order. Automated tooling catches a minority of real problems, so we also read the markup and operate the interface without a mouse.

We have not commissioned an independent third-party audit of this site. When we do, we will say so here and publish the date.

This is an evolving site, and we would rather name gaps than imply perfection.

• Externally hosted venture, client, and partner sites we link to are outside our direct control, and we cannot guarantee their conformance.
• Any third-party embed we add later carries its own accessibility behavior, which we will evaluate before shipping it.
• Long-form article typography and data-heavy layouts get the most scrutiny at desktop widths; we continue to refine them at small sizes.
• Where we find gaps in our own pages, we fix them in the next release rather than waiting for an audit cycle.

If something on zerotomany.lovable.app is hard or impossible to use, tell us. Email hello@wearezerotomany.com with the page address, what you were trying to do, and the assistive technology, browser, or device you were using.

We respond to accessibility reports ahead of general inquiries, we will tell you what we found and when it will be fixed, and we will supply the same information in another format if that is faster for you. If you would rather not use a web form or email client, say so and we will find another way.

If our response does not resolve the issue, write to hello@wearezerotomany.com with "Accessibility escalation" in the subject line. It goes to both founders. This statement applies to zerotomany.lovable.app and does not limit rights you may have under applicable accessibility law.