Rymeda
Accessibility

Accessibility Statement

Last updated 2026-06-20

Rymeda is for everyone who wants to take part in their health. We want the app to work well no matter how you see, hear, move, or interact with your device.

Rymeda is in private beta, so some features are still being refined. This statement explains what we have built, what is still a work in progress, and how to reach us if something gets in your way.

Our commitment

We believe access to health information and community should not depend on ability. Rymeda is committed to designing and building an app that people with a wide range of abilities can use comfortably and independently. Accessibility is treated as part of the product, not an afterthought, and it is something we keep working on with every release.

The standard we follow

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These are internationally recognized guidelines for making digital products usable by people with disabilities, covering things like readable text, clear structure, sufficient color contrast, and support for assistive technology. We use these guidelines as our target across the Rymeda app and this website. During the private beta we are still working toward full conformance, and we describe the gaps we know about below.

Standards and legal frameworks

Rymeda is available worldwide, so different accessibility rules apply depending on where you are. We treat the following as goals and as our direction of travel. They are not a promise that Rymeda fully conforms today, especially during the private beta.

  • WCAG 2.1 Level AA. This is the standard we currently target across the Rymeda app and this website, as described in the section above.
  • WCAG 2.2. We are aware that WCAG 2.2, published in 2023, is now the current version of the guidelines. We treat its additional criteria as our direction of travel and aim to move toward them over time.
  • European Union. Rymeda is not currently offered in the EU. The European Accessibility Act would apply to users in the EU on a future EU launch; its requirements are generally met through the EN 301 549 standard, which maps to WCAG 2.1 Level AA. That alignment is part of why WCAG 2.1 AA is our baseline target regardless of region.
  • United States. For users in the US, we work toward the accessibility expectations reflected in the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act.

These references describe the standards and laws we are working toward, not a certification or a guarantee of conformance, and they should not be relied on as a statement of legal compliance.

Accessibility features

Rymeda includes the following accessibility features:

  • Scalable text (Dynamic Type). Rymeda respects the text size you choose in your device settings, so you can make text larger or smaller and the app adjusts to fit.
  • Reduced motion. If you turn on Reduce Motion in your device settings, Rymeda limits animations and motion effects to make the experience calmer and easier to use.
  • Screen reader and VoiceOver support. Buttons, links, images, and other controls are labeled so screen readers such as VoiceOver can describe them and let you navigate by voice and gesture.
  • Color and contrast. We design text and important controls to have enough contrast against their background to stay readable, and we avoid using color alone to carry meaning.
  • Alternative text. Meaningful images include text descriptions so their content is available to people who cannot see them.
  • Clear structure and focus. Screens use headings and a logical order so that content is easier to follow with assistive technology and easier to scan visually.

Known limitations during beta

Because Rymeda is in active development, there are areas we are still improving. We want to be honest about them:

  • Some newer or experimental screens may not yet have complete screen-reader labels.
  • A small number of controls and images may be missing descriptions, which we are correcting as we find them.
  • Color contrast on a few non-essential or decorative elements may not yet meet the AA target.
  • Member-created Community content, such as posts and uploaded images, may not always include alternative text.

We are actively working to close these gaps. If you run into a barrier that is not listed here, please tell us using the contact details below so we can prioritize a fix.

Our ongoing process

Accessibility is an ongoing effort, not a one-time check. As part of building Rymeda we:

  • Consider accessibility when we design and review new features.
  • Test with assistive technology, including screen readers, and with different text sizes.
  • Fix accessibility issues that we find internally or that members report to us.
  • Update this statement as the app changes and as we make progress toward full WCAG 2.1 AA conformance.

Requesting accommodations

If you need an accommodation to use Rymeda, or if a part of the app is not working for you with your assistive technology, please reach out. Email accessibility@rymeda.com and tell us what you are trying to do and what is getting in the way. We will do our best to help you and to find an alternative while we work on a fix.

Reporting a barrier

If you come across an accessibility barrier in the Rymeda app or on this website, we want to know. When you write to accessibility@rymeda.com, it helps if you can include:

  • The screen or page where you ran into the problem.
  • What you were trying to do.
  • The device and operating system you were using, and any assistive technology, such as VoiceOver.
  • What happened, and what you expected to happen.

We treat accessibility reports as a priority and will respond as quickly as we can.

Feedback

Your feedback helps make Rymeda better for everyone. For accessibility-specific feedback, email accessibility@rymeda.com. For general questions you can visit our Support page or our Contact page, and for more on how we handle your information, see our Privacy Policy.

Rymeda is in private beta. This statement reflects the current state of the product and will be updated as our accessibility work continues.