Everyone should be able to use this site.

1 · What we’ve built in

This website was designed with accessibility as a first-class concern, not an afterthought. Specifically:

• Semantic HTML — correct landmarks (<header>, <main>, <nav>, <footer>), heading hierarchy, and labelled form fields.
• Keyboard navigation — every interactive element is reachable and operable from a keyboard. Visible focus rings (clay outline) appear on tab. A “Skip to content” link is the first focusable element on every page.
• Colour contrast — our warm-cream + ink palette is designed to meet WCAG AA contrast (4.5:1 for body, 3:1 for large text) in both light and dark themes.
• Dark mode — a Light / System / Dark theme switcher in the header. The site honours your operating system preference if you choose “System”.
• Reduced motion — the scroll-driven logo morph, header transitions and reveal animations all respect prefers-reduced-motion: reduce. Set the OS preference and animations are disabled automatically.
• Scalable typography — layouts use clamp() and relative units (em, rem) so the site reflows cleanly when you zoom up to 200%.
• Descriptive link text — we avoid “click here”; links say what they lead to.
• ARIA labels — icons, the theme switcher, and the brand mark all carry appropriate aria-label / aria-hidden attributes.
• No flashing content — no animation flashes more than three times per second.
• No auto-play media — no auto-playing video, audio or carousel.

2 · Known limitations

We’re transparent about where we’re not perfect today:

• Placeholder imagery — case-study and insight cards currently use text placeholders (e.g. [Editorial illustration]) instead of real images. When real photos and illustrations are added, they will carry descriptive alt text.
• Calendly embed — the booking widget on the Contact page is a third-party iframe. Its accessibility depends on Calendly’s own conformance. Until it’s wired up, the placeholder offers a direct mailto link as an alternative.
• Form validation messages — the contact form is currently a static demo; once it’s wired to a backend, server-side error messages will be announced to assistive tech via aria-live.
• Audit cadence — we self-test against WCAG 2.1 AA. We have not yet commissioned an independent accessibility audit; we plan to do so in 2026.

3 · How we test

• Keyboard-only walkthrough of every page on every release.
• Screen reader spot-checks with VoiceOver (macOS / iOS) and NVDA (Windows).
• Lighthouse accessibility audit; target score ≥ 95.
• Colour-contrast verification with the WebAIM contrast checker.
• Zoom test at 200% and 400% in modern browsers.

4 · Compatibility

The site is built with progressive enhancement and works in the latest two versions of:

• Chrome, Edge, Firefox, Safari (desktop & mobile)
• iOS Safari and Android Chrome
• VoiceOver, NVDA, TalkBack

JavaScript is used to inject the shared header / footer chrome and to drive the theme switcher and scroll animations. Content remains readable without JavaScript, though navigation chrome will be limited in that mode.

5 · Alternative formats

If you need any content from this site in a different format — large print, audio, plain text, structured data — email info@finox.co.uk. We aim to respond within 5 working days.

6 · Reporting an issue

If you find an accessibility problem we haven’t already listed, please tell us. We’ll acknowledge within 5 working days and aim to fix it within 30.

• Email: info@finox.co.uk with the subject line “Accessibility”
• Include the page URL, what went wrong, the assistive technology (if any) you were using, and your browser / OS

7 · Enforcement

If you’re not satisfied with our response, you can contact the Equality Advisory and Support Service (EASS) for England, Scotland and Wales:

• Website: equalityadvisoryservice.com
• Phone: 0808 800 0082
• Text: 0808 800 0084

This statement was prepared on 13 May 2026 based on a self-assessment against WCAG 2.1 Level AA. It will be reviewed at least once a year, and after any significant change to the website.