WeDosify Accessibility Statement
v1.0
Purpose
This accessibility statement applies to the WeDosify Non-Device Clinical Decision Support web application. This statement covers the web-based version of WeDosify and does not apply to any mobile applications or third-party integrations.
2. Our commitment to accessibility
Closed Loop Medicine is committed to ensuring the WeDosify web application is accessible to as many users as possible.
Our approach includes:
Inclusive design: Incorporating accessibility into our product development process from initial design through to implementation.
Designated oversight: An accessibility officer monitors compliance and coordinates improvements efforts.
Quality assurance: Accessibility testing as part of our release process through internal auditing for each major product release.
User feedback: Response to accessibility feedback from our user community.
3. Feedback and support
We welcome feedback on ways we can improve the accessibility of the WeDosify software. If you want to report a problem not listed on this page or think we can improve accessibility, please email support@wedosify.com.
4. Compliance status
The WeDosify application is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.2 level AA standard.
The application’s intended use population is limited to Primary Care physicians, as such, we anticipate little to no impact from the below listed non-compliances within this version.
4.1 Non-accessible content
The content listed below is non-accessible for the following reasons:
There is no support for screen reader technology throughout the application currently. Details are below in the ‘Disproportionate burden’ section.
4.2 Disproportionate burden
Programmatic identification for screen reader support.
The WeDosify application does not support screen reader technology. Given the intended use population, we expect little to no impact from the lack of screen reader support in this version of the product. We intend to implement satisfactory functionality with future releases or if this limitation directly affects current users.
This fails the below criterion:
1.3.1 (Information and relationship)
1.3.2 (Meaningful sequences)
1.3.5 (Identify input purpose)
2.4.3 (Focus order)
2.5.3 (Label in name)
3.1.1 (Language of page)
3.1.2 (Language of parts)
4.1.2 (Name, Role, Value)
5. Accessibility statement preparation
This statement was prepared on Jul 16, 2025.
Where appropriate, we include updates in our product development roadmap in response to changing regulatory requirements. WCAG compliance level is internally audited for each major product release.