About this statement
This statement applies to the standard Govform REAL service interface: starting a service, answering questions, correcting errors, reviewing and changing answers, and submitting a response.
Govforms Limited is committed to making Govform accessible. You should be able to:
- Complete the standard service journey using a keyboard.
- Enlarge text and use the service on a narrow screen.
- Review and change answers before submitting them.
Each organisation operating a service is responsible for its own content, documents, branding and integrations, and must publish an accessibility statement for its complete service.
Compliance status
The assessed release of the interface covered by this statement is fully compliant with the Web Content Accessibility Guidelines version 2.2 AA standard.
Govform supports public-sector organisations in meeting the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Feedback and contact information
If you find an accessibility problem or need information in another format, email support@govform.com or contact us. Include the page address, the problem and the support or format you need.
For help completing a service, contact the organisation operating it using the details on that service.
Enforcement procedure
For public-sector services covered by the accessibility regulations, the Equality and Human Rights Commission (EHRC) is responsible for enforcement. If you’re not satisfied with the response to your accessibility complaint, contact the Equality Advisory and Support Service (EASS). In Northern Ireland, contact the Equality Commission for Northern Ireland (ECNI).
Preparation of this statement
This statement was prepared and last reviewed on 2 October 2026.
The assessment covered a complete representative REAL service journey, including validation, check answers, confirmation, mobile navigation and session-extension controls. Shared personal-information and authentication fields were also checked.
Govforms Limited carried out an internal assessment against all 55 WCAG 2.2 level A and AA success criteria, combining automated checks, source-code review and manual interaction and visual testing.
How we tested
- Automated axe-core checks covered the representative journey, including question pages, validation errors, answer review, confirmation and mobile presentation. The final scans reported no WCAG A or AA violations.
- Keyboard testing covered completing questions, following error links, reviewing and changing answers, submitting a response and operating mobile navigation. We also verified that the session warning receives focus and can be extended using the keyboard.
- We reviewed 40 visual captures across eight journey states, covering desktop, portrait, landscape, doubled text size and open mobile menus. Eight further narrow-screen checks applied increased line, letter, word and paragraph spacing.
- Focused rendering and runtime tests checked personal-information fields, error associations, session warnings, repeated extensions and unsuccessful requests. Issues found during the assessment were fixed and retested.
Assistive-technology checks examined the information exposed to screen readers through Chrome’s browser and macOS accessibility APIs. These checks covered accessible names, roles and states, headings, labels, errors, status messages and modal-dialog focus behaviour.
The sampled journeys were also checked manually with VoiceOver, including its spoken output. No issues were reported during these checks.
The findings, corrections and retest evidence were reviewed separately for interface quality and statement accuracy.
Based on the GOV.UK model accessibility statement. Template material is used under the Open Government Licence v3.0.