Skip to content

Accessibility

EDFlow accessibility conformance for hospital reviewers: WCAG 2.2 AA on every surface, how it is tested (axe in CI, keyboard, screen readers, Dynamic Type and font scale), the conformance report, and known issues.

Every patient, family, staff, admin and display screen targets WCAG 2.2 level AA, and so do these docs.

Screenshot pending: patient-visit-homeThis screenshot is captured automatically from the running app with sample data.
WebYour visit

How it's tested

MethodWhere
axe (WCAG 2.2 AA rules)Every web end-to-end test, light and dark, English and French; build fails on a violation
KeyboardEvery flow operable without a mouse; visible focus; shortcuts documented
Screen readersVoiceOver (macOS, iOS), TalkBack, NVDA and JAWS on release candidates
Text sizeWeb at 200% on a 360-pixel phone with no horizontal scroll or clipping; iOS Dynamic Type to the largest accessibility sizes; Android font scale 200%
ColourStatus never by colour alone (greyscale snapshot tests); contrast checked on tokens
MotionReduced motion honoured; no flashing; notices fade in 200 ms at most
Target sizeControls at least 44 px (48 px for patient request tiles); every swipe action has a button

Patient-specific design

  • Plain language at grade 6 to 8, checked in CI.
  • The "I feel worse" screen and delay notices take focus and announce their title.
  • Stage changes are announced politely without moving focus.
  • English and French everywhere, plus safety messages in up to five community languages.

Conformance report

An Accessibility Conformance Report in VPAT 2.5 INT format is part of the security package, with the known issues from the latest CI run. Request it from Compliance documents.

Reporting a problem

Report accessibility problems through the contact page on the product site; they are triaged like defects.

Last updated on

Was this page helpful?

On this page