Skip to content
Accessibility

Accessibility statement

Our commitment to WCAG 2.1 Level AA conformance, how we test for it, and how to report a barrier you run into.

Our commitment

ImpactMojo is a free platform for development education across South Asia. A platform that cannot be used by people with disabilities (by screen reader users, keyboard-only users, people with low vision, people with motor impairments, people with cognitive differences) is not actually free. It is free only to those whose bodies already match what the web assumed.

Accessibility is part of the minimum we ship. Every page we ship should be usable with a screen reader, navigable with a keyboard, readable at any zoom level up to 200%, and legible to someone with moderate colour-vision differences or low-contrast sensitivity.

Conformance status

Target: Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

Current status: Partially conformant. The core public pages of impactmojo.in meet WCAG 2.1 Level AA as measured by automated testing (see below). Some third-party embedded content and legacy pages have known limitations that we are working through.

Scope: This statement covers everything under https://www.impactmojo.in/, including the homepage, the catalog, 22 flagship courses, 84 foundational courses in the 101 Series, 135 games, 35 Free Studio tools, book summaries, blog, and policy pages. It does not cover external sites we link to.

Statement last updated: 31 October 2026.

How we test

Every page on the site is checked each day with an automated accessibility tool against WCAG 2.1 Level AA: once in the light theme at phone width and once in the dark theme at desktop width. The same check also looks for pages that scroll sideways on a phone. When we change a page, it is checked again before the change goes live, and a new serious or critical problem keeps the change from going live until it is fixed.

The pages most people use (the homepage, sign-in and sign-up, About, the catalogue, the BCT Repository, membership, your account, coaching, the FAQ, the dojos, the Dataverse and the handouts) get a second, separate tool as well, in both themes and at both widths.

Manual review

Automated tools find roughly 30 to 50% of real accessibility problems. For the rest, we move through pages with the keyboard alone, test with the VoiceOver and NVDA screen readers when we add a major new section, and read our own pages at 200% zoom to check that nothing runs off the screen or becomes unreachable.

For the full story of how we got here, including the day we discovered our own site was lying about its accessibility state, read What It Actually Takes to Make an Accessible Website on our blog.

Accessibility features

  • Pages are built with headings, page regions and form labels that a screen reader can announce and jump between.
  • Every button, link and control can be reached with the keyboard, and the one in focus carries a visible outline in both colour themes.
  • Pages with long menus have a skip-to-content link.
  • Body text has a contrast of at least 6.2:1 in the light theme and 6.96:1 in the dark theme, above the 4.5:1 that WCAG AA asks for.
  • Pages open in the light or dark theme your device is set to, and a System, Light and Dark switch lets you choose otherwise.
  • The main pages can be read at 200% zoom without scrolling sideways.
  • Decorative animation switches off if your device is set to reduce motion.
  • Links inside running text are underlined, so you can tell them apart without relying on colour (WCAG 2.1 §1.4.1).
  • The Accessibility button in the top bar of every page sets the theme, the text size, wider line, letter and word spacing, underlines on every link, reduced motion and a stronger focus outline, and remembers your choices on this device. Its dyslexia-friendly font switch sets the whole page in OpenDyslexic (SIL Open Font License, self-hosted, nothing downloaded unless you switch it on) and opens up the letter, word and line spacing of running text. Your choice is remembered. The spacing is the part with the stronger evidence behind it: Zorzi et al. (PNAS 109(28), 2012) found extra letter spacing raised reading speed and halved errors in children with dyslexia, while Kuster et al. (Annals of Dyslexia, 2018) found a dyslexia-specific typeface gave no benefit over Arial. We ship the font because some readers prefer it, and the spacing because it works. The font covers Latin script only, so translated pages are unaffected.
  • A translation menu on key pages: Hindi, Tamil, Bengali, Marathi, and more are being rolled out.
  • Captions and transcripts come with the videos we produce. Podcast episodes include show notes.

Known limitations

We are honest about what is not yet fully conformant:

  • The 101 course slide decks are now our own pages, which ended the keyboard traps of the embedded decks they replaced and gave them a dark theme. A slide deck is still harder to follow in order with a screen reader than a plain page, and we are still working on that.
  • On 17 of the older Reading Companions, the keyboard may move through the page in an unexpected order.
  • Some of our 135 games and 35 Free Studio tools use custom canvas-based interactions (drag and drop, charts, timed simulations) that are challenging to make fully screen-reader accessible. We provide text alternatives and keyboard fallbacks where we can, but coverage is not yet complete.
  • The guided site tour and Google Translate come from other providers, so we cannot change their code. We check them by hand where we can.
  • Automated tools test only a third to a half of the WCAG success criteria. Problems with reading order, cognitive load and text alternatives for visual content can only be found by people.

How to report an accessibility barrier

If you run into something that stops you from using ImpactMojo, please tell us. We treat an accessibility report as a high-priority fault.

  • Email hello@impactmojo.in with "Accessibility issue" in the subject line.
  • If you have a GitHub account, you can open an issue on our public issue tracker and add the label "accessibility".
  • In the message, tell us the page URL, what you were trying to do, what happened instead, and (if you can) what assistive technology and browser you were using. Screenshots or screen recordings are helpful but not required.

We aim to acknowledge accessibility reports within two working days and to ship a fix or a clear plan within two weeks for serious or critical issues.

Standards and references

Changes to this statement

We update this statement whenever the way we test, the known limitations or the scope of conformance changes. Changes to the site are listed on our updates page.