Accessibility statement

Accessibility statement

Controlled document: ACC-DOC-ACCESSIBILITY (decision ACC-ACCESSIBILITY-001) Candidate version: 0.3
Release tested so far: the first public release passed the project's automated checks and its final deploy-preview and live-domain browser checks on 5 August 2026.
Legal wording basis: FND Guide is not a public-sector body. This is a plain account of the project's accessibility work, not a copied public-sector statement.

Service and standard

• Covered: the public site at fndguide.co.uk and its www redirect.
• Standard tested against: WCAG 2.2 level AA (the project's stated target).
• Scope and exclusions: all public pages; externally linked sites are outside our control and outside this statement.
• Compliance status: no formal conformance claim is made. The live release has not had an independent accessibility audit or assistive-technology user testing.

What you should be able to do

The site is built with semantic HTML and limited JavaScript. On the tested candidate you should be able to:

• zoom to at least 400% and read reflowed text without sideways scrolling;
• reach everything with a keyboard in a sensible order, with visible focus;
• use a screen reader with meaningful headings, landmarks, labels and link text;
• read comfortably with reduced-motion and contrast preferences respected;
• understand pages written for low energy and brain fog: short sections, one idea at a time, no jargon without explanation;
• use the worksheet fields with proper labels, and lose nothing important if scripting is unavailable — every page works without JavaScript;
• print preparation pages cleanly;
• ask for information in another way through the contact route.

These points were checked against the exact deploy preview and live domain on 5 August 2026. Any problem found later will be recorded here rather than hidden behind a broad compliance claim.

Known issues

Reporting and alternative access

• Accessibility contact: hello@fndguide.co.uk
• Monitored by: the project owner.
• If something is inaccessible to you, tell us what you were trying to read and what happened; we will try to provide the information in a way that works for you (for example plain text by email) while the underlying issue is fixed.
• Escalation: the complaints route on the corrections page.
• Contact test evidence: the direct mailbox, purpose-specific forwarders and external reply path passed on 2 August 2026. If this address fails, the About page records the current alternative route.

Test evidence

• Statement prepared: 17 July 2026; updated 5 August 2026.
• Internal checks to date (research builds, recorded in the project QA records): keyboard-reachable structure, label bindings, one-H1-per-page, landmark structure, 390–1440 px layouts without horizontal overflow, no-JavaScript rendering of all routes, print layouts, and automated axe-core checks in the test suite.
• Current generator and response-header contract last tested: 5 August 2026; the exact first public release also passed deploy-preview and live-domain route, layout and response checks.
• Assistive technologies tested: none yet; disclosed above.
• Disabled-user or access-needs testing: none yet; the prepared protocol can be used when participants are available.
• Full report location: internal QA and production-readiness records.

Review record

• Accessibility-owner check: project owner / 5 August 2026, controlled successor version 0.3.
• Independent accessibility advice or testing: not obtained — disclosed above.
• Legal or governance advice: not obtained.
• Owner exact-version decision: approved for the controlled successor transaction; publication still depends on that transaction and the exact correction-release checks.
• Next review trigger: any release that changes page structure, navigation or interactive elements.
• Exact owner-approved file SHA-256: none; this is not an approved version.