What you will learn
- How disability services are organised: health, education, employment, housing, and equipment
- What an accessible directory needs: more than a list with a filter
- How eligibility guidance works without giving legal or medical advice
- What application support looks like: advocates, documents, and timelines
- How navigation help is coordinated across agencies
What the project is
Disability support spans many systems: healthcare, education, employment support, housing adaptations, assistive equipment, transport, and benefits, each with its own eligibility rules, application routes, and waiting lists. A person or family navigating them alone faces a maze, and the maze itself becomes a barrier to the support they are entitled to. A navigation platform holds an accessible directory of services, eligibility guidance in plain language, application support tools, and advocate coordination, so a navigator or the person themselves can build a path through the systems in order, rather than discovering them by accident.
Accessibility is the product, not a feature. A navigation platform that is itself inaccessible, through poor screen reader support, complex language, or a design that assumes fine motor control, fails its users before they reach a single service. The platform must meet accessibility standards, support multiple formats, and offer human help, because navigation is often a conversation, not a search.
Core features
Accessibility of the platform itself is the feature. A disability navigation tool that disabled people cannot use is a contradiction, not a product.
- Accessible service directory with health, education, employment, housing, equipment, and benefits services, searchable by need and location.
- Plain-language eligibility guidance per service, with the key rule and the next step, and clear limits on what the guidance is not.
- Application support: document checklists, timeline tracking, and deadline reminders for applications in progress.
- Navigator coordination: advocates and navigators assigned to clients, with shared notes and task tracking.
- Accessible design: screen reader support, keyboard navigation, plain language, and multiple formats, tested with disabled users.
- Human help paths: phone, chat, and in-person options alongside the digital directory, because navigation is often a conversation.
- Gap reporting: needs with no matching service, reported in aggregate, to guide service development.
How it is built
Build the directory and its accessibility with disabled users and navigators, before adding application tools. A navigation platform designed without its users will navigate them into barriers it cannot see.
- Service study: inventory services across health, education, employment, housing, equipment, and benefits, and learn how navigators currently guide people through them.
- Directory and accessibility build: accessible directory, plain-language guidance, and human help paths, tested with disabled users.
- Application support: checklists, timelines, and deadline reminders, tested with navigators on real applications.
- Navigator coordination: shared notes, tasks, and client tracking, with consent-based sharing.
- Gap loop: aggregate gap reporting feeding service planning, so the platform improves the system, not just navigates it.
Tech considerations
The technical priorities are accessibility compliance, plain-language content management, and consent-based navigator sharing.
- Accessibility-tested interfaces meeting recognised standards, with screen reader, keyboard, and magnification support verified by testing with disabled users.
- Content management for service listings and guidance, so navigators can update details without developer help.
- Application tracking with document checklists and deadline reminders, linked to the navigator's task list.
- Consent-based sharing between clients, navigators, and agencies, with audit trails.
- Aggregate gap reporting that protects individual privacy while showing where services are missing.
Challenges to plan for
Disability navigation fails on inaccessibility, stale listings, and advice overreach. Each failure adds a barrier to people already facing many.
- Platform inaccessibility: a navigation tool that fails accessibility testing has added a barrier rather than removing one.
- Stale services: services close, change criteria, and move, and a directory nobody maintains misdirects vulnerable users.
- Advice overreach: eligibility guidance that reads as legal or medical advice creates liability and misleads users about their rights.
- Navigator capacity: a platform that generates demand for navigators without funding them creates waiting lists for help navigating waiting lists.
Who it is for, and honest limits
This fits disability organisations, local governments, health and education agencies, and navigator programs. It fits less well as a standalone directory without human help, because navigation for complex needs is usually a conversation, and a directory alone leaves users to navigate the conversation by themselves.
It does not decide eligibility, provide medical advice, or replace advocates. It makes services findable, guidance plain, and navigation supported. If a service does not exist, the platform should report the gap honestly, because that gap is itself important information.
Frequently asked questions
Is the guidance legal or medical advice?
No. Eligibility guidance explains program rules in plain language and states its limits. Complex cases should be referred to an adviser, advocate, or professional, and the platform should make that referral easy.
How accessible is the platform?
It should meet recognised accessibility standards and be tested with disabled users, including screen reader users. Accessibility is a launch requirement, not a post-launch improvement, for a disability service.
Can someone get human help through it?
Yes, through navigator contact options: phone, chat, or in-person, alongside the digital directory. Human help should be prominent, not buried, because many users will need it.
How are services kept current?
By service providers updating their own listings, with verification prompts and freshness timestamps. A listing without a verification date should be treated as suspect by users and by the system.
What if no service matches a need?
The gap is recorded in aggregate for service planning, and the user is offered the nearest alternatives and navigator help. An empty result without a next step is a failure for a person seeking support.