Is AI ready for low-vision rehabilitation?
A registered review found impressive navigation, recognition and accessibility prototypes across 19 studies. Yet only four studies measured a user-facing functional or usability outcome, and none used a validated quality-of-life or functional-vision instrument.
The short version
- What happened
- The prospectively registered review searched four databases to 27 February 2026, screened 2,420 unique records and included 19 peer-reviewed studies.
- Who it affects
- People with low vision should be shown how a tool fails in the environments where they will use it, not only its best accuracy figure.
- What remains unproven
- Only 19 heterogeneous studies and no quantitative meta-analysis
Keep in mind
Only 19 heterogeneous studies and no quantitative meta-analysis
Four user-facing functional or usability evaluations; 14 technical-only evaluations
No validated quality-of-life or functional-vision outcome in the included studies
Inconsistent dataset reporting and limited independent validation
Published academic studies may omit commercial deployments and negative unpublished results
Source analysis · 1 linked source. Primary analysed source date: 15 October 2026.
Read the full report · 6 min The evidence, methods, implications and limitations
The answer: technically promising, clinically unproven
AI systems can already identify objects, read signs, map routes and suggest low-vision aids under selected test conditions. A new systematic review found examples of sub-metre localization, high object-recognition accuracy and successful navigation tasks. Those figures show that engineers can build useful components. They do not establish that a person with low vision will be safer, more independent or better able to work and study after adopting a system. The review’s most important finding is the distance between benchmark performance and patient-important evidence.
Across the 19 included studies, only four incorporated a user-facing functional or usability outcome. Fourteen reported technical metrics without a matching functional or patient-reported outcome, and no study used a validated quality-of-life or functional-vision instrument. That makes the review a map of prototypes and early evaluations, not a clinical verdict. Clinicians and commissioners should resist translating an accuracy percentage into a promise of independence unless the underlying task, test environment, error costs and participant experience are clear.[1]
How the review was conducted
The researchers registered the protocol prospectively in PROSPERO as CRD420261324781 and followed PRISMA reporting guidance. They searched PubMed, Scopus, Web of Science and IEEE Xplore from inception to 27 February 2026. After removing duplicates, 2,420 records were screened; 34 full texts were assessed and 19 peer-reviewed empirical studies were included. Two reviewers independently screened records and extracted information. Eligible designs ranged from randomized and quasi-experimental work to cohort, usability, prototype and mixed-methods studies.
That breadth was appropriate for an emerging field but prevented a meta-analysis. Navigation, object detection, reading, device fitting and interface repair measure different things on incompatible scales. The authors therefore synthesized results narratively across six application domains. They did not complete a formal study-quality appraisal because the included papers mainly described system development and used dissimilar technical measures. The review itself was funded by the Else Kröner-Fresenius-Stiftung Foundation and the NKABOM project; the authors declared no commercial conflict.[1]
What worked—and under which conditions
Navigation was the largest domain, represented by eight studies. One UNav evaluation reported 100% task success and fewer wrong turns than unassisted navigation, but its server-dependent pipeline added about 3.62 seconds of round-trip delay. An augmented-reality sign-reading system improved route efficiency while users took roughly 129 seconds longer to complete tasks. Other systems performed strongly on sign detection, curbstone segmentation or indoor localization, yet their test conditions varied and some results came from held-out datasets rather than live journeys.
Recognition systems produced similarly mixed signals. Reported object or scene accuracy could be high for well-defined, high-contrast categories while falling for complex or low-contrast inputs. Construction-hazard detection reached 92% dynamic accuracy after temporal filtering, but motion blur, oblique viewpoints and camera limitations still caused failures. A chart-description system for educational videos achieved an F1 score of 86.1% for detection, yet generated captions could hallucinate and did not handle some complex charts. Those are meaningful engineering results with safety-critical exceptions.[1]
The real-world gap is not a footnote
Lighting degraded performance in five studies. Rain, fog, snow, clutter and changing illumination also challenged some systems. Cloud processing introduced dependence on connectivity; on-device processing reduced that dependence but brought battery, heat and computational constraints. Text-reading pipelines took 31 to 66 seconds in some configurations, while optical-character recognition could add three to four seconds per sign. A delayed or missing description may be inconvenient in a document and dangerous at a road crossing, so average accuracy is not enough.
Representation is another uncertainty. Dataset sizes were inconsistently reported, and few studies clearly documented evaluation on a truly independent dataset. Some systems were tested by sighted people in simulated low-vision conditions or evaluated through expert ratings rather than everyday use by the intended population. The review excluded company deployments and unpublished work, so it may miss operational products; conversely, academic publication does not guarantee that a prototype is available, affordable, maintainable or compatible with a person’s preferred rehabilitation plan.[1]
What clinicians, developers and users can do now
Low-vision services can treat AI tools as candidates for individualized trials rather than replacements for established rehabilitation. A useful assessment should specify the person’s goals, residual vision, mobility context, device access and tolerance for audio, visual or haptic feedback. Staff should test the tool in the environments where it will be used, document failure modes and retain non-AI alternatives. Procurement questions should cover offline operation, update policy, privacy, battery life, incident reporting and what happens when the model is uncertain.
Developers should involve people with low vision from problem definition through evaluation. Safety-critical functions need on-device fallbacks, clear confidence cues and an easy way to stop or override guidance. Performance should be disaggregated by lighting, weather, device, condition and user group. Affordability and training matter as much as model architecture: a system that assumes a recent phone, continuous data connection or precise camera alignment can widen access gaps even when its laboratory score is excellent.[1]
What would change the assessment
Confidence would rise with prospective comparative studies that recruit diverse people with low vision and measure real tasks over months, not minutes. Common outcomes should include falls or near misses, route completion, reading performance, fatigue, device abandonment, confidence, participation and validated functional-vision and quality-of-life scores. Trials should report adverse events, false reassurance and the burden of checking incorrect outputs. Independent replication outside the developers’ own dataset and site is essential.
Until that evidence arrives, the most defensible conclusion is narrower than the strongest performance figures. AI can make parts of low-vision support more adaptive and context-aware, and several prototypes deserve careful field testing. The review does not show that AI rehabilitation improves health, independence or quality of life at population scale. People choosing a tool should receive both the technical promise and the practical uncertainty, with clinicians and users—not benchmark leaderboards—deciding whether the trade-off is acceptable.[1]