Commitment
finconduit is committed to making finconduit.com usable for all visitors, regardless of ability or the assistive technology used. Accessibility is a design principle we treat with the same seriousness as security, privacy, and regulatory conformance — not an afterthought added during a remediation cycle.
We aim for substantial conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, the international consensus standard published by the W3C and adopted directly or by reference into UK and EU law.
Audience
This statement applies to the public-facing finconduit.com website. Internal client-portal accessibility is governed under the relevant Master Services Agreement and is reviewed separately for each engagement.
Conformance Status
As of 8 June 2026, finconduit.com is in partial conformance with WCAG 2.2 Level AA. “Partial conformance” means that, while we have implemented the substantial majority of WCAG 2.2 AA success criteria across the site, some portions of the content do not yet fully conform. The known gaps are documented in Section 05 below, and we address them on a rolling basis as part of our regular development cadence.
Pages were self-assessed against WCAG 2.2 AA by the finconduit engineering team using a combination of automated tooling, manual keyboard walkthroughs, and screen-reader spot checks. An independent audit is scheduled — see Section 09.
Applicable Standards
Our accessibility work is anchored against three reference frameworks. Each is named explicitly so that compliance officers, procurement reviewers, and accessibility consultancies can map our posture against the criteria they assess.
- WCAG 2.2 Level AA (W3C) — the international web accessibility standard, covering perceivable, operable, understandable, and robust criteria across desktop and mobile.
- EN 301 549 v3.2.1 — the European harmonised accessibility standard, which incorporates WCAG 2.1 AA by reference and adds requirements specific to ICT procurement under the European Accessibility Act.
- UK Equality Act 2010 — the reasonable adjustment duty applicable to service providers in the United Kingdom, which we treat as the floor for our public-facing site.
Where a difference exists between the WCAG 2.2 baseline we target and the EN 301 549 v3.2.1 floor (which currently references WCAG 2.1), we work to the higher of the two.
What We Have Implemented
The list below describes the accessibility features that are in place across the site today. It is intentionally specific so that an accessibility reviewer can verify each item directly.
- Semantic HTML with landmark roles (header, nav, main, footer) used consistently across the site
- Skip-to-content link on every page via the fc-skip-link class — appears on first Tab
- Keyboard navigation across forms, interactive tools, and primary navigation
- Visible focus indicators on all interactive elements in both dark and light modes
- Minimum 4.5:1 contrast ratio on body text in both dark and light modes
- Theme switcher that respects the operating system prefers-color-scheme preference
- prefers-reduced-motion respected on framer-motion animations across the site
- Alt text on informational images; decorative SVGs are explicitly marked aria-hidden="true"
- Form labels associated with inputs via for/id pairs; inline error messages where validation applies
- ARIA roles, labels, and properties applied where semantic HTML alone was not sufficient
- Practitioner tools designed to be operable by keyboard, with input/output relationships exposed to assistive technology
Verification
A reviewer can confirm the implemented items above by inspecting the site source, using the Tab key from any page (the skip-to-content link appears immediately), toggling the OS-level reduced-motion preference, and switching themes via the in-page theme switcher.
Known Limitations
We document accessibility limitations rather than ignore them. Each item below is on an active worklist; expected remediation timelines are described in Section 09.
Slider-based tools
Some practitioner tools use sliders that may be challenging with certain screen readers. Keyboard arrow-key support is provided, but the visual band readouts may not announce smoothly in all assistive-technology combinations. Active workstream.
Blog footnote markers
Some long-form blog footnote markers may require manual navigation via keyboard shortcuts rather than direct keyboard focus. We are reviewing the markup pattern to make footnote anchors a primary tab stop.
PDF assets
PDF assets we publish (legal opinions, sample memoranda where published) may not be fully tagged for screen-reader use. If you encounter an untagged PDF, request an HTML alternative via info@finconduit.com and we will provide one promptly.
If you encounter an accessibility barrier that is not described above, we want to hear about it. Contact details are in Section 07.
Compatibility
finconduit.com is designed to be operable across the major modern browser and assistive-technology combinations. The matrix below shows where we have tested directly.
Browsers tested
Latest stable versions of Chrome, Firefox, Safari, and Edge on desktop and mobile.
Screen readers tested
VoiceOver on macOS 14+ and iOS 17+, NVDA on Windows 10/11.
Limited testing
JAWS testing is limited. We welcome detailed JAWS-related feedback at the contact address below.
The site uses progressive enhancement: core content and navigation work without JavaScript, and animations gracefully degrade where the browser or user preference indicates reduced motion. We do not require any specific browser plugin or extension to use the site.
Feedback & Contact
If you experience an accessibility barrier on finconduit.com, or if you want to request a more accessible format for any content, please contact us. We treat accessibility feedback as a priority queue and respond within five business days.
- Primary: accessibility@finconduit.com (preferred for accessibility-specific feedback)
- Fallback: info@finconduit.com — until the accessibility@ alias is provisioned, please use info@ and your message will be routed internally to the accessibility lead
- Response SLA: five business days from receipt
What to include
Where possible, include the URL of the page concerned, the browser and assistive technology in use, and a brief description of the barrier encountered. This lets us reproduce and address the issue more quickly.
Enforcement Procedure
If you are not satisfied with how finconduit has responded to an accessibility complaint, you have the right to escalate to your national accessibility-monitoring body. Contact details vary by jurisdiction:
- United Kingdom — Equality and Human Rights Commission (EHRC), which enforces the Equality Act 2010 reasonable adjustment duty.
- European Economic Area — each EEA member state has designated a national accessibility-monitoring body under the European Accessibility Act framework. Contact details are published by your national government.
We commit to responding to all accessibility complaints — direct or escalated — within five business days, and to providing a substantive remediation path or explanation within twenty business days where the matter is non-trivial.
Roadmap
This roadmap sets out our planned accessibility programme. Dates are good-faith targets; we will update this section as work progresses.
- Q3 2026 — complete an independent WCAG 2.2 Level AA audit by an accessibility consultancy.
- Q4 2026 — remediate gaps identified in the audit, prioritised by user impact.
- Q1 2027 — re-test the site against WCAG 2.2 AA using NVDA, JAWS, and VoiceOver, and update this statement to reflect the post-remediation conformance position.
Continuous review
Outside the scheduled audit cycle, accessibility is reviewed as part of every substantive feature release. Where a release would materially affect this statement, the statement is updated on or before the release date.