Skip to accessibility information
Accessibility

Accessibility statement for Govform Builder

Accessibility information for people designing and managing services in Govform Builder.

About this statement

This statement applies to Govform Builder’s core service-design interface: the service library, page designer, component settings and service environment controls.

Govforms Limited is committed to making Govform accessible. You should be able to:

  • Navigate and edit services using a keyboard.
  • Enlarge text and use the interface on a narrow screen.
  • Identify controls, validation errors and changes using assistive technology.

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.

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 the service library, page navigation, page designer, choice menus, component settings, text-editing dialogs and environment controls, in light and dark themes.

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 24 combinations of core screens, light and dark themes, and viewport widths from 320 to 1280 pixels. The final scans reported no WCAG A or AA violations.
  • Keyboard testing covered navigation, option menus, editing dialogs, toolbar arrow controls and alternatives to dragging. We checked 102 representative focus states, including visible focus and controls remaining unobscured.
  • Visual checks covered 200% browser zoom, doubled text size, portrait and landscape layouts, and increased line, letter, word and paragraph spacing. Contrast measurements included text, field boundaries and focus indicators.
  • Focused regression tests checked shared field rendering, session warnings, repeated session extensions and failure handling. 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.