Legal
Accessibility
Last updated: July 9, 2026
This statement describes how Vesper (operated by Carpenter Create LLC) approaches accessibility, where we stand today, and how to reach us if you hit a barrier. It covers this site and the Vesper app.
Our commitment
We want Vesper to be usable by as many people as possible, including those who rely on assistive technology. Accessibility is part of how we design — calm, high-contrast ink-on-porcelain visuals, keyboard-operable controls, labeled inputs, and motion that respects your “reduce motion” setting. This is ongoing work, not a finished checkbox.
Conformance status
We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our target. Our conformance is partial and improving: Vesper has not yet completed an independent audit or a full manual screen-reader review, so we describe our status as “working toward” rather than “fully conformant.” We would rather be honest about where we are than overstate it.
What we’ve done so far
Semantic HTML and labeled controls throughout, text alternatives for informational icons and charts, visible keyboard focus, and animations that honor your system “reduce motion” preference. The interface uses a single, high-contrast accent and generous spacing to stay legible.
Known limitations
Some areas have not yet completed a full keyboard and screen-reader pass — in particular the conversational Ask Vesper planner, the interactive weather charts (hourly graph, sun path), and voice features. Dynamic updates may not always be announced to screen readers, and third-party surfaces such as the Stripe checkout follow their own providers’ accessibility. We’re actively working through these.
Report an accessibility issue
If something is hard to use or a barrier gets in your way, please tell us through our contact page. Include the page and what happened, and a way to reach you. We read every report, aim to respond promptly, and prioritize fixes for barriers that block core tasks.
Ongoing improvement
We review accessibility as we build, fold reported issues into our work, and update this statement as things change.