Accessibility statement

1. The aim

Sudhinam Chits wants sudhinamchits.com to be usable by as many people as possible, including people using a screen reader, navigating by keyboard, relying on magnification, or needing reduced motion or larger text.

We aim to meet the Web Content Accessibility Guidelines at level AA. That standard informs how the pages are built rather than being checked once at the end.

There is a specific reason to care on a site like this one. The pages that matter most explain money — an instalment, a discount, a dividend — to somebody deciding whether to commit for twenty months. A figure that a screen reader cannot announce properly, or a table that collapses into nonsense on a phone, is a page that has failed at the only thing it was for.

2. What has been done

Pages are built from semantic HTML with one main heading each and a heading order that follows the content. Every page opens with a skip link so a keyboard user reaches the main content without going through the navigation.

Controls are real buttons and links with visible focus outlines, accessible names and keyboard operation. The navigation, the question-and-answer accordions, the enquiry form and the calculator all work without a mouse.

The calculator uses genuine form fields with persistent visible labels, numeric input modes so phones show a number keypad, and a results region that announces itself when the figures change, so a screen-reader user hears the new payout rather than having to hunt for it. Its error message is announced too.

Figures use tabular numerals so columns of rupees line up, images carry alternative text describing what they show, colour is never the only way information is conveyed, the layout reflows to a single readable column on small screens, and animation respects the reduced-motion preference set in the operating system.

Every text and background pair has been measured against the surface it is actually rendered on, including muted copy, tinted cards and the pale bands, and none falls below the ratio the standard requires.

3. Known limitations

We publish this because a statement that claims perfection is not believable.

Material linked from this site but published elsewhere — the text of the law, public registers — is outside our control and may not meet the same standard. Those sources are chosen for authority.

Long articles use a table of contents and a contextual side panel on wide screens. Both are additions rather than requirements: the article stays complete and in a sensible order when they collapse on a phone or are skipped by assistive technology.

Where we find a barrier we record it and fix it in the ordinary course of maintaining the site.

4. Telling us

If you hit a barrier here, write to sudhinamchits@gmail.com. It helps to know which page, what you were trying to do, and the browser and assistive technology you were using — but a short description is far better than nothing at all.

We aim to acknowledge accessibility reports as quickly as any other enquiry, and to say what can be fixed and when. Where something cannot be fixed quickly we will find another way to give you the information.

If you would like anything on this site in a different format, or explained in person at the office, ask.

5. Maintenance

This statement describes the position on the date at its head, is reviewed when the site changes materially, and is revised when a limitation is resolved or a new one is found.

Accessibility work here is part of building a page rather than an audit run afterwards, which is why this statement describes measures rather than a certificate.