Accessibility
Accessibility
How the forms made here work for everybody who fills them in, how we check that, and what is not perfect yet.
What we aim for
The forms visitors fill in, embedded in a page, opened over it or on their own hosted page, aim to meet WCAG 2.2 at level AA, the standard the European Accessibility Act and the Dutch government build on.
What that means in a form
- Every field has a visible label tied to it, and help text and error messages are read out with the field they belong to.
- A form sent with problems says so once, at the top, and puts the cursor in the first field to fix.
- Every part works with a keyboard alone. In a form with steps, moving to the next step announces which step it is.
- A form shown as a dialog keeps the keyboard and screen reader inside it until it is closed, closes with Escape, and returns the focus to where it was.
- No puzzles to prove you are human: spam is stopped by a check the browser does on its own, without asking anything of the visitor.
- The layout follows the space it has rather than the screen, so the form stays usable when zoomed in, and animations stop when the device asks for reduced motion.
How it is checked
With axe-core, against WCAG 2.0, 2.1 and 2.2 at A and AA, on forms with every type of field: before anything is filled in, after sending a form with errors, at each step of a form with steps, with entries added and removed in repeating groups, and in the popup modes. Keyboard behaviour and focus are checked by hand on the same forms.
What depends on the form’s owner
The organisation that publishes a form chooses its colours, texts and questions. Our default theme meets the contrast requirements; a theme of their own should keep text and buttons at a contrast of at least 4.5 to 1 against their background. Labels and help text are theirs to write clearly.
Known limitations
- The builder that organisations use to make forms has not yet been checked to the same level as the forms themselves.
- A form shown in an iframe, such as on SharePoint, has the height its page gives it, and can need scrolling inside the frame.
- A Dutch address filled in from the postcode is filled in without being read out. The filled-in fields can be checked and changed as usual.
Something does not work for you?
Tell the organisation whose form it is: they can help you another way, and pass the problem on to us. If you build forms here, tell us through Support in the builder.
Or write to us:
Formscoop · Connected ConceptsHet Schaakbord 5
1567 MG Assendelft
The Netherlands
Last checked: October 2026.