Accessibility Statement
Last Updated: August 12, 2026
1. Our Commitment
This tool exists to help people work with text in their own language. That includes people who use a keyboard only, a screen reader, or high-contrast and enlarged text settings. We aim to meet WCAG 2.1 level AA for the converter and the content around it, and we treat accessibility problems as bugs to fix rather than nice-to-haves.
2. Keyboard Access
Every control in the converter — the input and output boxes, the script and font selectors, the copy, swap, clear and history buttons, the theme toggle and the language switcher — can be reached and operated with the keyboard alone. Focus is visible on all interactive elements. The FAQ items are native disclosure widgets, so they open with Enter or Space.
3. Screen Readers and Labels
Form controls carry labels, images carry alternative text, and the page has one main heading and a logical heading order. Status messages such as 'Copied' are announced. The converter's two text areas are labelled as Unicode input and legacy output so their purpose is clear out of context.
4. Colour and Contrast
Text and interface colours meet the AA contrast ratio in both light and dark themes, and the site respects your operating system's colour-scheme preference. Colour is never the only way information is conveyed. Text size can be changed from the site's own control and from your browser without breaking the layout.
5. Known Limitations
Legacy Indic fonts are third-party files whose glyphs we do not control; a converted character may be visually ambiguous in a given font, which is a property of the font rather than of the page. Some older DTP workflows the site documents require software that is not itself accessible. If you hit a barrier we have not listed, tell us.
6. Reporting a Problem
If something on this site blocks you, please contact us with the page address, what you were trying to do, and the assistive technology or browser you were using. We will respond and fix what we can.