Accessibility
Accessibility is a core goal, not an afterthought. We aim for WCAG 2.2 level AA, and level AAA where we can.
What we do
- Strong contrast: body text targets a 7:1 ratio, in both light and dark themes.
- Full keyboard use: every control is reachable and operable without a mouse, with a visible focus outline and a “skip to the meaning” link.
- Correct language markup: Malayalam and English runs are tagged so screen readers pronounce them properly.
- Semantic, server-rendered HTML: headings, lists, and real tables, readable without JavaScript.
- Controls that respect you: a light/dark theme and a text-size control; we honour your device's reduced-motion and increased-contrast settings.
- Generous targets: interactive controls are at least 44×44 pixels.
- No accessibility overlay widget: those often make things worse; we build access into the page itself.
Known limitations
- Pronunciation audio exists only for some words (where a real recording is available); the button is hidden when there is none, rather than reading the wrong thing.
- Some romanization is shown in scholarly form (with diacritics) alongside the everyday spelling.
Report a barrier
If something is hard to use, please tell us through the contribute page. We treat access problems as bugs and fix them.
Last updated: 29 August 2026.