Accessibility

Bleu Financial is working to make this website usable by as many people as possible, including people who use screen readers, keyboard navigation, magnification, voice control, or who need reduced motion or higher contrast.

A good part of who this site is for is people working through an insurance question they find stressful, some of them for the first time and some of them later in life. Accessibility is not a compliance exercise for that audience — it is whether the site works at all.

We use WCAG 2.2 Level AA as our design target. On touch targets we aim higher than that: major interactive controls are built to roughly 44 by 44 pixels, which is the Level AAA figure rather than the AA minimum.

These are specific, and you can check every one of them on any page:

Structure and navigation

• Every page begins with a skip link to the main content, and uses proper landmark structure — header, navigation, main, footer.
• Headings follow a real hierarchy: one h1 per page, and sections nested under it in order rather than chosen for their size.
• The page language is declared, so a screen reader pronounces it correctly.
• Long documents like this one carry a labelled “on this page” navigation with working anchor links.

Controls

• Every interactive control is a real button, link or form element. There are no div elements pretending to be buttons anywhere on this site, so keyboard operation and screen-reader announcement come from the platform rather than from something we reimplemented.
• Focus is always visible, with a distinct ring that holds contrast against its background.
• Nothing on this site requires dragging, and nothing requires a mouse.
• Every input has a programmatically associated label. Where a visible label would duplicate the heading beside it, the label is given to assistive technology rather than removed.
• Major interactive controls — menu buttons, the theme toggle, primary actions — are built to a 44-pixel target.

Tables and errors

• Comparison tables keep their semantics when they stack on a phone, so a screen reader still announces each value with the option it belongs to instead of reading a flat list of numbers.
• Errors are described in plain language with a clear way to recover, and never signalled by colour alone.

Reading and motion

• Layouts are responsive and reflow down to a 320-pixel viewport without horizontal scrolling.
• Body text is set at a comfortable size and measure rather than shrunk to look tidy — including on the legal pages.
• Light and dark themes are both first-class, and the site follows your system setting unless you choose otherwise.
• Motion respects your system’s reduced-motion setting. Animation is decorative throughout; nothing depends on one to convey information.
• Nothing on this site auto-plays, flashes or moves without your input.

Accessible structure is enforced in the code rather than left to review: the skip link and the landmarks live in the single page shell every route renders inside, table semantics are set explicitly in the shared comparison component, and reduced-motion handling comes from one shared hook. A page cannot opt out of them by accident.

Before a release we check pages manually in a browser at 320, 390, 768 and 1280 pixels wide, in both light and dark themes, for layout breakage, horizontal overflow and console errors, and we operate the pages by keyboard.

That is a reasonable process, and it is not a substitute for testing with assistive technology — which is why the next section says what it says.

A full audit with assistive technology. Nobody has yet worked through this site with a screen reader — NVDA, JAWS or VoiceOver — or with voice control, and recorded the results.

Structural checks and width sweeps catch a category of problem. They do not tell you whether a page is genuinely usable by somebody who cannot see it, and we are not going to claim conformance on the strength of the ones we have. When that audit happens, this page will say what was tested, with what, by whom and when — and what it found.

We also know of no accessibility statement that is ever finished. If something this page claims is contradicted by your experience of the site, we would far rather hear it than have the claim stand.

This site loads no third-party scripts, embeds or widgets, so there is no external component whose accessibility is outside our control. We do link out to regulators, government agencies and industry bodies so you can check our sources. Those websites are operated by other organisations, and their accessibility is theirs rather than ours.

Please tell us. Barrier reports take priority over other work on this site, and a specific report is far more useful than a general one.

Email info@bleu.financial and tell us, as far as you can:

• the page — its address, or what it was called;
• what you were trying to do;
• what happened instead;
• what you were using — browser, device, and any assistive technology, if you know it.

We will acknowledge your report, tell you what we find, and if a fix is going to take time we will say so rather than going quiet. If the content you needed is behind the barrier, tell us and we will find another way to get it to you.

Accessibility questions and reports go to info@bleu.financial.