Access to SAARTHI should work for every educator.
This statement explains our accessibility target, the limitations we currently know about, and how to request help or an accessible alternative.
Our commitment
A clear accessibility target
SAARTHI targets WCAG 2.2 Level AA for release-critical web journeys and generated documents. Accessibility is part of design, engineering, content review, and release acceptance—not a one-time check.
Keyboard access
Release-critical journeys are designed for keyboard operation with visible focus and a skip link.
Responsive presentation
Core pages are designed to reflow on mobile screens and at enlarged browser zoom.
Readable structure
We use semantic headings, labelled controls, text alternatives, and non-colour status cues.
Language access
Hindi and English parity is a release target. Terminology remains subject to the approved language review.
Known limitations
Issues still being remediated
We publish these limitations so users can make an informed choice and request an alternative. They remain release-gate work, not accepted permanent exceptions.
- Some legacy pages are still being checked for duplicate landmarks, unnamed controls, and undersized touch targets.
- Some generated PDF files are still undergoing Hindi-font, reading-order, tagging, and assistive-technology validation.
- Full Hindi and English parity has not yet been verified across every workflow and download.
- Offline assessment recovery cannot be accepted until the released instrument passes the full disconnect-and-resume test.
Assisted use
Tell us what is blocking you
You can report an accessibility barrier or ask for content in an alternative format. Please do not include passwords, one-time codes, assessment answers, or private evidence in your message.
Helpful details to include
The page or file, what you were trying to do, the browser or device, any assistive technology used, and the alternative format or response method you prefer.
Response process
How an accessibility request is handled
- Step 1
Record
The request is logged without collecting unnecessary personal or assessment data.
- Step 2
Triage
The team identifies the affected journey, severity, and a suitable accessible alternative.
- Step 3
Respond
Support shares the alternative or next action through the contact route you provided.
- Step 4
Remediate
The underlying issue is tracked, tested, and included in release evidence when corrected.
हिंदी सारांश
SAARTHI का लक्ष्य महत्वपूर्ण वेब प्रक्रियाओं और दस्तावेज़ों के लिए WCAG 2.2 स्तर AA है। औपचारिक अनुरूपता परीक्षण अभी जारी है। यदि किसी पृष्ठ, नियंत्रण या दस्तावेज़ का उपयोग करने में बाधा हो, तो सहायता फ़ॉर्म या ईमेल के माध्यम से सुलभ विकल्प माँगें। संदेश में पासवर्ड, OTP, मूल्यांकन उत्तर या निजी साक्ष्य न भेजें।
हिंदी शब्दावली की अधिकृत समीक्षा अभी लंबित है।
We review this statement whenever a material accessibility issue is identified, the platform changes, or an applicable standard is updated. Verified improvements and known limitations are reflected here.