Inclusive access

Accessibility statement

We want as many people as possible to be able to use Voxa, including people who rely on a screen reader, keyboard navigation, magnification, or other assistive technology. We review accessibility as the product changes.

How we approach it

Accessibility is considered while pages are designed and built, not bolted on afterwards. In practice we aim for:

Semantic HTML with a sensible heading order, page landmarks, and descriptive page titles.
Form controls with visible labels, clear error text, and status messages assistive technology can announce.
Full keyboard operation with a visible focus indicator, so no task depends on using a mouse.
Text alternatives for icons, images, and controls that carry meaning.
Layouts that reflow on small screens and when text is enlarged, with light and dark themes chosen for readable contrast.

The standard we work towards

We use the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as our reference point and try to meet it wherever we reasonably can. We have not completed a formal external audit, so we do not claim full conformance, and some parts of the service will fall short while we keep improving them. We review this statement as the product develops.

Where we know there are gaps

Some areas have had less accessibility attention than others, including the study and survey builders, data-heavy tables, and testing across the full range of browser and assistive-technology combinations. Studies are also built and hosted by researchers, so we cannot guarantee the accessibility of the questions or tasks inside every study. We ask researchers to consider access needs and we follow up on reports about specific studies.

Tell us if something does not work

If a page or task is hard or impossible to use, please tell us. You can also ask for information in another format or help with a task you cannot complete. In the contact form, choose support, then Accessibility. Tell us the page or study, what you were trying to do, and what happened. Details about your device, browser, or assistive technology can help, but only share what you are comfortable sharing. A person reads every message and replies by email. We cannot promise a fix or a timescale for every report, but we will tell you where it stands.