Legal
Accessibility Statement
Effective Date: February 2026
Document Version: 2.0
Rymeda, Inc. (“Rymeda,” “we,” “us”) is committed to ensuring digital accessibility for people with disabilities. As a healthcare technology platform, we recognize that accessible design is not only a legal obligation but a clinical imperative — patients and providers with disabilities must have equal access to healthcare tools and information.
1. Conformance Standards
The Rymeda platform is designed and developed to conform to the following accessibility standards:
| Standard | Level | Description |
|---|---|---|
| WCAG 2.1 | Level AA | Web Content Accessibility Guidelines 2.1 Level AA, published by the W3C Web Accessibility Initiative (WAI). Covers perceivable, operable, understandable, and robust criteria |
| ADA Title III | Full compliance | Americans with Disabilities Act, 42 USC §12101 et seq. — equal access to places of public accommodation, including digital services |
| Section 508 | Full compliance | Rehabilitation Act §508, 29 USC §794d — electronic and information technology accessibility for federal agencies and their contractors |
| EN 301 549 | Aligned | European standard for digital accessibility, aligned with WCAG 2.1 AA. Applicable to EU users |
2. Accessibility Features
| Category | Feature | WCAG Criterion |
|---|---|---|
| Structure | Semantic HTML with heading hierarchy (h1–h6), landmark regions (main, nav, header, footer), and proper document structure | 1.3.1 Info and Relationships |
| Navigation | Full keyboard navigability without mouse. Visible focus indicators for all interactive elements. Skip-to-content links | 2.1.1 Keyboard; 2.4.7 Focus Visible |
| Color & Contrast | Minimum 4.5:1 contrast for normal text, 3:1 for large text. Color is not the sole means of conveying information. Colored badges include text labels | 1.4.3 Contrast (Minimum); 1.4.1 Use of Color |
| Text Alternatives | Alt text for images and icons. ARIA labels for interactive elements. Decorative images marked with aria-hidden | 1.1.1 Non-text Content |
| Forms | Labels associated with input fields. Error messages identify the field and describe the error. Required fields indicated programmatically | 1.3.1; 3.3.1 Error Identification; 3.3.2 Labels |
| Responsive Design | Content reflows at 320px width. Browser zoom up to 200% without content loss. No horizontal scrolling at standard breakpoints | 1.4.10 Reflow; 1.4.4 Resize Text |
| Assistive Technology | Compatible with NVDA, VoiceOver, JAWS, and TalkBack screen readers. ARIA roles and live regions for dynamic content updates | 4.1.2 Name, Role, Value |
| Motion & Animation | Respects prefers-reduced-motion OS setting. Framer Motion animations disable when reduced motion is preferred. No auto-playing content | 2.3.3 Animation from Interactions |
3. Healthcare-Specific Accessibility
As a healthcare platform, Rymeda implements additional accessibility measures for clinical workflows:
- Clinical Data Tables: Data tables (vitals, lab results, medications) include proper
<th>headers,scopeattributes, and captions for screen reader navigation - Status Indicators: Clinical note statuses (draft, AI draft, reviewed, signed) use text labels in addition to color coding
- Voice-to-Text Alternative: Voice note functionality provides text-based alternatives for providers who cannot use audio input
- Telehealth Accessibility: 100ms video sessions support closed captioning and adjustable display settings
- Legal Documents: All legal and policy pages use semantic HTML structure accessible to screen readers with proper heading navigation
4. Known Limitations
While we strive for full WCAG 2.1 Level AA conformance, the following limitations are known and being actively remediated:
| Limitation | Affected Area | Remediation Plan |
|---|---|---|
| Complex data visualizations may lack complete text alternatives | Analytics dashboards, clinical charts | Implementing data table alternatives and enhanced ARIA descriptions |
| Some third-party embedded content may not fully conform | 100ms video interface, Stripe payment forms | Working with vendors to improve accessibility. Providing alternative workflows where needed |
| Older PDF documents may not be fully tagged | Legacy document uploads | Rolling remediation program to re-tag PDFs with proper accessibility structure |
5. Testing & Evaluation
| Method | Frequency | Scope |
|---|---|---|
| Automated Scanning | Every build (CI/CD) | ESLint jsx-a11y plugin enforces accessibility rules during development. Automated WCAG checks in deployment pipeline |
| Screen Reader Testing | Monthly | Manual testing with NVDA (Windows), VoiceOver (macOS/iOS), JAWS (Windows), and TalkBack (Android) |
| Keyboard Navigation | Every feature release | Complete keyboard-only navigation testing of all interactive features |
| Third-Party Audit | Annual | Independent accessibility audit by qualified accessibility consultants against WCAG 2.1 AA criteria |
| User Testing | Semi-annual | Usability testing sessions with participants with disabilities, including screen reader users and keyboard-only users |
6. Accommodation Requests
If you experience any accessibility barrier or need assistance accessing content or features on the Rymeda platform, we will work with you to provide the information or service in an accessible format. Accommodation requests are handled as follows:
- Email legal@rymeda.com with a description of the barrier
- We acknowledge all accessibility requests within 2 business days
- We provide an interim accommodation within 5 business days where feasible
- Permanent fixes are prioritized in the development backlog based on severity and impact
- You will be notified when the barrier has been resolved
Contact
Legal Team