Refidly

Accessibility Statement

Where Refidly stands against WCAG 2.1 Level AA, what still falls short, and how to tell us when something blocks you.

Last updated · August 11, 2026

Our standard

What we do

  • Keyboard operation across navigation, forms, dialogs, and the referral tables, with a visible focus indicator on every interactive element.
  • Semantic headings, landmarks, and labelled navigation so screen reader users can move through a page by structure.
  • Form fields tied to their labels, with validation errors announced as text rather than signalled by color alone.
  • Text and interface colors chosen from a token palette checked against WCAG AA contrast, in both light and dark themes.
  • Motion respected: animated reveals and floating elements stop when the operating system requests reduced motion.
  • Layouts that reflow without horizontal scrolling down to a narrow viewport, and that survive browser zoom to 200 percent.
  • Meaningful alternative text on informative images, and decorative graphics hidden from assistive technology.

Known limitations

  • The referral and facility tables carry many dynamic columns. Keyboard navigation works, but announcement of cell context during inline editing is still being improved.
  • Analytics charts convey trends visually. Underlying figures are available through CSV export, and text alternatives for each chart are in progress.
  • The calendar view uses a third-party component whose keyboard behaviour we do not fully control. We are tracking its accessibility fixes upstream.
  • Some PDF and CSV exports are generated for print layout and are not tagged for screen readers.

How we test

Feedback

Accessibility feedback