Accessibility statement

Using this website

NOISSIME LTD runs this website and the survey application. We want as many people as possible to be able to use both — including people answering a survey, who did not choose the tool and may be doing it once, on a phone, in a hurry.

That means we intend for you to be able to:

• navigate the site and complete a survey using a keyboard alone;
• change colours, contrast levels and fonts using browser or operating system settings;
• zoom in to 300% without text spilling off the screen;
• use a screen reader to read and complete a survey;
• have the interface honour a reduced-motion preference, which the animations on this site do.

AbilityNet's My Computer My Way has practical advice on adjusting a device to suit your needs.

How accessible this website is

We do not yet know with certainty, and it would be dishonest to say otherwise. WCAG 2.2 AA is the target we design and build to, and we test as we go — keyboard order, focus visibility, contrast, form labelling and error messaging. That is internal testing by the people who wrote the code, not independent assessment, and internal testing reliably misses things.

Areas we consider higher risk, and have not independently verified:

• Ranking questions, which are operated by dragging items into order. Drag interactions are the hardest question type to make work well for keyboard and screen reader users.
• Matrix questions, where a grid of rows shares one scale. Grids can be verbose or ambiguous to a screen reader if the row and column relationships are not announced correctly.
• Bento option tiles, the default presentation for multiple choice and checkbox questions, and any option or question images a survey author adds.
• The conversational layout, which shows one question at a time and auto-advances on one-tap questions. Automatic movement can disorientate, and we have not verified the focus and announcement behaviour at each step.
• The builder itself, which is drag-and-drop. It is used by survey authors rather than respondents, but that is not a reason for it to be inaccessible.

Naming these is not an admission that each is broken. It is a statement about what we have and have not proved. As we verify them, this list shrinks and the statement is updated.

What survey authors control

A large part of whether a published survey is accessible is decided by the person who built it, not by us. If you are publishing a survey, particularly as a public sector body:

• write plain, short question text, and use the description line rather than cramming context into the title;
• give every question image a purpose — decorative images add noise for screen reader users;
• prefer a multiple choice or dropdown question to a ranking question where the ranking is not essential;
• keep equality monitoring questions optional;
• use conditional logic to keep the survey short, which helps everyone and helps people with cognitive or attention difficulties most;
• check the contrast of any per-survey accent colour you set against the text placed on it.

Your own accessibility statement should cover the survey you publish. This statement covers the platform underneath it.

Reporting an accessibility problem

We want to hear about anything that stopped you, including small things. Report a problem through the contact page. It helps if you can tell us:

• the web address of the page or survey;
• what you were trying to do, and what happened instead;
• the browser and version you were using;
• any assistive technology involved — screen reader, magnifier, voice control, switch access — and its version.

We aim to acknowledge a report within five working days and to tell you what we intend to do about it, including if the answer is that a fix will take time. If you need the content of a survey in another format so that you can respond to it, contact the organisation running the survey first, since they control its content and their obligations; tell us as well and we will help where the obstacle is ours.

Enforcement procedure

NOISSIME LTD is a private company, so the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 do not apply to us directly. They may well apply to the public sector organisation using our platform to run a survey, which is why this statement follows their format.

We do have duties under the Equality Act 2010, including the duty to make reasonable adjustments. If you are unhappy with how we have responded to an accessibility complaint, the Equality Advisory and Support Service (EASS) can advise you. Where a survey is published by a public sector body and you are dissatisfied with their response, complaints about the accessibility regulations are handled by the Equality and Human Rights Commission, or the Equality Commission for Northern Ireland in Northern Ireland.

Technical information about accessibility

We are committed to making this website and the survey application accessible, in accordance with the principles of the Public Sector Bodies Accessibility Regulations even where they do not bind us.

Compliance status

We make no compliance claim. The Web Content Accessibility Guidelines version 2.2 level AA standard is what we build to, but conformance has not been assessed by an independent party and we will not describe the site as "fully compliant" or "partially compliant" on the basis of our own untested opinion. When an audit has been completed, this section will state the result, the auditor and the date, including any failures found.

How we tested

Testing to date has been carried out internally by the development team during build: keyboard-only navigation, browser zoom, automated checks in the browser's developer tools, and manual inspection of focus order, labelling and colour contrast. No independent audit, and no user testing with disabled people, has been carried out. Both are things we intend to commission, and we will not present the intention as an achievement here.

Preparation of this statement

This statement was prepared on 22 July 2026 and describes the platform as at that date. It is reviewed when the interface changes materially and at least annually. Related pages: security, UK GDPR and the sub-processor list.