Accessibility

Where we stand

We want Flourish to work for everybody, including people using a screen reader, a keyboard, magnification or a phone with the text turned up. We are not there yet, and this page says so plainly rather than claiming a standard we have not measured against.

We have not had an independent accessibility audit, and we have not tested the whole product against the Web Content Accessibility Guidelines. We are working towards WCAG 2.2 level AA. Until an audit has happened, treat anything on this page as our own assessment.

What we have built

• Text size can be set to default, large or extra large in Settings, under Accessibility.
• A higher contrast mode, a bold text mode and a wider line spacing mode are in the same place.
• Reduce motion turns off animation for people who find it uncomfortable.
• Light and dark themes, which follow your device setting unless you choose one.
• The interface is available in more than forty languages.
• Pages are built from standard HTML elements, so headings, lists, tables and links are announced properly, and interactive parts come from components with keyboard support and labels built in.
• The public pages, including this one, work without JavaScript running.

What we know is not good enough

These are the parts we would expect a disabled user to struggle with today.

• Maps and charts. The map of nearby work and the labour market charts are visual, and there is no equivalent table or text description for a screen reader user.
• Moss. Answers stream in a few words at a time, and a screen reader may read a partial answer or repeat itself. The thinking panel and quick replies have not been tested with assistive technology.
• Long forms and onboarding. Focus order and error announcements have not been checked end to end.
• Colour contrast. It has not been measured across every component or against the high contrast mode.
• Third party components. Sign-in comes from Clerk, payment from Stripe and maps from Google. We do not control their accessibility, and we have not audited them.
• Documents you upload. A PDF you add is stored as you sent it, and we do not make it accessible.
• Mobile screen readers. We have done no systematic testing with VoiceOver or TalkBack.

What we are doing about it

• Fixing what people report to us, which is currently how most problems reach us.
• Building new features from components that already carry labels and keyboard support, rather than hand-rolled ones.
• Planning a first independent audit.

Tell us when something blocks you

Email accessibility@flourish.so and describe what you were trying to do, what happened, and what you were using, such as a browser and a screen reader. We aim to reply within five working days.

If you need something from Flourish in another format while we fix the underlying problem, ask and we will find a way to get it to you.

If we do not put it right

The Equality Act 2010 requires us to make reasonable adjustments. If you are not happy with how we responded, the Equality Advisory and Support Service can advise you. They are at equalityadvisoryservice.com, and on 0808 800 0082.

About this statement

This statement was written by the Flourish team from our own review of the product, not from a formal test. It is reviewed when the product changes materially, and at least once a year.