Our commitment
We aim for the evaria.ai website and studio to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. This statement describes where we are today.
What we do
- Semantic HTML, landmarks, a skip link and a logical heading structure on every page.
- Everything can be used with a keyboard, with a visible focus indicator.
- Text and controls meet WCAG AA contrast ratios; layouts reflow down to narrow phone widths.
- Form fields have labels, and errors are described in text and announced to screen readers.
- Progress in the studio is announced through live regions.
- Sample recordings use the browser’s own audio controls and come with captions and a full transcript.
- Animation stops when your system asks for reduced motion.
- Every public page is checked automatically with axe-core before release, and key journeys are tested with a keyboard.
Known limitations
- We have not yet had an independent accessibility audit, and automated tools cannot catch every problem.
- Narration produced by Evaria is AI-generated speech. It can misread notation, so it should be reviewed before it is used as an accessible alternative; the studio always provides the script and captions alongside the audio.
- Captions are timed at utterance boundaries rather than word by word.
- Payment pages are provided by Stripe and are outside our control.
Feedback
If something on the site is hard to use with your setup, please tell us — through the contact form or at hello@evaria.ai. Describe the page and what happened, and we will work on a fix and, meanwhile, help you another way.