Accessibility

Effective date: August 24, 2026

WCAG 2.1 AA targetSection 508VPAT on request

Clinicians are not a uniform group, and neither is the staff around them. Someone reading a caseload with a screen reader, someone who cannot use a trackpad after a long shift, someone adjusting contrast at the end of a fourteen-hour day: the product has to work for all of them. This page states our target, what is already true, and where we fall short.

The standard we work to

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, which is also the benchmark Section 508 references for federal procurement and the one most health systems and universities apply in their own reviews.

A Voluntary Product Accessibility Template (VPAT) documenting our conformance claim is available to customers and prospects on request at hi@medera.info.

What is in place

Keyboard operation. Every interactive control is reachable and operable by keyboard, with a visible focus indicator, and no keyboard traps.
Semantic structure. Pages use real headings in order, landmark regions and native controls, so assistive technology can navigate by structure rather than by guessing.
Contrast. Body text and interface text meet or exceed the 4.5:1 ratio AA requires; large text and interface components meet 3:1.
Reduced motion. Scroll animations and transitions are suppressed for anyone whose system requests reduced motion.
Text alternatives. Meaningful images carry descriptions; decorative artwork is hidden from assistive technology rather than announced as noise.
Resizing and reflow. Content reflows to narrow viewports and remains usable at 200% zoom without horizontal scrolling.
Forms. Every field has a programmatically associated label, and errors are announced rather than signalled by colour alone.

Where we fall short today

An accessibility statement that claims everything works is not worth reading. These are the known gaps we are working on.

Live transcript regions. Rapidly updating text can overwhelm a screen reader. We are refining the live-region politeness settings so updates are announced usefully rather than constantly.
Data-dense visualisations. Outcome charts convey a great deal through position and colour. Tabular equivalents exist for the underlying data, but the parity between the two is not yet complete.
Third-party components. Where we embed a vendor component, its conformance is theirs, and we do not claim what we cannot verify. We are auditing each one and replacing those that fall short.
Formal audit. Our conformance claim is currently based on internal testing with keyboard, VoiceOver and NVDA, plus automated checks. An independent third-party audit is planned rather than complete, and we will say so here until it is.

If a barrier is blocking your work right now, tell us and we will find you a way through while we fix the underlying issue. That is a better outcome than waiting for a release.

How we test

Manual keyboard-only walkthroughs of every primary workflow before release.
Screen reader testing with VoiceOver on macOS and iOS, and NVDA on Windows.
Automated checks in continuous integration, which catch regressions but never substitute for the manual passes.
Contrast verified against the design tokens rather than per-screen, so a fix holds across the product.

Reporting a barrier

Email hi@medera.info with what you were trying to do, the assistive technology and browser you were using, and the page or screen where it broke. We acknowledge within two business days and will tell you honestly whether the fix is days or quarters away.

Our Trust Center, Privacy Policy and Acceptable Use Policy.

Questions about this document?

Our privacy and legal team responds to verified requests within thirty days, and usually much sooner.