Skip to content
LEGAL

Accessibility

Where we are on WCAG 2.1 AA, what assistive tech we test against, and what we know is still rough. Honest list — please report what we missed.

Last updated: 2026-09-08

On this page

1. Our commitment

In plain English: We are working toward WCAG 2.1 AA across the web and mobile apps.

MyPanditji is committed to making the Service usable for the widest possible audience, including people with visual, motor, auditory or cognitive impairments. We follow the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA conformance level as our target across the web app, the mobile apps, and the marketing site.

2. What is already in place

In plain English: Skip-to-content, 4.5:1 contrast, large tap targets, semantic landmarks, focus rings, screen-reader labels on every interactive element.

Across the Service today:

A skip-to-content link is the first focusable element on every page and meets the WCAG 2.5.5 44×44 px tap-target rule.
Body text meets a 4.5:1 contrast ratio against its background; large text meets at least 3:1.
All interactive controls have an accessible name (aria-label or visible text), a visible focus indicator, and a target size of at least 44×44 px on touch surfaces.
Landmarks (header, nav, main, footer) are present on every page; lists and headings are used semantically.
Form fields use programmatically associated labels and inline error messages.
Animations honour the user’s `prefers-reduced-motion` setting via Framer Motion’s built-in handling; non-essential motion is replaced with a static end state when reduced motion is requested.
Images that convey information have descriptive `alt` text; decorative images are marked `aria-hidden`.

3. Tested assistive technologies

In plain English: We test on the screen readers and zoom levels real users actually use.

Our regular accessibility test pass covers:

macOS VoiceOver + Safari and Chrome
iOS VoiceOver + Safari
Android TalkBack + Chrome
NVDA + Firefox on Windows
Browser zoom up to 200% without loss of content
Keyboard-only navigation on web

If you use a different assistive technology and run into trouble, please tell us — testing is iterative and your report makes the next pass better.

4. Known issues we are working on

In plain English: No app is perfectly accessible. Here is the open list, written honestly.

We track open accessibility issues openly. Current known issues include:

Some animated motion graphics on the marketing pages (constellation field, orbiting mandala) are aria-hidden but their surrounding sections still load extra JS; we plan to inline-defer them for slower devices.
The chat thread’s long-message virtualisation can occasionally cause screen readers to re-announce earlier messages on scroll; a stable announcement region is in build.
Some Devanagari-only content on the dashboard is not yet exposed with a `lang="hi"` attribute, which can affect screen-reader pronunciation.

If you find an issue not listed here, please write to support@mypanditji.io.

5. Contact us

In plain English: Email support@mypanditji.io with your device, OS, assistive tech, and what went wrong. We respond within 5 working days.

For accessibility feedback, alternative-format requests, or to report a barrier you encountered, email support@mypanditji.io. Where helpful, include:

The URL or screen where the issue occurred.
Your device, operating system, browser, and assistive technology versions.
A short description of what you expected and what happened.

We aim to acknowledge accessibility reports within two business days and to substantively respond within five.