Coming soon: we're building something new Get in touch →

Accessibility statement

Last updated: 29 September 2026

Our commitment

Marky is committed to ensuring digital accessibility for all users, including teachers, students, and parents with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standard.

Accessibility features

The Marky platform and this website include the following accessibility features:

Website (this site)

  • Skip to content links on every page for keyboard navigation.
  • Semantic HTML with proper heading hierarchy and landmarks.
  • Breadcrumb navigation with ARIA labels.
  • Alt text and ARIA labels on interactive elements.
  • Responsive design that works on all screen sizes.
  • Sufficient colour contrast throughout the design.
  • No autoplay media or flashing content.
  • Print stylesheet for clean printing.

Marky application

  • Text-to-Speech (TTS): Students and parents can have content read aloud.
  • Dyslexia-friendly font: Selectable alternative font for improved readability.
  • Extra time settings: Teachers can configure extended time for SEND students on the practice exams they sit in the student portal.
  • High contrast mode: Available alongside dark mode for improved visibility.
  • Keyboard navigable: the application is built to be used with a keyboard alone, and we check this by hand as screens change.
  • Screen reader support: Built with semantic HTML, ARIA labelling and a complete keyboard path, so a screen reader can navigate the application.
  • Support for 60 languages: Interface translation, including right-to-left layouts for Arabic, Persian, Hebrew, and Pashto.
  • Resizable text: Interface scales properly up to 200% zoom.

Known limitations

  • PDFs that Marky generates, such as reports, practice papers and mark schemes, carry a document title and language, so a screen reader announces them correctly and reads them in the right voice. They are not currently tagged for accessibility (PDF/UA), which means reading order is not guaranteed in a complex table. We are migrating student and parent reports to a tagged PDF/UA-1 output and will update this statement when that work ships. On-screen results are fully accessible in the meantime, and we will supply an accessible alternative format on request: email hello@markyedu.com.

Testing

Every page of this website is checked against WCAG 2.1 A and AA with axe-core as part of our site checks, which fail on any serious or critical violation. That check is real tooling, not a statement of intent. Its first run found thirty-one contrast failures on our own pages, and every one was fixed before this page claimed any of the following. What we do:

  • Run axe-core over every built page, failing on serious and critical WCAG 2.1 AA violations. The latest run found none on any page.
  • Build to the semantic HTML and ARIA patterns WCAG 2.1 AA calls for, and check keyboard navigation by hand as pages change.
  • Hold every text/background pair to the AA contrast ratio, which the automated check now enforces rather than trusts.
  • Treat any accessibility problem a school reports to us as a priority fix. We have not yet commissioned an independent WCAG audit or a formal screen-reader audit, and we would rather say so than imply one.

Feedback

We welcome feedback on the accessibility of Marky. If you encounter any barriers, please contact us:

We aim to respond to accessibility feedback within 5 working days.

Enforcement

If you are not satisfied with our response, you can contact the Equality Advisory Support Service (EASS).