Manifest position 812 · CrUX rank bucket 1000
https://accounts.digitallocker.gov.in
Partial after retries
57 of 58 checks were judged conclusively. End-to-end account completion is blocked by the requirement for a real mobile/Aadhaar identity and OTP.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-mode screenshot is visually identical to light mode; the preference probe reports prefers-color-scheme: dark=true while body remains rgb(255,255,255) and computed color-scheme is normal. F01 medium: System dark-mode preference is ignored. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion probe sampled the carousel four times over 7.5s and its transform stayed unchanged; no Web Animations were active. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors mobile screenshot retains visible text, controls, borders and carousel actions. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no view-transition CSS and the representative routes are separate MPA documents. F02 low: Page changes are abrupt full-document navigations with no View Transition enhancement. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling or reveal behavior exists on the representative pages, so there is no scroll-linked implementation to assess. |
implement-natural-interactionsphysical-gestures | issues | high | The HAR and DOM show Swiper plus Owl Carousel scripts and no scroll-driven CSS; the mobile screenshot shows custom carousel controls. F03 low: Carousel interaction is implemented by two JavaScript carousel libraries rather than platform scroll snap. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | DOM styles show a fixed-top header; platform CSS inspection found no scroll-state/container treatment or scroll timeline. F04 low: The fixed header does not adapt to scroll state. |
provide-guided-navigationanchored-positioning | issues | high | The platform probe found two custom overlays, no popover/dialog elements, and no anchor positioning CSS. F05 low: Dropdowns and overlays rely on custom/Bootstrap positioning rather than resilient anchored primitives. |
provide-guided-navigationdirects-attention | pass | high | The ecosystem page presents a visible in-page section menu followed by a matching blue “Why DigiLocker?” heading; carousel actions are explicitly labeled. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The 360x800 login screenshot shows a fixed “DigiLocker is better on mobile app” banner occupying the bottom edge before interaction. F06 medium: The login page opens with a fixed app-download banner covering the bottom of the primary flow. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The platform probe counted custom .modal/.dropdown-menu overlays but zero dialog, popover, or details elements. F07 medium: Transient UI is built from custom modal/dropdown markup instead of semantic primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Homepage, content and login screenshots devote the dominant viewport area to task/content; persistent chrome is compact. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The 360px layout capture reports scrollWidth 374px and horizontalOverflowPx 14. F08 medium: The home page overflows horizontally on a narrow viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Live CSS inspection found no @container rules or container-type on the page. F09 low: Reusable cards and carousels respond only to viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe focused header controls and CTAs; computed outline was none and box-shadow none. Several header buttons are only 30x30px. F10 high: Keyboard focus is not visibly indicated on primary controls. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage exposes Login/Register and document exploration; login page states “Login or Create Account” and asks for the single next input. |
support-core-task-successprimary-flow-completion | blocked | high | End-to-end account access requires a real Indian mobile/Aadhaar identity and OTP. The public flow was attempted through the required phone field, but no test credential was available. |
support-core-task-successclear-system-state-and-recovery | issues | high | Submitting the empty required mobile field yields only the browser validationMessage; aria-invalid and aria-describedby remain absent and the page error region is empty. F11 medium: Invalid login input is not exposed as an actionable accessible error. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 7.3s and CLS 0.342 (performance score 0.53); the independent trace measured LCP 2.16s, showing substantial run variability but corroborating late visual work. F12 high: Cold mobile performance is outside the good Core Web Vitals range. |
be-fast-and-stablevisual-stability | issues | high | Mobile layout observation measured CLS 0.158; Lighthouse measured 0.342 and identifies unsized carousel and accessibility-widget images as culprits. The image audit found 88 of 89 images without dimensions. F13 high: Unsized images and late widget/carousel insertion cause visible layout shift. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded one 57.76ms long task and only 7.76ms total blocking time; Lighthouse TBT was 0ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR shows five VeryHigh-priority parser stylesheets and a synchronous Swiper script in head; many large CDN resources have no cache header. Lighthouse reports a 2.795s longest dependency chain. F14 high: The critical path includes blocking scripts/styles and ineffective caching. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR records Swiper and Owl Carousel plus jQuery, Bootstrap, Popper, Font Awesome, chatbot and accessibility bundles; script transfer is 207KB and a 158KB icon font is loaded. F15 medium: Two carousel libraries and broad UI bundles are shipped for one landing page. |
be-inclusivenames-roles-labels | issues | high | Lighthouse reports an unnamed accessibility-widget close button, an unlabeled menu checkbox and an image without alt; the image audit found six missing alt attributes. The login mobile field has no associated label. F16 high: Important controls and images lack accessible names or labels. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed and forced-colors screenshot preserves readable text/control boundaries. |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports no main landmark, nonsequential heading order, role=presentation conflicts and tabindex=1. The home page has no h1; content pages also omit main landmarks. F17 high: Landmark, heading, role and focus structure is invalid. |
be-inclusivelegible-text | pass | high | Mobile screenshots show readable body text, clear spacing, and no clipping on content/login templates. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Viewport allows scaling, Lighthouse meta-viewport and target-size audits pass, and login/content templates have no horizontal overflow at 360px. No time-based media requiring captions appears. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no logged errors. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse confirms doctype/charset and aspect-ratio rendering, but the dedicated image audit found 88/89 images without dimensions, 11 oversized images and 23 without responsive sources. F18 medium: Image markup is structurally incomplete despite a valid document shell. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse’s inspector-issues audit identifies a cookie issue on the aistore.myscheme.in embedded resource. F19 low: Chrome records an inspector issue from an embedded third-party response. |
be-discoverabletitle-and-description | pass | high | Homepage has a descriptive title and meta description in both raw and rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse reports javascript:void(0) anchors; recon enumerates multiple empty-text links and social links implemented as script-triggered placeholders. F20 medium: Some links are not crawlable and many icon links have no descriptive text. |
be-discoverablecanonical-and-indexing-signals | issues | high | Direct requests to both /robots.txt and /sitemap.xml return HTTP 403 AccessDenied while the page declares index,follow. F21 medium: robots.txt and sitemap.xml are inaccessible. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage includes accurate WebSite, GovernmentOrganization and GovernmentService JSON-LD plus Open Graph and Twitter metadata matching visible DigiLocker content. |
be-private-and-securesecure-transport-and-headers | issues | high | Header inspection finds a CSP but script-src includes unsafe-eval and style-src includes unsafe-inline, weakening XSS protection on an identity service. F22 high: The Content Security Policy permits unsafe script evaluation. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Network capture found no known trackers, no exposed secrets and one secure first-party preference cookie; observed third parties are DigiLocker/government service infrastructure. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login page exposes only a telephone form; source probe found no navigator.credentials/WebAuthn integration. No permission prompt fires on load. F23 high: The public authentication entry offers phone OTP only, with no phishing-resistant sign-in option. |
be-private-and-securedefensive-browser-policies | issues | high | Although HSTS, nosniff, X-Frame-Options, Referrer-Policy and Permissions-Policy are present, CSP frame-ancestors permits numerous wildcard domains and the policy relies on unsafe-eval/unsafe-inline. F24 medium: Browser defenses are broad rather than least-privilege. |
be-resilientprogressive-enhancement | pass | high | Raw HTML is a substantive 71KB document with 68% rendered-word coverage, title and description; crawler screenshot retains the main public content rather than an empty JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | The live DOM contains custom modal/dropdown UI but no dialog, popover or anchor-positioning primitives. F25 medium: Custom overlays are not using resilient top-layer and fallback positioning. |
be-resilientoffline-and-installable | issues | high | The platform probe found zero service-worker registrations and recon found no web app manifest, despite mobile-web-app-capable metadata. F26 medium: The app-like service is neither installable nor backed by an offline fallback. |
be-resilientnetwork-and-http-failure-states | issues | high | A representative bad route renders a bare XML AccessDenied response with no title, navigation, explanation, or route back to DigiLocker. F27 high: Unknown routes expose raw infrastructure errors with no recovery. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares html lang=en, exposes 13 Indian language options, and CSS inspection found logical properties. |
be-internationalisedlocale-aware-data | issues | high | After activating the Hindi option and waiting, html lang remained en and “Last Updated” remained in English. F28 medium: The visible language control did not switch locale during the probe and the date remained English. |
be-internationalisedtime-zone-correctness | not-applicable | high | Representative public pages contain no event scheduling, time-zone conversion, recurring event or partial-time concept. |
be-trustworthyno-dark-patterns | pass | high | The public login entry states the action and Terms of Service before continuation; OTP/Aadhaar alternatives and app-promo dismissal are visible, with no preselected paid continuity. |
be-trustworthyhumane-error-handling | issues | high | Submitting the empty required mobile field yields only the browser validationMessage; aria-invalid and aria-describedby remain absent and the page error region is empty. F11 medium: Invalid login input is not exposed as an actionable accessible error. |
be-trustworthytrustworthy-input-assistance | issues | high | The login probe reports autocomplete=off and an empty labels collection for the required telephone field. F29 high: The mobile number field disables autofill and has no label. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The login page exposes only a telephone form; source probe found no navigator.credentials/WebAuthn integration. No permission prompt fires on load. F23 high: The public authentication entry offers phone OTP only, with no phishing-resistant sign-in option. |
be-sustainableoptimised-assets | issues | high | The image audit found 11 oversized images, 21 legacy-format images and 23 images without srcset; four 2280px JPEG banners transfer about 890KB combined. F30 medium: Landing-page imagery is oversized and uses legacy formats without responsive selection. |
be-sustainableno-wasteful-work | pass | high | Trace observed negligible blocking work and tracker scan found no known analytics trackers; the load performs three task-related fetches without ongoing media playback. |
be-sustainablethird-party-and-media-budget | issues | high | HAR records Swiper and Owl Carousel plus jQuery, Bootstrap, Popper, Font Awesome, chatbot and accessibility bundles; script transfer is 207KB and a 158KB icon font is loaded. The image audit found 11 oversized images, 21 legacy-format images and 23 images without srcset; four 2280px JPEG banners transfer about 890KB combined. F15 medium: Two carousel libraries and broad UI bundles are shipped for one landing page. F30 medium: Landing-page imagery is oversized and uses legacy formats without responsive selection. |
be-agent-readystructured-agent-capabilities | issues | high | Discoverability shows content is crawlable, but the platform probe found no WebMCP registration and Lighthouse agentic-browsing scored 0.17. F31 low: A high-value document service exposes no structured agent capability. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generative feature is presented to users; introducing on-device inference would not currently serve an identified task. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten menu open/close cycles, heap self-size fell from 12,186,171 to 12,034,364 bytes and node count fell from 184,871 to 184,836. |
be-memory-efficientbounded-footprint | pass | high | Single-page heap is about 12.2MB across 184,871 snapshot nodes, proportionate to this image/card landing page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Ten menu cycles produced no node-count growth (35 fewer nodes) and no growing Detached* constructor appears in top constructor summaries. |
Provenance
Canonical report: results/atomic/reports/0812-accounts_digitallocker_gov_in.json
Report SHA-256: dcc6032edf5d21a3d0f2dbd677e4c39c79dcb780f32609d92a4486403cc2e276
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/accounts_digitallocker_gov_in/2026-07-28T07-53-58-817Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/accounts_digitallocker_gov_in/2026-07-28T07-53-58-817Z
Catalog SHA-256: sha256:78ccfdb2d483f4c57d9dafed80fd86c6265585a56457c8dcfddc254b80fb44d7
Raw screenshots, HARs, traces, heaps, and other browser artifacts are retained at the local evidence root and intentionally are not committed. Artifact paths in the canonical report are relative to that root.