Accessibility
We’re committed to making Zephyria accessible to everyone. Here’s what we’ve built, what we’re improving, and where we need your help.
What we’ve done
WCAG 2.1 AA contrast
Body text, link text and status labels are measured against WCAG 2.1 AA contrast in both light and dark themes by computing the ratios from the stylesheet rather than judging by eye, and the colours we checked clear 4.5:1 against the background they actually sit on — including the tint behind a status label, which is not the same as the page behind it. That is one success criterion, not full AA conformance, and we have not audited with assistive-technology users. Every interactive element is reachable and operable by keyboard, with a visible focus indicator, and a skip link jumps straight to the main content. Automated accessibility testing is not yet part of our pipeline.
Keyboard navigation
Every interactive element is reachable and operable with a keyboard alone. Focus indicators are visible and consistent.
Semantic HTML & ARIA
Semantic HTML, proper ARIA labels, and meaningful link text throughout. Skip navigation links for keyboard users.
Reduced motion
Animations are disabled for users who prefer reduced motion (system preference respected).
Voice-based interaction
Iris provides voice-based interaction as an alternative to visual UI — a core accessibility feature for our product.
Voice demonstrations
We provide voice demonstrations through Iris for users who prefer or require non-visual navigation. Our voice interface supports conversation-based interactions without relying on visual UI elements.
Explore Iris →Known gaps
We’d rather hear about a barrier than pretend it doesn’t exist. Here are the gaps we know about and are actively working to close:
Live captions during a voice demo
A live conversation with Iris has no on-screen captions yet, so the demo is not usable without audio. Where that is a barrier, ask us and we will arrange a recorded walkthrough, a text-based session, or a call with a person.
IN DESIGNNo audit with assistive-technology users
We have not completed an audit with people who use screen readers, switch access or voice control day to day. Automated checks and our own keyboard testing are not a substitute for that, and we are not going to claim otherwise.
IN DESIGNAutomated testing integration
We haven’t yet integrated automated accessibility testing into our CI/CD pipeline. This is a priority for the next development cycle.
IN DESIGNForm error communication
Some form errors could be more clearly communicated to screen reader users. We’re improving error messages and focus management across all forms.
IN DESIGNVideo transcripts
When we add video demos or product walkthroughs, we’ll provide full transcripts and audio descriptions. Currently, our product demonstrations are text and voice-only.
IN DESIGNFound a barrier?
Tell us. We’ll fix it.