Accessibility statement
Last updated ·
What we aim for on this website, what has been built to meet it, and — stated plainly and in the same place — where it does not.
Our commitment
We want this site to be usable by everybody, including people who navigate by keyboard, use a screen reader or other assistive technology, need larger text or stronger contrast, or turn animation off. Accessibility here is part of how the site is built rather than an audit bolted on afterwards — and where it falls short, we would rather list it here than leave a visitor to discover it.
What this statement covers
This website: the English pages at the site root. It does not cover systems we build inside a client’s own environment; the accessibility requirements for those are set per engagement.
Conformance target
The target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This site is partially conformant with WCAG 2.2 Level AA: most of it meets the standard, and the specific places that do not are listed under “Known exceptions” below. “Partially conformant” is the accurate term and it is used deliberately — a claim of full conformance would be contradicted by our own design system, which records the failures in writing.
Keyboard and focus
Every control is reachable and operable by keyboard alone, and nothing traps focus — the mobile navigation and the consent banner are both non-modal and both close on Escape, because trapping focus in something that does not block the page is itself a failure. Focus is always visible: the indicator is drawn in two tones so that it keeps at least a 3:1 contrast against every surface colour in the design, which no single colour could manage. A skip link is the first thing in the document. Focus is moved deliberately after any action that changes what is on screen — sending a selection to the enquiry form, submitting it, or landing on a validation error.
Structure, forms and errors
Pages use real landmarks and a heading order that does not skip levels. Interactive elements are native ones wherever a native one exists — checkboxes rather than buttons imitating checkboxes, and a real disclosure widget rather than a scripted accordion — so keyboard behaviour and screen-reader announcement come from the browser rather than from our code. Every form control has a real label, never a placeholder standing in for one. Error messages are text, are tied to their control programmatically, and are also gathered into a summary at the top of the form. Colour is never the only signal for a state, and the interface is written to survive forced-colours mode, where the operating system replaces the palette entirely.
Motion, and working without JavaScript
Content that advances on its own carries a visible pause control that is in the accessibility tree and reachable by keyboard. A reduced-motion preference is honoured in JavaScript and not only in CSS — a stylesheet can shorten an animation but it cannot decline to start a timer — and the preference is re-read if you change it without reloading. Every page works with JavaScript disabled, blocked or still loading: the enquiry form posts and is processed, navigation is open rather than hidden behind a menu button that would do nothing, and no content is hidden by a script that may never arrive.
Language and direction
Every page declares its language and its text direction. The site currently publishes in English only, left to right. The stylesheets use logical directions rather than fixed left and right, so a right-to-left language can be published later without the layout being rebuilt as a mirrored copy of itself; that support is kept in place and is currently unused.
Known exceptions
The palette values that previously fell below the 4.5:1 minimum for body text have been corrected: the muted body text, the scrolling band of system labels, the integration examples, the small annotation on the “what we do” comparison, and the footer headings, copyright line and tagline now measure between 4.55:1 and 5.13:1. The original design values are retained in the design system so the change is reversible and auditable. One substantive exception remains. The main call-to-action button places white text on a gradient running from the brand blue to the accent teal; against the blue end that text measures 5.32:1, and against the teal end 1.82:1, so text over the second half of the button does not meet the minimum. It is recorded here explicitly because automated checkers do not report it — they cannot compute a ratio against a gradient, so they return “unable to determine” rather than a failure, and a reader would otherwise be told the page is clean. Correcting it means changing a colour that also appears in the logo, so it is a decision for the design owner rather than something to alter quietly in a stylesheet. Separately, a decorative numeral measures 1.75:1, in a section that is switched off and does not currently render.
Other known gaps
This site has not been tested with assistive technology by anyone who uses assistive technology, and it has not been audited by a third party — see “How this was assessed”.
How this was assessed
This is a self-assessment. It is based on a review of this site’s own design and behaviour specifications against WCAG 2.2 Level AA, and on contrast ratios computed by hand for each foreground and background pair the design actually renders; those ratios have not been cross-checked against an external tool. No third-party accessibility audit has been carried out, and no testing session with screen-reader or other assistive-technology users has been recorded. We would rather say that plainly than imply a level of verification that has not happened. The statement is reviewed whenever the site changes materially and whenever one of the exceptions above is resolved.
Feedback
If you meet a barrier on this site, tell us and we will fix it. Write to hello@confluxive.com with the address of the page, what you were trying to do, and the browser or assistive technology you were using. We aim to reply within within five working days. If a page is unusable for you, say so: we will send you what it contains in a form you can use while we correct it.
If we do not resolve it
If you are not satisfied with our response, you may be able to raise the matter with the body responsible for enforcing accessibility requirements in your jurisdiction. Ask us and we will tell you which body that is for your situation. Raising a complaint is not a reason for us to stop working on the problem, and we will keep you informed either way.