Skip to main content
Log inGet started

Accessibility

What this product has been checked against, what works, what does not work yet and what is being done about it. Every statement below carries the date it was last looked at.

Read on 2026-10-14. The oldest review on this page is from 2026-08-25.

Skip straight to reporting a barrier

What has been assessed

Standard: WCAG 2.2, level AA. This is the standard being worked to, not a claim to have reached it. What has not been reached is listed under known gaps below.

Last assessed: 2026-08-25, by engineering, against the per-journey verifiers in .journeycode/ranger/tools/.

What was in scope: The signed-out public pages and the member day, readiness, goals and settings screens. The employer, clinician and platform-admin consoles were NOT in scope.

How it was checked: Internal review by the engineering team: keyboard-only walkthroughs, automated contrast and landmark checks in the build, and per-journey browser verification. No independent audit and no formal screen-reader user testing.

Known gaps

What does not conform yet, who it affects, and what is intended about it.

What you can change in the product

Last reviewed 2026-08-25

Which display settings exist for motion, contrast and text size, and where are they?

Settings, then Display, holds the controls that change how the product looks: a light or dark theme, an accent colour, and a switch that reduces motion so animated transitions and count-ups are not played.

Reduced motion is also honoured automatically when your operating system or browser already asks for it, so you do not have to set it twice.

Text size follows your browser and operating system settings rather than a control inside the product. Pages are built to stay readable and complete when text is enlarged to 200 percent.

Reviewed by engineering, against the display preferences panel (J224).

Using it without a mouse

Last reviewed 2026-08-25

Which parts of the product can be operated by keyboard alone, and which cannot yet?

Every page is built from standard links, buttons and form controls, so the whole of it can be reached and operated with a keyboard alone, in the order the page reads.

Where a panel opens over the page, focus moves into it and the Escape key closes it and returns focus to what opened it.

This was checked by walking each journey with a keyboard only, on the screens named in the assessment scope above. Anything found that did not work is listed as a known gap below.

Reviewed by engineering, against the per-journey keyboard walkthroughs in .journeycode/ranger/tools/.

Using it with a screen reader

Last reviewed 2026-08-25

What is announced, in what order, and where does that break down today?

Pages are marked up with headings, landmarks and labelled controls, so a screen reader announces a page structure rather than a wall of text, and every control has a name that says what it does.

Numbers that carry meaning are not left to colour alone: a readiness band, a confidence level and a trend direction are each stated in words beside the colour that shows them.

This has been verified structurally, in the build and in the browser. It has NOT been verified by a person who uses a screen reader daily, and that difference matters: structural correctness is not the same as being usable. Independent testing with screen-reader users is an open commitment and is listed as a known gap below.

Reviewed by engineering, against the accessible-name and landmark checks in .journeycode/ranger/tools/.

What has actually been tested

Which assistive technologies and browsers was this checked against, and which were not?

Not stated. Thriverence has no checked answer to this yet, and does not make a claim it cannot show you the record for.

Reporting a barrier

Last reviewed 2026-08-25

Where does a report go, who answers it, and how long does that take?

The form on this page opens a tracked ticket in the same queue that answers every other support request, and hands you a reference straight away.

A report is answered within five working days by the engineering team. If you leave an address, the reply goes there. If you do not, the report is still logged and worked on, and the reference is your own way of following it up.

You do not need an account to report a barrier, and you are not asked to prove you have one.

Reviewed by engineering, against the support ledger (J191) this form writes into.

If you already have an account, the theme is at /settings/preferences (Settings, then Preferences) and in the Display panel behind the gear at the top of Today, which also holds the accent colour and the switch that stops the moving background.

Report a barrier

If something here stopped you, tell us. This opens a tracked ticket and gives you a reference straight away. You do not need an account, and reports are answered within 5 working days.

The page or the part of it, in your own words. A link is fine too.

What you were trying to do and what stopped you. As much or as little as you like.

A screen reader, a browser, magnification, voice control, a keyboard alone. It helps us reproduce what you saw.

Only so we can reply. Leave it blank and the report is still logged and worked on, but nobody can write back to you.