Accessibility statement

The standard we work to

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, on every page of the site. We build to it from the first line of code rather than fixing things afterwards.

This statement describes a target and the work behind it. It is not a claim that every page already conforms: the site is still being built and has not yet had an independent audit.

What we do

• Real buttons, links, headings, lists and form labels, so assistive technology can describe every control.
• Everything can be reached and used with a keyboard alone, with a visible focus ring in both themes and no focus traps.
• A “Skip to main content” link and a unique page title on every page.
• Text contrast of at least 4.5:1 and form-field borders of at least 3:1, in both the light and the dark theme.
• Buttons and links at least 44 pixels tall, so they are easy to hit on a touch screen.
• Form errors are written in words, tied to the field they belong to, and announced to screen readers.
• Nothing relies on colour alone: states such as password strength, verification and selection are also given as text.
• Pages reflow down to a 320-pixel-wide screen and stay usable at 200% zoom.
• We honour your device's reduced-motion setting, and you can choose a light or dark theme.
• Members are prompted to describe their photos, and every photo has a default text alternative.

No accessibility overlays

We do not use accessibility overlay widgets or toolbars. They tend to get in the way of the assistive technology people already rely on. Accessibility is built into the site itself.

How we test

• Automated checks with axe-core as part of our build.
• Manual keyboard-only checks of each screen.
• Screen-reader testing with VoiceOver and NVDA.
• An independent audit is planned before launch and once a year after that. We will publish the date of the latest audit here.

Known limitations

The site is in pre-launch development and has not been independently audited yet, so there may be barriers we have not found. We will list known issues here, with what we are doing about each one, as soon as testing finds them.

• Text alternatives for member photos are written by members, so their quality varies.

Tell us about a barrier

If something on TrueFLR is hard or impossible for you to use, or you need information from the site in another format, email accessibility@trueflr.com.

It helps if you tell us the page you were on, what you were trying to do, and the browser and assistive technology you use — but none of that is required. A person reads every message.