Accessibility
Designed towards WCAG 2.2 AA.
Accessibility is an ongoing responsibility, not a badge or one-off certificate.
Statement date: 26 July 2026.
Measures included
- Semantic headings, landmarks and one main heading per page
- Keyboard-accessible navigation with Escape-key closing
- Visible focus and skip navigation
- Responsive reflow, readable line lengths and touch-sized controls
- Status labels that use words rather than colour alone
- Reduced-motion support
- Labelled forms with plain instructions
- HTML and Markdown versions of controlling methodology documents
Checks completed for this release
The package was checked for internal links, heading structure, form labels, responsive layouts, keyboard navigation logic, colour-independent status text and desktop and mobile rendering. These checks do not constitute independent accessibility certification.
Known limitations
Google-hosted fonts depend on a third-party service and fall back to system fonts if unavailable. Word downloads may be less accessible than the linked HTML or Markdown content. Netlify’s hosted form-management interface is outside the public site and is not assessed by this statement.
Report a problem
Use the contact form and select Privacy or accessibility. Include the page, device, browser and nature of the problem where possible.