Accessibility of questionnaires
Pristo CX questionnaires work with a keyboard and with screen readers, in light and dark themes and in right-to-left languages. This reference lists what the respondent forms do, what you can do as the author to keep a questionnaire accessible, and the gaps respondents may still meet. It describes the forms as released on 11 October 2026 and is not a certification or a claim of conformance to a standard.
This page is about the questionnaires your respondents answer. The accessibility statement covers this Help Center, the site you are reading.
Summary
Section titled “Summary”| Area | What the forms do |
|---|---|
| Keyboard | Respondents can answer every question type and use the buttons and menus with the keyboard alone. The first Tab stop on a page is Skip to content, which moves past the header to the questions |
| Labels | A question’s title is its label. Screen readers also read whether it is required, its description and its error message |
| Focus | Buttons, options and links show a 2-pixel outline in a fixed color when they have the focus. Text fields show a thicker border in the questionnaire’s secondary color |
| Errors | A question with a problem is marked invalid and shows its message under it. A dialog explains the problem, and closing it moves the focus to the first question to fix |
| Pages | The page bar reads each page as a step, such as “Step 2” and the page name, and says which steps are completed. Tabs also say whether a page is valid or invalid, not only by color |
| Announcements | Screen readers announce a cleared field, a chosen date and a counter’s new value |
| Languages | The page declares the language it shows. Right-to-left languages, such as Hebrew, mirror the layout, and arrow keys follow the reading direction |
| Theme | Respondents can switch between the light and the dark theme. The button is named after what it does, such as Turn Dark |
| Zoom and motion | Respondents can zoom in on phones. When the device asks for reduced motion, animations and scrolling are instant |
Keyboard use by question type
Section titled “Keyboard use by question type”| Question type | How it works with a keyboard |
|---|---|
| Text and number fields | Respondents type the answer. Long text answers, and text fields with a length limit, show a character counter |
| Choices and checkboxes | Standard radio buttons and checkboxes |
| Smiley and numeric rating scales | The scale is one Tab stop. The arrow keys move between options in the reading direction, Home and End go to the first and the last option, and Space or Enter selects. Selecting the chosen option again clears it |
| Grids | Each row is a group of options named after the row, and each option reads its row and column |
| Date and time | Respondents type the date, or press the Down arrow key to open the calendar. In the calendar, the arrow keys choose a day, Enter selects it, and Esc closes it and keeps the earlier date. The calendar button also moves the focus into the calendar |
| Counter | The plus and minus buttons are named after the question, and each press announces the new value. At the lowest or highest value, the focus moves to the field |
| Signature | Respondents draw in the box, or type their full name in Or type your full name instead |
| Photo, audio and video | Named buttons take a photo and start, pause, resume and stop a recording |
Changes since 21 September 2026
Section titled “Changes since 21 September 2026”- Keyboard users can move into the date picker’s calendar and back out, and Esc keeps the earlier date. In right-to-left languages, the Left and Right arrow keys follow the mirrored calendar.
- Counter buttons are named after their question, screen readers announce the new value, and the focus moves to the counter’s field at its lowest or highest value.
- Screen readers read the signature instructions once instead of twice.
- The Hebrew theme button names the action it takes.
- Confirmation dialogs use translated Confirm and Cancel buttons instead of English ones.
See What’s new in October 2026 for the other changes in this period.
Make your questionnaire accessible
Section titled “Make your questionnaire accessible”| Do this | Where | Why |
|---|---|---|
| Give every question a title | Title in the question’s settings | The title is the question’s label. A question without a title has no name for screen readers, and a placeholder does not replace it |
| Put instructions in the description | Description in the question’s settings | Screen readers read the description with the field |
| Describe every image that carries information | Alt text in the image’s settings | Screen readers read this text instead of the image, and skip an image without it. When you add a logo, its alt text starts as the file name, so replace it |
| Ask the question in words | The question’s Title | Answer options are text, and an image holds no answer. Do not put the question or the options only in an image |
| Name each page | A section title at the top of each page | Section titles are headings, which screen readers list. They help respondents find their place after they move to another page |
| Choose colors with enough contrast | Style in the form builder | In the light theme, buttons such as Next have white text on the secondary color, which also colors the page bar and selected options. Pristo CX does not check the contrast. White text on the secondary color of the Party theme has a contrast of about 2.5 to 1, and the Custom theme starts with light gray at about 1.5 to 1 |
| Add a title to the embed code | The embed code from the Share tab | The code has no title, and screen readers name a frame by its title. Add one, for example <iframe title="Example Coffee survey" …> |
| Test with the keyboard | Preview | Go through the questionnaire with Tab, the arrow keys, Space and Enter only, in every language it has |
See Question types for each question’s settings and Translate a questionnaire for the languages.
Known gaps
Section titled “Known gaps”| Gap | Effect | What you can do |
|---|---|---|
| The language button is hidden on phone-sized screens | Respondents on most phones see only the main language | For a phone audience that needs another language, create a separate questionnaire in that language |
| The focus does not move when the page changes | After Next or Previous, screen readers do not announce the new page, and the browser title stays the same | Start each page with a section title |
| An error replaces the description | While a question shows an error, its description is hidden | Keep instructions that respondents need to fix an answer in the title |
| The time picker’s lists | The hour and minute lists in the time picker have no names for screen readers and do not take the keyboard focus | Respondents can type the time in the field |
| Notifications are short | Messages such as Network Error disappear after 2.5 seconds | None |
| Some texts cannot be translated | Grid rows and columns, image alt text and the end page’s title and subtitle stay in the main language | Write them so that all your respondents understand them, or use a separate questionnaire per language |
| Pages before the questionnaire | The expired, thank-you and unsubscribe pages are in English or Hebrew only | None |
| Language names | The language menu names each language in English, such as Hebrew, not in the language itself | None |
| The redirect picture | The picture on the end page that redirects respondents has no text alternative | None |