JFDI Consulting is committed to making this site usable by as many people as possible. This includes people with visual, auditory, motor, or cognitive disabilities, and people using assistive technologies such as screen readers, screen magnifiers, voice input, or keyboard-only navigation.
Conformance target
This site aims to meet Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We test against the success criteria in that standard and use automated tools (axe-core via Playwright, Lighthouse) to regression-gate every change.
What we have done
- Skip-to-main-content link as the first focusable element on every page
- Visible focus indicators on every interactive element (outline ≥2px, ≥3:1 contrast against surrounding surfaces)
prefers-reduced-motionhonoured across all animations, transitions, and scroll-reveal effects- Minimum 24×24 CSS pixel touch targets on interactive elements
- Form error recovery that moves focus to the first invalid field and announces error count via an ARIA live region
lang="en-GB"set on every page so assistive tech selects the right voice and dictionary- Automated WCAG 2.2 AA gate in CI — any violation blocks the build
Known limitations
- Cloudflare Turnstile (our anti-spam widget on contact and newsletter forms) is a cross-origin iframe we cannot inspect directly. Cloudflare publishes Turnstile as WCAG 2.2 AAA compliant at the widget level. We exclude it from our own axe-core scans because the iframe is sandboxed.
- YouTube embeds (a single case-study page) render as a lazy-load facade by default — a button plus poster image. When activated, the embedded iframe is YouTube’s own interface; its accessibility is YouTube’s responsibility.
Audit
This statement was prepared following an internal audit completed in Phase 41 of the platform hardening milestone. The audit date is the date of deploy for the Phase 41 commit on this site (see the footer for the latest deploy timestamp).
Contact
If you hit an accessibility barrier on this site, please email us at [email protected] with a description of the issue, the URL, and (if you can) the assistive technology you were using. We aim to respond within three working days.
