Accessibility Statement

We want FODSPOT to be usable by as many people as possible. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and we treat accessibility as a core requirement rather than an afterthought.

What we do

• Use semantic HTML and a logical heading structure.
• Support full keyboard navigation with visible focus outlines.
• Test colour contrast in the light theme, the manual dark theme and the dark theme your operating system asks for.
• Respect your system theme preference and provide a manual theme toggle.
• Build accessible forms with clear labels and error messages.
• Honour reduced-motion preferences for animations.
• Provide a responsive layout that reflows to a 320 pixel wide screen without side-to-side scrolling.

Conformance status

WCAG 2.2 AA is our target. We are not claiming that FODSPOT conforms to it.

A conformance claim covers every page and every complete task, and it needs testing by people as well as by software. We have not finished that work, so saying we conform would be a stronger statement than our evidence supports.

What we have tested, and when

An accessibility review on 25 August 2026 covered a representative sample of public pages using automated checks, plus targeted manual checks of reflow, keyboard focus, labels, landmarks and both ways of choosing a dark theme.

It found five faults, and all five have since been fixed:

• Supporting text failed the minimum contrast ratio when a dark theme came from your operating system rather than from our theme toggle.
• The business, jobs and events directories needed side-to-side scrolling on a narrow screen, because the search box and its button could not fit.
• Contact details on a business profile were not marked up as a description list correctly, which affects how a screen reader announces them.
• The “Call us” and “Email us” buttons did not include those words in the name that assistive technology and speech control use.
• The map on a business profile was described as an image while containing buttons, which gives assistive technology contradictory information.

What we have not tested yet

We are being specific about this so you know where the gaps are rather than assuming there are none:

• Signed-in journeys end to end: creating an account, claiming a listing, editing a business, posting a job or event, and payment.
• Full screen reader testing with NVDA, JAWS and VoiceOver, and testing with speech input.
• The embedded payment form, which is provided by Stripe.
• Setting an exact map pin using only a keyboard, when adding or editing a business.
• Windows high contrast mode, 400 per cent zoom and custom text spacing.

Feedback

If you encounter an accessibility barrier, or need information in a different format, please let us know and we’ll do our best to put it right. Tell us what you were trying to do and what got in the way, and we will reply. Your feedback helps us improve, and it tells us what to prioritise.