Accessibility standard
Designed with disabled people.
Interactive board demo. Example profiles, cases and dashboard figures are fictional. Actions stay in this browser session; nothing is sent.
Accessibility is a release requirement.
Every feature must work for people using different devices, assistive technologies and ways of understanding information.
Before production: an independent WCAG 2.2 AA audit plus testing with disabled people.Both are proposed launch gates. Neither has been completed for this prototype.
What every feature must support
WCAG 2.2 reference · This is a target standard, not a claim that every criterion currently passes.
Testing with disabled people
Recruit and pay participants with varied access needs. Test actual tasks: joining, finding a role, asking a question, applying, pausing and controlling privacy. Record barriers, fix them, then retest.
More than one format
Plan Easy Read, large print, audio, captions, transcripts and BSL where justified by the content and audience. Agree delivery and quality checks; never display a format as available before it exists.
Plain-language summary
You should be able to use Reach in the way that works for you. You can ask for help. You choose what you share. Before the service launches, disabled people will help test it and an independent specialist will check it.
Audio, Easy Read and BSL versions are planned, not supplied by this prototype.
Platform technology by InkfireProposed engineering, hosting and technology operations.
Platform status · demo Technical accessibility help