Accessibility
Everyone should be able to learn about treatments, complete an online visit, and manage their care on StackRx, including people who use assistive technology. This statement explains what we're doing and how to reach us if something gets in your way.
Our commitment
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across joinstackrx.com and the StackRx account, intake, and checkout experience. WCAG is a widely used standard for making digital content usable by people with a range of disabilities.
Accessibility is ongoing work. We treat it as part of how we design, build, and review every page, not as a one-time project.
How we approach it
Our goals include:
- Pages that work with a keyboard alone, with a visible focus indicator.
- Clear headings, labels, and page structure that screen readers can follow.
- Text alternatives for meaningful images, and captions or descriptions for videos that carry information.
- Enough color contrast to read text comfortably, and never using color alone to convey meaning.
- Text that can be resized and zoomed without losing content.
- Respect for your device's reduced-motion setting.
- Forms with clear instructions, helpful error messages, and enough time to complete them.
- Plain language, especially for health and legal information.
How we test
We test every page type (home, shop, each treatment page, legal pages, and error pages) at desktop and mobile sizes, including with menus open:
- Automated checks against WCAG 2.0, 2.1 and 2.2 Level A and AA rules, using the open-source axe-core engine.
- Scripted keyboard checks: skip link, menus, the mobile menu, the plan picker, pause controls for moving content, focus visibility, and error messages.
- Layout checks at 320 pixels wide (equivalent to 400% zoom) for content that would force sideways scrolling.
- Color contrast checks for text and focus indicators.
We re-run these checks before every release. [Manual screen reader testing (NVDA, VoiceOver) and an independent audit: add who and when once scheduled]
Known limitations
We know some parts of StackRx may not yet fully meet our goals. As of our last review, our automated and keyboard checks found no failures. Online visits, sign-in and checkout are not yet available on the site; they will be tested against the same standard before they launch. [Confirm, and add any limitations found in manual screen reader testing]
Third-party tools
Some parts of the experience may be provided by partners, such as the payment form or provider messaging tools. We ask our partners to meet accessibility standards and will work with them to fix issues you report. [List of third-party tools used in the patient flow]
Need help, or found a barrier?
If something on StackRx is hard to use, please tell us. We'll help you get what you need another way, and we'll work on a fix.
- Email: [Accessibility email]
- Phone: [Support phone]
- Mail: [Mailing address]
It helps to include the page address, what you were trying to do, and the device, browser, and any assistive technology you were using. You don't need to include any health information.
You can also ask for this or any other StackRx policy in another format, such as large print or plain text.
How we respond
We'll reply within [Response timeframe, e.g., 2 business days] to confirm we've received your message, and we'll keep you updated until the issue is resolved.
Last reviewed
This statement was last reviewed on September 26, 2026.