MedNow

Accessibility

Last reviewed: August 25, 2026Target: WCAG 2.2 Level AA

MedNow is study software for people training to work in healthcare. Some of those people are disabled, and a practice exam that cannot be taken without sight or without a mouse is not a practice exam — it is a closed door in front of a career.

This page says where we actually stand, including what still does not work. If you hit a barrier, please tell us: team@mednowapp.com.

1. The standard we work to

We measure ourselves against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. WCAG 2.1 Level AA is the standard the U.S. Department of Justice adopted for state and local government under Title II of the ADA, and it is the benchmark courts and settlements apply to private businesses. WCAG 2.2 includes everything in 2.1, so working to 2.2 covers both.

2. Conformance status

Partially conformant with WCAG 2.2 Level AA. “Partially conformant” means most of the product meets the standard, but some parts do not yet. We are not claiming full conformance, because we have not completed the testing that would justify that claim — see section 5.

3. What we have done

  • Every interactive control is reachable and operable by keyboard alone, with a visible focus indicator in both the light and dark themes.
  • Results, scores, timers, errors and loading states are announced to screen readers, rather than being shown only by colour or position.
  • Colour contrast is measured against the WCAG formula, as a test that reads the real theme values and runs on every push and pull request — a colour that fails the ratio fails that check.
  • Nothing depends on colour alone to convey meaning.
  • The interface honours your system settings for reduced motion and increased contrast.
  • Page structure uses real headings, lists, tables and landmarks, so a screen reader can navigate by them.
  • Charts and diagrams have text alternatives that carry the same information, not just a label saying a chart is present.
  • Keyboard shortcuts are scoped so they do not fight a screen reader’s own single-key navigation.

4. Known limitations

These are the things we know are not right yet. This list is maintained honestly; if you find something not on it, that is a gap in our testing and we would like to know.

  • Diagram-based questions. A small number of practice items ask you to identify a region of an anatomical diagram. Every region is keyboard-reachable and described by its position in words, but these items are inherently visual and spatial. If they are a barrier for you, contact us and we will arrange an alternative.
  • Printed and PDF documents. Worksheets, exam papers and student reports are generated for printing. We are still improving how well their structure survives into a tagged PDF.
  • Third-party content. Payment pages are hosted by Stripe and we do not control their accessibility.
  • Timed exams. Full-length mock exams are timed because the real certification exam is timed, and removing the limit would stop it being a realistic rehearsal. If you receive extended time on your actual exam, contact us — we do not want the practice to be harder than the real thing.

5. How we have tested

Our review so far has been an audit of the code and interface against WCAG 2.2 AA, plus automated checks — contrast ratios, accessible names on controls, keyboard shortcut handling — that run on every push and pull request. To be exact about what that does and does not guarantee: those checks gate the repository, not the deploy itself, so they are a signal we act on rather than a wall that makes a regression impossible. And they catch a great deal, but they are not the same as testing with assistive technology in the hands of the people who use it. Testing with screen-reader users is the next thing we are doing, and until it is done we will not claim full conformance.

The product is built with Next.js and React and is intended to work in current versions of Chrome, Edge, Firefox and Safari, with VoiceOver, NVDA and JAWS.

6. Tell us about a barrier

If any part of MedNow is difficult or impossible for you to use, please email team@mednowapp.com. It helps if you can tell us the page, what you were trying to do, and what assistive technology and browser you were using — but please write to us even if you would rather not go into detail.

We aim to reply within five business days. If something is blocking you from studying right now, say so and we will prioritise it and find you a way through in the meantime.

If you need something in a different format, or need an adjustment to use the product, ask. We would rather make an arrangement than have you go without.

7. For schools and programs

If you are evaluating MedNow for an institution and need an accessibility conformance report (VPAT) for procurement, contact us at team@mednowapp.com and tell us which edition you need. We would rather give you an accurate report with its gaps marked than a clean one you cannot rely on.