Accessibility statement

Semantic HTML (headings, lists, tables, real <button>/<a> elements) throughout. A ‘Skip to main content’ link as the first thing keyboard focus reaches. Every form control is now programmatically joined to its label, and the six one-time-code boxes are announced as a single named group. Data table headers carry scope, so a screen reader can say which column a cell belongs to. The page language attribute follows the English/Hindi toggle, so Hindi is not read aloud in an English voice. Every disabled control carries a tooltip explaining why, instead of just looking greyed out.

Colour contrast was computed for every text and background pair in the palette against WCAG 2.2 AA. All text pairs pass, most of them well clear of the 4.5:1 minimum. Two things failed and were fixed: the focus ring's dark edge ran along the bottom of a control only, leaving three sides below the 3:1 a focus indicator needs, and one secondary button's outline was too faint to be its own boundary. Faint dividers between table rows remain low-contrast by design; they are decoration, not the thing identifying a control.

No testing with an actual screen reader, on any platform. No testing by anyone who uses assistive technology daily. Keyboard-only navigation has not been walked end to end, only spot-checked. No testing at 200% zoom or on a real low-end Android device. Contrast was computed from the palette, which does not catch text sitting on an image or a gradient. Passing a contrast calculation is not the same as being usable, and this page should not be read as a claim of WCAG 2.2 AA conformance.

This is a prototype without a feedback backend yet (see Give feedback) — there's no way to route a report to anyone right now. Worth knowing regardless of whether it can be acted on immediately.