Therapy withVR
Accessibility Statement
Version | 1.0.0 |
Published | March 2026 |
Next review | March 2027 |
Company | withVR BV |
Registered address | Jozef Hebbelynckstraat 21, Merelbeke 9820, Belgium |
VAT / company number | BE-0790.909.294 |
Governing law | Belgian law |
Jurisdiction | Courts of Ghent, Belgium |
Contact | hello@withvr.app | legal@withvr.app |
This Accessibility Statement applies to the Therapy withVR platform, including the Web App and the VR App on Meta Quest headsets. It explains the platform's current accessibility status, known limitations, and withVR BV's commitments to improving accessibility over time.
withVR BV is committed to making Therapy withVR as accessible as reasonably possible. We recognize that our platform is used by professionals working with people with diverse communication needs, and that accessibility matters to our user community. This statement is honest about where we are today and transparent about our plans.
1. This website (withvr.app)
This section covers the marketing website at withvr.app - the pages you are reading now. The Therapy withVR software product (Web App and VR App) is covered separately from Section 2 onwards.
Area | Status | Notes |
Standard targeted | WCAG 2.2 Level AA | Self-assessment completed April 2026. A formal commissioned audit is deferred due to budget. The self-assessment is the current baseline and will be reviewed annually. |
Lighthouse Accessibility score | 100 / 100 | Desktop and mobile. Measured via Lighthouse 12.8.2 on homepage, About, Evidence Hub, Evidence study page, Why withVR, FAQ, Blog index, and Resources. Reports archived in the repository. |
Automated scan (pa11y + axe-core WCAG 2.2 AA) | All hard failures resolved | ARIA misuse, link-in-text-block distinction, landmark structure, and modal semantics have all been addressed. Remaining warnings are color-contrast items flagged needsFurtherReview by axe - all computed ratios on the core palette pass AA (body text 6.09:1, meta text 4.52:1, headings 18.4:1, links 7.4:1). |
Structural checks | All 8 priority pages pass | Skip-to-content link, main/nav/footer landmarks, lang attribute, viewport meta, heading hierarchy, alt-text coverage, and button-name presence verified across homepage, Evidence Hub, Evidence study, About, Why withVR, FAQ, Blog index, and Resources. |
Keyboard navigation | Supported | All interactive elements reachable via keyboard. Focus indicators visible. Skip-to-content link is the first focusable element. The cookie consent banner, language switcher, and brochure modal are all keyboard-operable; Escape closes the modal. |
Screen reader compatibility | Supported (automated) | Semantic HTML, ARIA roles, and landmark structure in place. Formal screen-reader walkthrough (NVDA / VoiceOver / JAWS) has not yet been performed - listed as a known limitation. |
Languages available | 11 languages | English, Dutch, French, German, Norwegian, Italian, Czech, Spanish, Portuguese, Greek, Arabic, Turkish. Each locale has the correct |
Motion and animation | Respects user preference | Animations honor |
Text sizing and zoom | Supported | Text reflows at 200% browser zoom without loss of content or functionality. Relative units (rem/em) used throughout. |
Known website limitations: formal screen-reader walkthrough pending; formal commissioned WCAG 2.2 AA audit deferred until funding permits. See Section 6 (Known Limitations) for more.
2. Platform Overview
Therapy withVR consists of two separate applications with different accessibility considerations:
Component | Description |
Web App | The main control interface used by the supervising professional. Runs in any modern desktop web browser on Windows or macOS. The professional configures sessions, manages profiles, and controls the VR environment from this interface. |
VR App (Meta Quest) | The immersive environment experienced by the person inside VR. Runs on Meta Quest 2, 3, and Pro headsets. This application is experienced by the individual the professional is working with, not the professional themselves. |
Important context: Therapy withVR is a professional tool operated by a supervising professional. The Web App is the primary interface for the professional user. The VR App is the environment experienced by their client, student, or research participant. Accessibility considerations therefore apply differently to each component and each user role. |
3. Applicable Standards and Legal Framework
Standard / legislation | Applicability to Therapy withVR |
WCAG 2.2 Level AA (Web Content Accessibility Guidelines) | Target standard for the Web App. A formal independent audit has not yet been completed. withVR BV is working toward WCAG 2.2 AA conformance and will publish results of any formal audit. |
European Accessibility Act (EAA) - EU Directive 2019/882, enforceable from June 2025 | The EAA applies to digital services offered to consumers in the EU. Therapy withVR is primarily a professional platform. The applicability of the EAA to B2B professional tools is being monitored as Belgian implementing guidance develops. withVR BV’s accessibility improvements target the underlying EN 301 549 / WCAG 2.2 AA standard regardless of EAA applicability. |
EN 301 549 (European standard for ICT accessibility) | The harmonized EU standard for digital accessibility. Referenced as the technical standard for EAA compliance. withVR BV's accessibility improvements target EN 301 549 / WCAG 2.2 AA alignment. |
Section 508 (US - Rehabilitation Act) | Applies to US federal agencies and federally funded programs. Therapy withVR is not a US federal system, but institutional users in US federally funded settings may have Section 508 requirements. withVR BV's WCAG 2.2 AA work addresses the underlying technical requirements. |
VPAT / ACR (Voluntary Product Accessibility Template / Accessibility Conformance Report) | A VPAT v2.5 (International Edition) was completed in March 2026 covering WCAG 2.0/2.1/2.2, Section 508, and EN 301 549 for the current platform version (v4.0.0). The VPAT is available as a downloadable PDF. |
4. Web App Accessibility
The Web App is the primary interface for professional users. The following table describes the current accessibility status of key Web App features:
Feature / area | Status | Notes |
Keyboard navigation | Partial | Interface elements outside the VR preview (navigation, buttons, form fields, settings, AI features) can be operated by keyboard. The VR preview is rendered as a Unity WebGL canvas - avatar selection, position placement, and the emotion color picker within the preview require mouse interaction and are not keyboard accessible. This is a limitation of the WebGL rendering. |
Screen reader compatibility | Partial | The Web App has not been formally tested with screen readers. Basic semantic HTML structure is in place. A formal screen reader audit is planned. |
Color contrast | Partial | The interface uses a blue and white color scheme. Contrast ratios have not been formally audited against WCAG 2.2 AA requirements (4.5:1 for normal text, 3:1 for large text). Audit is planned. |
Text sizing and zoom | Not supported | Browser zoom does not currently affect the Web App interface. The application uses fixed scaling that does not respond to browser zoom controls. Users cannot resize text up to 200% without the interface failing to scale. This is a known limitation. |
Focus indicators | Partial | Visible focus indicators are present for most interactive elements. Some elements may have insufficient focus visibility. Under review. |
Language | Partial | The Web App interface is available in 59 languages with 52 avatar language-region combinations. The HTML lang attribute is set to the default language but does not dynamically update when the user changes language through Settings. This is a known limitation planned for a future update. |
Form labels and error messages | Supported | Form fields include labels. All form errors are identified in text, including login errors, account creation errors, and profile creation errors. Error messages appear as visible text, not only as color changes. |
HTTPS / secure connection | Supported | All data transmitted via HTTPS. Browser security indicators confirm encrypted connection. |
Cookie consent banner | Not yet assessed | The cookie consent banner on withvr.app has not been formally tested for keyboard accessibility or screen reader compatibility. Accessibility assessment is planned as part of the WCAG 2.2 AA audit. |
5. VR App Accessibility
The VR App runs on Meta Quest headsets and presents inherent accessibility constraints related to the hardware and the nature of virtual reality. This section describes those constraints honestly and explains what is possible within them.
5.1 Hardware requirements and physical constraints
The VR App requires a Meta Quest 2, 3, or Pro headset. This creates inherent physical accessibility constraints:
- Users must be able to wear a VR headset and hold or use the Meta Quest controllers, or have a carer or professional who can assist with this
- The VR experience involves a head-mounted display, which may not be suitable for users with certain vestibular conditions, photosensitivity, epilepsy or a history of seizures, or physical limitations that prevent headset use. Supervising professionals should assess suitability for VR-based practice on an individual basis before use. If a person is known to have photosensitive epilepsy or a history of seizures, the VR App should not be used. Neither the VR App nor the Web App contain flashing content.
- Full hand tracking is supported as an alternative to controllers for all VR interactions. Users can complete a full session - including sign in, navigating the Waiting Room, interacting with art, and exiting - using only hand tracking and no controllers. Controllers remain available as an alternative input method
- The minimum physical space required is that needed to stand or sit with the headset on - Stationary boundary mode allows use from a fixed position
Note: The VR App is experienced by the client, student, or participant inside VR - not by the supervising professional. The supervising professional uses only the Web App. Physical accessibility of the VR experience is therefore a consideration for the individual’s suitability for VR-based practice, which is a clinical decision for the supervising professional. The platform has been used with individuals with Fragile X and with individuals across a range of cognitive profiles. No formal cognitive accessibility audit has been conducted. |
5.2 Visual and audio accessibility inside VR
Feature | Current status |
Avatar voices | All avatar speech is AI-synthesized using Google Text-to-Speech. The voices are clear synthetic voices. No captioning of avatar speech is currently available inside VR. This is a known limitation. |
Visual environment | VR environments are designed for visual immersion. No audio description of the visual environment is currently provided. This is a known limitation. |
Text size inside VR | Most text elements displayed inside VR are at fixed sizes determined by the virtual environment design. However, text displayed on the in-VR laptop (used for prompts and reading tasks) automatically scales to fit the available space: shorter text appears larger, and longer text appears smaller. Users cannot manually adjust text size inside VR. |
Subtitles / captions | Captions for avatar speech are not currently available inside VR. This is a planned improvement. |
Color and contrast inside VR | VR environments use natural-looking scene lighting. No high-contrast mode is available inside VR. This is a known limitation. |
Meta Quest platform accessibility | Meta Quest headsets include platform-level accessibility features (font scaling, color correction, etc.) managed by Meta. These are not controlled by withVR BV. See meta.com/accessibility for details. |
6. Known Limitations
The following accessibility limitations are currently known. withVR BV is committed to addressing these over time:
Limitation | Plan |
No captions for avatar speech inside VR | Planned improvement. Target inclusion in a future release. Contact hello@withvr.app to register interest. |
No formal WCAG 2.2 AA audit of the Web App | A formal accessibility audit is planned when funding permits. Results will be published in an updated Accessibility Statement and VPAT when available. |
Screen reader compatibility not formally tested | Formal screen reader testing (NVDA, JAWS, VoiceOver) is planned as part of the accessibility audit. |
Color contrast not formally audited | Color contrast audit is planned as part of the WCAG 2.2 AA assessment. |
No high-contrast mode, no skip navigation, and browser zoom not functional in the Web App | No high-contrast mode is available. No skip navigation mechanism has been implemented (the application auto-focuses the first input field on each screen, which assists keyboard users but does not satisfy the WCAG requirement). Browser zoom does not affect the Web App interface due to fixed scaling. These are known limitations planned for future updates. |
No alternative to VR headset for the VR experience | The VR experience requires a Meta Quest headset by design. No screen-based alternative to the VR environment is currently planned. The Web App provides full control of the session without requiring the professional to use VR. |
7. Regulatory Compliance Status
This section provides an honest summary of withVR BV's current regulatory compliance position:
Feature / area | Status | Notes |
WCAG 2.2 Level AA | In progress | Target standard. No formal audit completed yet. Working toward conformance. Known partial gaps listed in Section 4 and 6. |
European Accessibility Act (EAA) | Monitoring | EAA in force June 2025. Therapy withVR is primarily a professional platform. The applicability of the EAA to B2B professional tools is being monitored as Belgian implementing guidance develops. withVR BV’s accessibility improvements target EN 301 549 / WCAG 2.2 AA regardless of EAA applicability. |
VPAT / ACR | Available | VPAT v2.5 completed March 2026 for platform version v4.0.0. Available alongside this Accessibility Statement. |
Section 508 (US) | Partial alignment | No formal Section 508 assessment completed. WCAG 2.2 AA work addresses core underlying requirements. |
Our commitment: withVR BV will not claim full accessibility conformance it has not achieved. This statement reflects our honest current position. We are actively working to improve accessibility and will update this statement as progress is made. |
8. Feedback and Accessibility Requests
If you experience an accessibility barrier when using Therapy withVR, or if you have an accessibility requirement that the platform does not currently meet, we want to hear from you.
We will:
- Acknowledge your contact within 5 business days
- Investigate the barrier or requirement you have identified
- Where possible, provide a workaround or alternative access method while a longer-term fix is developed
- Keep you informed of progress
Accessibility feedback and requests: hello@withvr.app Subject line: Accessibility - [brief description of issue or request] Institutional procurement accessibility enquiries: legal@withvr.app |
If you are not satisfied with our response, you may escalate to the Belgian Digital Accessibility Authority or your national accessibility enforcement body.
9. Accessibility Improvement Plan
withVR BV is committed to ongoing accessibility improvement. The following actions are planned:
Action | Target |
Commission a formal WCAG 2.2 AA accessibility audit of the Web App | When funding permits |
Publish an updated Accessibility Statement based on audit findings | Following audit completion |
Update the VPAT (Voluntary Product Accessibility Template) for the current platform version | Completed March 2026 |
Implement captions for avatar speech inside VR | Under development - contact hello@withvr.app to register interest |
Address any critical or high-priority gaps identified in the audit | Within 6 months of audit |
Review and address medium-priority gaps | Within 12 months of audit |
Annual review of this Accessibility Statement | Each March |
This statement was last reviewed in March 2026. The next scheduled review is March 2027, or sooner if material accessibility changes are made to the platform.
withVR BV | Jozef Hebbelynckstraat 21, Merelbeke 9820, Belgium | hello@withvr.app | withvr.app