MyaGuide Reception — Accessibility statement
Document: Accessibility statement · Product: MyaGuide Reception · Version 1.1 · International edition: 2 October 2026
1 Our commitment
1.1 MyaGuide Reception is used by residents of shelter and reception locations, including people with limited digital skills, limited knowledge of the language of the country where they are staying, or a disability. We want the Service to be usable by as many people as possible. Accessibility is a product requirement, not a finishing touch.
1.2 The Service is provided to public authorities and other organisations. Their legal obligations for digital accessibility therefore determine how the Service is built and tested.
1.3 This statement describes our standard, the investigation status, the known limitations, and how you can get help or report a problem.
2 Multilingualism as accessibility
For many residents, language is the main barrier. The Service lets you use the Guide and Mya in the available languages and make a language request if your language is missing. We treat expanding languages as an accessibility priority, alongside the technical accessibility below.
3 Standard and investigation status
3.1 The Service is delivered in accordance with EN 301 549 / WCAG 2.1 level AA, an accessibility standard used for ICT products and services. WCAG 2.2 level AA is our development target.
3.2 On 6 September 2026, a technical accessibility assessment was carried out in the test environment on the Guide for residents, the Mya chat, language selection, resident forms, and a sample of the logged-in Management Environment. This combined automated checks with inspection of the page structure, names and roles for assistive technology, keyboard operation, focus, contrast, narrow screens, text enlargement, and content in two languages, including Arabic. Automated checks alone are not sufficient to establish conformity.
3.3 Investigation status: internal technical partial assessment of 6 September 2026, carried out for MyaGuide with support from Codex. Shortcomings were identified and technical improvements were specifically checked in the test environment. This is not an independent conformity assessment and it has not yet been established that the full Service complies with WCAG 2.2 level AA. Actual screen reader tests, additional browser and device checks, and full management processes still need to be completed before the first deployment at an organisation. Request the assessment report of 6 September 2026.
3.4 The organisation deploying the Service publishes its own statutory accessibility statement with status and feedback mechanism. MyaGuide provides the assessment report and the necessary information for that purpose.
4 Known limitations
4.1 The technical partial assessment identified the points for attention below. The assessment report contains the individual findings and retest results. The remaining checks will be carried out before completion of the accessibility assessment for the first deployment; the implementation date for this has not yet been determined.
| Function | Effect on users | Measure and remaining check | Schedule |
|---|---|---|---|
| Guide, demo and login screen | Some text and focus indicators were insufficiently visible | Contrast and focus display have been adjusted and specifically measured in the test environment; additional states and devices remain part of the assessment | Before completion of the assessment for the first deployment |
| Mobile Mya chat and dialog windows | Focus could be lost after closing; long answers require checking for full accessibility | Focus recovery and dialog operation have been improved; long answers and operation with mobile assistive technology are checked additionally | Before completion of the assessment for the first deployment |
| Multilingual content and management tasks | Incorrect language or role labels can interfere with pronunciation and recognition of actions | Language and role labels are specifically checked; actual screen reader operation and the full multilingual page set remain open | Before completion of the assessment for the first deployment |
| Forms and Management Environment | Input purposes, error explanations, and full operation paths must be reliable for all users | Form semantics and error focus have been improved; full management, authentication, and financial processes are still being additionally assessed | Before completion of the assessment for the first deployment |
4.2 Independently of that investigation, the following limitations are known:
| Limitation | Effect | Measure |
|---|---|---|
| Immediate physical handover of a shared device cannot be detected | A next user may see a conversation before a clearing event | End the conversation before handover; automatic clearing follows 2 minutes of inactivity, with a warning after 90 seconds and a button to continue |
| Translated content is automatically translated from source information managed by the organisation | Translations may be inaccurate | Check important information with a staff member |
| Mya offers Chat and Talk | Talk uses the microphone and audio; browser and device support may vary | Use Chat when speaking does not work or is not suitable; use device/browser assistive technology or ask staff for help |
5 Non-digital and guided access
5.1 The Service is an additional digital information channel and not a replacement for personal support. Which alternatives are available at a Location, such as printed information, personal help or a staffed information point, is determined by the organisation.
5.2 The Service is not presented by MyaGuide or by organisations as a replacement for the personal support that a Location offers.
6 Feedback and help
If you experience an accessibility problem or would like to receive information in another form, please contact the staff of your Location or MyaGuide using the details in article 8. We confirm accessibility reports within five working days and include them in the remediation plan.
7 Periodic review
We assess the accessibility of the Service and this statement at least annually and after every material change to the Service, and update this statement accordingly.
8 Contact
Van Riemsdijk & Karman S.L. (MyaGuide)
Jávea, Spain
reception@myaguide.com
9 Version history
| Version | Date | Changes |
|---|---|---|
| 1.0 | 6 September 2026 | First final version. Standard EN 301 549 / WCAG 2.1 AA, development target WCAG 2.2 AA. Replaces all earlier drafts |