Accessibility statement

People use EDFlow in pain, tired, frightened, in a second language, with one hand or with a screen reader. We design every screen for that moment, and we want to hear when we get it wrong.

Version 1.0Effective September 24, 2026

Our standard

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on every screen, on the web and in the apps, and to meet the Accessibility for Ontarians with Disabilities Act (AODA) requirements for websites.[1][2]

  • Text can grow to 200% on the web, and to the largest system sizes on iPhone and Android, without cutting off sentences.
  • Every action has a visible label, targets are at least 44 pixels, and focus is always visible for keyboard users.
  • Status is never shown by colour alone: every state has an icon and words.
  • Screens work with VoiceOver, TalkBack and desktop screen readers, and live updates are announced politely.
  • Reduced motion, high contrast and dark mode are respected.
  • English and French are equal, and patient text is written at a grade 6 to 8 reading level.

How we check, and known limitations

Automated accessibility checks run on every page before each release, and we test by hand with keyboards and screen readers. Known limitations:

  • Charts in the staff analytics have a table view, but some complex charts are easier to read in the table than by screen reader.
  • Languages other than English and French are machine translated after review of safety messages; the rest may read less naturally.
  • Scanning a QR code needs a camera. You can always enter your visit code instead, or ask staff for help.

Other formats

Ask a staff member at the hospital, or write to support@edflow.space, for any of this information in another format, such as large print, plain text or a format that works with your assistive technology. We will provide it at no cost.

Feedback and our response

Tell us about any barrier you meet with the form below or at support@edflow.space. A person will reply within 5 business days, and we track every report until it is fixed or explained. Please don't include any health information.

Tell us about a barrier

Sources

  1. [1]What's New in WCAG 2.2 (opens in a new tab) · W3C
  2. [2]How to make websites accessible (AODA) (opens in a new tab) · Government of Ontario