Accessibility statement
Everyone in the team should be able to answer
A survey about whether people feel able to speak up is no use if some of them can't use it. This page says how accessible Measure is, how we check, what we know still needs work, and how to tell us when something gets in your way.
The short version. We design and test Measure against the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. On our own testing it meets that standard. It has not yet been independently audited or tested by someone who uses a screen reader every day, so until it has, we describe it as partially conformant.
If anything here stops you taking part, email support@psychsafety.com. A person who built it will reply.
What this covers
Everything at measure.psychsafety.com that the people we work with use:
- the team survey people answer, and the self-check;
- signing in, building a survey, and the organiser's dashboard;
- the team's report and the organiser's report, including printing or saving them as a PDF;
- the organisation dashboard;
- the public pages, such as the questions, plans and this one;
- the emails we send organisers.
It does not cover our own internal administration pages, which only Psych Safety staff use. Our other sites (the Learning Lab, the Field Guide and the Toolkit) are separate and are not covered by this statement.
What you should be able to do
- Use it all with a keyboard. Every screen works without a mouse. When a new question appears, focus moves to it, and stays on the answer you picked.
- Zoom in to 400%. Pages reflow to a narrow column without scrolling sideways, down to 320 pixels wide.
- Change the text spacing (line height, letter and word spacing) without anything being cut off.
- Use a screen reader. Pages use proper headings, labels and landmarks, and every chart has a text description of what it shows.
- Take your time. There is no time limit on answering. If you reload the page part-way through, your answers so far come back, for up to an hour.
- Sign in without a password or a puzzle. Organisers sign in with a six-digit code sent by email, which can be pasted in. There is no CAPTCHA. A code lasts ten minutes; a new one can be asked for at any time.
- Answer in your own language, or in plain English. Respondents can answer in English, Spanish, German, French or Korean, where the organiser offers them, or in Easy Read English: the same questions in short sentences and everyday words.
- Say "I don't know". Team questions offer "I don't have enough information to say", so nobody has to guess.
- Turn off motion. If your device asks for reduced motion, the small transition between questions is switched off.
How we check
- On every release: automated walk-throughs of the main journeys in a real browser, including a keyboard-only run through a survey that checks where focus goes, and a check that the text colours the pages use keep at least 4.5:1 contrast. A release that fails any of them doesn't go out.
- Automated WCAG 2.2 AA scans (axe) of 39 screens, from the public pages through every step of building, answering and reading a survey. The latest, on 23 October 2026, found no failures once the issues it and our own checks raised that day were fixed: colour contrast in two places, the edges of form fields, table headers, headings for each question, and the number keys that answer a question.
- Manual checks of reflow at 320 pixels, text spacing, keyboard focus in dialogs, single-key shortcuts, the contrast of form-field edges, and whether anything fixed to the screen can hide what has focus.
Automated tools find only some accessibility problems, which is why the next step is a review by a regular screen-reader user (see below).
What we know still needs work
- Screen-reader testing by a daily user. Nobody who relies on a screen reader every day has yet tested Measure with NVDA or VoiceOver. We are arranging this, and will update this page with what we learn.
- The browser tab title stays the same as you move between steps of building or answering a survey. Each step has its own heading, and focus moves to it, but the tab title doesn't change with it.
- A few messages use the browser's own pop-up (for example, a close date out of range in the survey builder). They are read out by screen readers, but a message beside the field would be clearer.
- Saving a report as a PDF uses your browser's print function. How well the PDF works with assistive technology depends on the browser; recent versions of Chrome and Edge produce tagged PDFs. The report itself is always available as a web page.
If something gets in your way
Email support@psychsafety.com, or use Help & feedback at the bottom of any page in the survey. Tell us what you were trying to do and what happened; you don't need to give your name. If you need the survey or a report in another form, such as large print or read aloud on a call, tell us what would help and we'll do what we can. A respondent's answers stay anonymous whichever way they reach us.
If you are an organiser, and someone in your team can't take part because of something here, tell us. We would rather fix it than have them left out of the result.
For procurement
An Accessibility Conformance Report for Measure, using the VPAT 2.5 template (WCAG edition), is available on request from support@psychsafety.com.
This statement was prepared on 23 October 2026, based on testing by Psych Safety, and is reviewed whenever Measure changes in a way that could affect it.