Assistive Device Claims Accessibility: Where Marketing Must Stop

What “Assistive” Means in Practice
The term *assistive* applies only to features verified during production QC and aligned with the declared conformity scope. For the Vox One AI Glasses, this includes real-time speech-to-text captioning, object distance estimation via stereo depth mapping, and adjustable audio gain — all tested at IPQC and FQC using AQL 2.5 for major defects. It does not include optical correction, contrast sensitivity calibration, or integration with certified low-vision assessment tools. Any claim implying equivalence to Class I medical devices (e.g., “vision aid”, “hearing support system”) is prohibited under factory policy and would invalidate CE RED coverage.The Boundary Between Wellness and Clinical Use
Wellness guidance — such as posture alerts from the H3 health smartwatch or ambient sound labelling from the Vox One — remains outside medical device regulation because it carries no diagnostic intent and makes no therapeutic promise. Translation output is explicitly labelled a *reference translation*, never certified or legally binding. This distinction is enforced at firmware level: no model ships with health algorithm outputs that could be interpreted as clinical indicators — a safeguard confirmed in the how we build and test process.Where Certification Ends and Responsibility Begins
Regulatory documentation is tied strictly to hardware revision and test scope. CE RED covers radio, EMC and safety for the Vox One; UKCA is available on request but not pre-booked; FCC Part 15 B/C applies only to unmodified RF configurations. No model holds ISO 13485, IEC 62304 or MDR Annex II certification. Importers assuming responsibility for EAA, WEEE, BattG or DEEE/Triman obligations must initiate those assessments independently — the factory supplies only what is listed in the FACTS block, nothing more.Accessibility Statements: Precision Over Promise
An accessibility statement must describe what the user can do, not what condition it addresses. Acceptable phrasing includes:- Voice-controlled navigation without touch input
- Text-to-speech output compatible with screen reader APIs
- Adjustable font size and colour inversion in the companion app
- Tactile markers on physical controls (verified per EN 1811 for skin-contact parts)
- Audio cues with variable pitch and duration, tested across hearing thresholds (500–4000 Hz)
What This Process Cannot Do
This process does not validate claims against the EU Accessibility Act (EAA), nor does it generate EN 301 549 conformance reports. No WingPhoenix model has undergone formal usability testing with persons with disabilities per CEN/CENELEC Guide 6 or ISO/IEC GUIDE 71. Importers requiring EAA alignment must engage a third-party assessor before placing orders — the factory cannot supply test evidence beyond its published scope. To proceed, review the buyer resources, consult the CE RED document checklist, and confirm firmware customisation needs via firmware and app white-label.| Claim Type | Permitted? | Basis Required | Document Supplied? |
|---|---|---|---|
| “Voice-narrated interface” | Yes | FQC audio verification log | Yes, with CE RED package |
| “Designed for low-vision users” | No | Clinical evaluation + notified body | No — invalidates CE RED |
| “Complies with EN 301 549” | No | Harmonised standard test report | No — not in current scope |
| “Battery UN38.3 certified” | Yes | Test summary + SDS per order | Yes, shipped with goods |
| “Meets Toy Safety Directive” | Conditional | Age grading on packaging + EN 71-1/-2/-3 booking | Yes, per build |
| “Supports emergency response” | No | Class IIa MDR certification | No — prohibited for all models |
| “Google Play certified” | No | GMS licence agreement | No — GMS is not licensed by default |
Contact the sales team to align your accessibility statement with factory test scope, confirm MOQs for configured samples — including the K1 AI companion robot or full product catalogue — and schedule a review of your intended claims against the Journal of WingPhoenix AI guidance.
Questions buyers ask
What wording turns an AI glasses product into a regulated medical device?
Claiming it diagnoses, treats, mitigates, monitors or prevents disease — or implying clinical validation for conditions like low vision, hearing loss or cognitive impairment — triggers MDR or IVDR classification. The Vox One AI Glasses are designed and documented solely as consumer electronics under EN 62368-1.
How do I verify that a supplier’s “accessibility statement” is legally defensible?
Cross-check every claim against the documents supplied per hardware revision: CE RED (EN 300 328, EN 301 489, EN 62368-1), RoHS 3, REACH SVHC screening and, where applicable, EN 1811 nickel release. No claim may exceed the test scope booked with an accredited laboratory — and no certificate exists for wellness output, translation reference or companion functionality.
Why did our distributor fail the sample audit when the box said “designed for users with visual impairment”?
That phrase crosses into medical device territory unless substantiated by clinical evaluation and notified body involvement. The factory policy permits only functional descriptions — e.g., “voice-narrated interface”, “high-contrast display mode”, “tactile feedback controls” — all verified at FQC and documented in the CE RED document checklist.
What claim do most suppliers avoid answering directly?
Whether the device has been assessed against the EU Accessibility Act (EAA) Directive (EU) 2019/882. WingPhoenix does not assert EAA conformance; it is not part of the factory’s current test scope. Conformance requires harmonised standards (e.g., EN 301 549 v3.2.1), which are not yet booked for any model. Importers must commission this separately if required for public procurement.
Related: more on ai glasses & accessibility · buyer guides · customisation tiers