Accessibility statement

10 November 2026. Monty (hellomonty.app) aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, for students and for teachers, in English, French, Arabic and Spanish.

What Monty does

  • Every page works with a keyboard, with visible focus; touch targets are at least 44 pixels.
  • Colour is never the only signal: statuses have an icon and words.
  • Settings has a text size, spacing and tint, and a choice of fonts (Lexend, Atkinson Hyperlegible Next, OpenDyslexic); movement follows the device's "reduce motion" setting or Monty's own; sound is off.
  • Pages read right to left in Arabic, while code stays left to right, as Python needs.
  • Feedback is read out once, whole, to screen readers, not letter by letter as it appears.
  • Light and dark colour schemes, both checked for contrast.

How it's checked

  • Automated checks (axe) on the main pages at phone and desktop widths, in every test run on three browsers.
  • A sweep of every page and every lesson step, in both colour schemes and several languages, for text that spills, overlaps or is cut off.
  • A look by eye at phone and desktop widths before each release.

Monty hasn't been audited by an independent accessibility specialist yet.

Known limits

  • The code editor hasn't been tested with every screen reader yet.
  • The French, Arabic and Spanish texts are drafts until a native speaker has reviewed them.

Tell us

If something doesn't work for you, say so through the complaints and concerns route, or reply to any email from Monty. We reply within 2 school days.