Accessibility

Accessibility Statement

Last updated: 15 September 2026

Our commitment

TwinaForms builds forms that are filled in by the public — volunteers, donors, applicants and service users. If a form cannot be completed by someone using a screen reader or a keyboard, the form has failed at its job. We treat accessibility as part of whether the product works, not as an optional extra.

The standard we work to

We work to Israeli Standard IS 5568, which is based on the Web Content Accessibility Guidelines (WCAG) 2.0 at Level AA. Accessibility is reviewed as part of our ongoing development, and we continue to improve it as the product develops.

This website

This website is built as standard HTML with semantic structure, descriptive page titles, text alternatives for images, labelled navigation landmarks, and support for both left-to-right and right-to-left reading. It can be navigated by keyboard and resized without loss of content.

Published forms

Forms published with TwinaForms are generated by our software, so much of their accessibility is determined by us rather than by the organisation that built the form.

Currently in place: every field is given a programmatically associated label; required fields are marked using native HTML so that assistive technology announces them; field validation uses the browser's built-in mechanism, which screen readers understand; autocomplete hints are provided so that browsers can fill in personal details; and both right-to-left and left-to-right layouts are fully supported, including Hebrew.

Where we are still improving. We are continuing to improve how status and error messages are conveyed to assistive technology, and how grouped choice questions are announced. These are scheduled improvements to our form generator, and every form republished after they ship benefits from them automatically.

Colour contrast depends on the visual theme chosen by the organisation publishing the form. We are adding a contrast check to our theme editor so that form authors are warned before publishing a combination that falls below the standard.

A note for organisations publishing forms

Some of what makes a form accessible is in your hands rather than ours: writing clear field labels and instructions, providing meaningful alternative text for any images you add, choosing a theme with sufficient contrast, and keeping forms as short as the task allows. We are happy to advise.

Reporting an accessibility problem

If you encounter a barrier on this website or on a form published with TwinaForms, please tell us. Reports from people who actually hit the problem are the most useful information we receive, and we treat them as defects rather than as suggestions.

Contact: supportat@twinaforms.com

Please tell us the page or form address, what you were trying to do, and the assistive technology or browser you were using, if you can. We will acknowledge your report and tell you what we intend to do about it.

If your problem concerns a specific form published by an organisation — its wording, its questions, or the service behind it — that organisation is responsible for it. If you are not sure who to contact, write to us and we will help you find them.