Gouri by Clarity

Accessibility statement

Last reviewed 5 October 2026.

Gouri is built to be used by everyone who works in the institution, including people who use a keyboard instead of a mouse, a screen reader, magnification, high-contrast settings or a phone. It is designed to meet the Web Content Accessibility Guidelines 2.1 at level AA and the Guidelines for Indian Government Websites 3.0.

Using Gouri

• Everything can be done with a keyboard. Alt with a number opens a section; j and k move between entries on the page; Alt with / lists every key.
• Pages work with screen readers: every control is labelled, headings are in order, and when a section opens, focus moves to its heading.
• Text can be enlarged to 200% and the page reflows to a single column, down to the width of a phone.
• Gouri follows your device's dark mode, reduced-motion and high-contrast settings.
• Nothing is conveyed by colour alone; every status is also written in words.
• Anything that commits you — signing a note, sending a reply, releasing a report — asks you to confirm first, and tells you what will happen.

What is not yet right

• The interface is in English only. Hindi, and the language of each state that requires it, will follow once Hindi drafting has been evaluated to the same standard as English.
• Drafted notes and plans are written by the engine and may use official phrasing that is harder to read than the rest of the interface. The person who signs can change any of it.
• Documents you upload are shown as they arrived. A scanned page with no text layer cannot be read by a screen reader until it has been read by the engine; the text it extracted is shown alongside it.

Tell us

If anything in Gouri is hard to use, or you need information in another form, tell the web information manager this institution has named for Gouri. Say what you were trying to do and which page you were on. You should hear back within five working days.

How this was checked

Every release is checked by automated tests that compute the colour contrast of every pairing, refuse unlabelled controls, inline styles and outside requests, and by an audit that opens every page and checks headings, landmarks, names, focus, target sizes and reflow. The checklist mapping each requirement to its check is kept with the product's records.