Accessibility statement — the DPDPNiti web application (legal review pending — see note)
Measured on 4 October 2026 against commit d14b1ac1. We update this page whenever the lists below change.
Last updated 4 October 2026* Legal review pending
We want people who use a keyboard, a screen reader or magnification to be able to use the application. It has not been audited by an independent accessibility specialist, and we do not claim conformance with WCAG 2.2 level AA or with any other standard. What follows comes from reading our code and from a contrast script that runs against our design colours.
What the application does today
- The page language is declared, and the browser's zoom is not locked.
- Form fields are generally built with a visible text label. Error and status messages are announced to screen readers through live regions. Dialogs use the browser's native dialog element.
- Colour contrast, measured by script: of the 125 text-and-background colour pairs the script can read, none is below 4.5:1 (3:1 for large text). The keyboard focus ring measures 8.65:1 against white, and 9.59:1 against the dark header. For the form fields whose outline colour is set in our code, the outline measures 4.83:1 against white; WCAG asks for 3:1.
- A print stylesheet is provided.
Known to fall short
- There is no “skip to main content” link.
- Reduced-motion preferences are honoured in one component, not across the application.
- The application has a light theme only.
- Some outlines other than those of form fields are lighter than 3:1 against the page: the highlighted border on a selected choice card, the drop zone where evidence is uploaded, and the outline buttons.
- The script reads colours from our code. It cannot see a colour that depends on what sits behind an element, a hover or disabled state, or an image.
- We run no automated accessibility test other than that contrast script, and we have not tested systematically with a keyboard-only walk-through or with screen readers across browsers.
Tell us about a barrier
Write to connect_dpdpniti@azpiration.in (the contact address this site already publishes). Tell us the page, what you were trying to do and what got in the way.
Source of every figure above: apps/web/scripts/check-contrast.mjs on commit d14b1ac1; the sentences about labels, live regions, dialogs and language come from counting them in apps/web/src and apps/web/index.html (labels 277, live-region sites 146, native dialogs 70); the “falls short” items are counts of zero or one in the same code (skip link 0, motion-reduce 1).
See it against your own obligations
A walkthrough of the real product — the assessment, the controls, the evidence and the audit trail — with the roadmap shown as the roadmap.
Scheduling opens Calendly, a third party who will see what you enter there. Email reaches us directly and this site records nothing either way.