Evaluating Luzia for Messaging-Based AI Accessibility
On this page
Quick answer
A messaging-based assistant may reduce installation and interface friction for people already using the supported channel. It is not automatically accessible to every disabled person, language community, device, or network condition.
The earlier version of this page invented three named user stories, asserted device and network support, and used unsupported regional statistics and comparison tables. Those claims have been removed.
Verify current access
Start at Luzia’s official product and record:
- supported messaging channels and countries;
- whether a separate account or app is required;
- supported languages and voice inputs;
- file, image, and message limits;
- cost and rate limits;
- privacy, retention, deletion, and human-review terms;
- support and incident-reporting routes.
Do not assume that an integration once available on WhatsApp or Telegram is still active in every region.
Test on representative devices
Use the oldest supported phone and operating system in the target group. Test on constrained storage, low memory, slow or intermittent networks, battery-saving mode, and limited data plans.
Record successful task completion, response time, retries, data transferred, app crashes, lost context, and whether a failed request can be resumed. A service running inside a familiar app may still depend on network and device behavior.
Evaluate assistive technology
Include users of:
- screen readers;
- voice control;
- switch access;
- magnification and large text;
- captions or transcripts;
- reduced motion;
- high contrast.
Check focus order, accessible names, message reading order, language changes, audio alternatives, error messages, and whether generated images receive useful descriptions. Messaging-platform accessibility and assistant-output accessibility are separate layers.
Use WCAG 2.2 as a reference, then test with actual users and devices.
Review voice and language
For each target language and regional variant, test text, voice input, transcription, code-switching, formality, and ambiguous phrasing. Use native reviewers. Keep sensitive medical, legal, or financial content out of the test unless qualified oversight and approved data handling are in place.
A total language count does not establish acceptable quality for one language or disability context.
Examine privacy and safety
Messaging assistants may process content through the messaging platform, the assistant provider, model providers, and other subprocessors. Map who receives:
- message text;
- voice recordings and transcripts;
- images and files;
- contact and device information;
- location or metadata;
- feedback and support records.
Check retention, model-training choices, account deletion, export, age requirements, and escalation. Do not use a chatbot to check medication interactions or make high-stakes decisions without an authoritative source and qualified professional.
Run task-based user research
Recruit participants who represent the intended access needs and compensate them appropriately. Give realistic tasks without coaching, then record completion, errors, assistance required, confidence, and qualitative feedback.
Do not turn fictional personas into evidence. Publish participant count, recruitment, devices, tasks, limitations, and consent process if results are reported.
Decision
Adopt Luzia for a target group only when the current product passes that group’s device, assistive-technology, language, privacy, reliability, and support requirements. Keep an accessible alternative channel for failures or unsupported needs.