Last update: 11 October 2026

Accessibility statement

1) Our commitment

Polzy is used by the people who run a feedback programme and by everyone who answers one, so it has to work for people who use a keyboard, a screen reader, magnification or voice control. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, the level the European standard EN 301 549 sets for the web.

This statement covers the website at polzy.ai, the help center, the Polzy app and the survey pages your respondents answer.

2) Compliance status

Polzy partially conforms to WCAG 2.1 level AA: most of it meets the standard, and the parts that do not yet, or that depend on what a survey's author chooses, are listed under Known limitations.

3) How we checked

This statement is based on our own assessment, not on an external audit. We check:

Keyboard. Every page and control can be reached and used without a mouse, in a visible focus order, with a link to skip to the main content. Dialogs and the mobile menu keep focus inside them while open and give it back when they close.
Screen readers. Controls carry the roles, names and states a screen reader announces, and moving to another page is announced. Our tests find controls by their accessible role and name, so a control that loses its name is noticed.
Contrast. The interface's colours are defined once, as design tokens, and automated tests check that text meets the AA contrast ratio on every background, in light and dark mode. On a survey, the text on a control painted in the author's brand colour is chosen to stay readable.
Automated checks. Shared controls and key screens, including the survey a respondent answers, are checked with axe-core in our test suite.
Motion. Animation follows your device's reduced-motion setting.

4) Known limitations

What a survey's author chooses. A survey is painted in the workspace's own colours, fonts and images. Polzy keeps the text on its controls readable, but cannot check every choice: a pale colour on a light background, a picture behind the questions, or custom CSS an author adds can make a survey harder to read.
Images without a description. An image an author adds to a survey is described to a screen reader only when they write its alternative text.
Content from other services. A GIF chosen from GIPHY carries the description GIPHY gives it, and a survey embedded in another website is only as accessible as the page around it.
Charts. Some charts in results and analytics are not yet fully described to a screen reader. The answers behind them can be exported.
PDF documents. Invoice and credit-note PDFs are not tagged for screen readers. Write to billing@polzy.ai and we will send you the same document in a form you can use.

5) Report a problem

If part of Polzy is hard or impossible for you to use, write to support@polzy.ai. Tell us the page, what you were trying to do and, if you use one, your assistive technology. We reply within two working days and tell you what we will do and when. If you need information in another form, we will help you get it.

If you are answering a survey, you can also contact the organization that sent it to you.

6) Enforcement

If you are not satisfied with our reply, you can contact the authority responsible for enforcing accessibility requirements in your country.

7) About this statement

This statement was prepared on 11 October 2026. We review it when a change to the product affects accessibility, and at least once a year.