uidai.gov.in
After a news story about Aadhaar data leaks, Suresh wants to lock his biometrics on the UIDAI site.
Who is trying to use this site
Essential tremor and moderate macular degeneration. Uses his phone at large text size, occasionally VoiceOver. Reads Telugu comfortably, English slowly.
What the automated audit found
Automated scanning is a floor, not a ceiling. Real assistive-technology testing by disabled users finds more problems, not fewer. Every finding here is a mechanical check on the site’s own markup, third-party widgets excluded. See the methodology and right of reply.
Findings, ranked by severity
A button has no accessible name; a screen reader will announce it as "button" with no purpose
axe · button-name · 4 elements · landingButtons must have discernible text. WCAG 2A. Deque rule reference.
The page has no top-level <h1>, so screen reader users cannot orient
axe · page-has-heading-one · 1 element · landingPage should contain a level-one heading. (WCAG mapping not surfaced by axe). Deque rule reference.
A scrollable region cannot be reached by keyboard
axe · scrollable-region-focusable · 1 element · landingScrollable region must have keyboard access. WCAG 2A, WCAG 211, WCAG 213. Deque rule reference.
A button has no accessible name; a screen reader will announce it as "button" with no purpose
axe · button-name · 4 elements · biometric-lock-serviceButtons must have discernible text. WCAG 2A. Deque rule reference.
The page has no top-level <h1>, so screen reader users cannot orient
axe · page-has-heading-one · 1 element · biometric-lock-servicePage should contain a level-one heading. (WCAG mapping not surfaced by axe). Deque rule reference.
A scrollable region cannot be reached by keyboard
axe · scrollable-region-focusable · 1 element · biometric-lock-serviceScrollable region must have keyboard access. WCAG 2A, WCAG 211, WCAG 213. Deque rule reference.