Skip to main content
oncall.fyi

Accessibility

We want oncall.fyi to be usable by the people who design and carry on-call responsibility, including people who navigate with a keyboard, screen reader, zoom, voice input, reduced motion, or alternative colour settings.

Our target

Our target is WCAG 2.2 Level AA for the public site and its core tool flows. This target does not by itself constitute a legal conformance claim. We use automated checks together with keyboard, zoom, screen-reader, contrast, mobile and reduced-motion testing.

WCAG 2.2 added four success criteria at Level AA — 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), and 3.3.8 Accessible Authentication (Minimum) — and two at Level A, 3.2.6 Consistent Help and 3.3.7 Redundant Entry, which AA conformance also requires.

What we do

  • Semantic headings and landmarks
  • A skip link and a visible focus indicator that is never removed
  • Tools that can be completed entirely by keyboard
  • Real labels, with error messages next to the field they belong to
  • Result announcements through a live region
  • Written interpretation alongside every score, so no chart is the only way to understand a result
  • Colour plus an icon or a label for every state — never colour alone
  • Reduced-motion support: with motion reduced, animation is removed and no information or function is lost
  • No dragging. Reordering uses buttons, which satisfies 2.5.7 by design rather than by workaround
  • Responsive reflow, tested at 360, 390, 768, 1024, 1280 and 1440 px
  • Primary controls at least 44 by 44 px, above the 24 px minimum
  • No authentication anywhere on the site, so 3.3.8 has no failing surface

Known limitations

We do not use a generic “fully compliant” statement while unresolved barriers exist. Current known issues:

  • Independent audit not yet done. The site has been tested by the team that built it, not by an independent accessibility reviewer. Owner: the MonoDuty Support Team.
  • Screen-reader coverage. Testing so far has been structural and keyboard-based. A full pass with VoiceOver, NVDA and JAWS on the tool flows is outstanding.

Feedback

If a page or tool is difficult to use, write to [email protected] and include the page, the task, your browser and device, and your assistive technology if you are comfortable doing so. The MonoDuty Support Team aims to acknowledge accessibility reports within 5 business days.

Review record

Last reviewed: 3 September 2026
Test scope: every page template — home, guide, template, glossary term, migration, the three tool flows, search, and the policy pages. Checks run: keyboard-only operation, accessible name on every focusable element, heading order, landmark structure, colour contrast measured numerically in both themes, reduced-motion behaviour, target sizes, and reflow from 360 px to 1440 px.
Standards reference: WCAG 2.2 Level AA target