Manifest position 708 · CrUX rank bucket 1000
https://evikas.mpkrishi.mp.gov.in
Coverage complete
Atomic coverage complete across 58/58 checks. Representative public templates and the primary registration surface were inspected; authenticated/real-identity submission and external admin login were not covered.
Attempts
2 / 3
Judged checks
58 / 58
Blocked
0
Not run
0
This report has no published overall score. Blocked and not-run checks are not passes. A coverage-complete report means every check has a judged outcome; it does not mean every check passed.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Under prefers-color-scheme: dark, the dark probe still measured the body as rgb(255,255,255) with rgb(33,37,41) text, and the screenshot remained light. F01 medium: The interface ignores the system color scheme. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found six of seven animations still running, including ripple, aiGlow, slideroll and slide; only the scroll animation paused. F02 medium: Most continuous animation remains active when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | DOM/CSS inspection found no contrast preference or forced-colors adaptation, while the site relies on pale green/orange decorative treatments. F03 low: No high-contrast adaptation is evident. |
implement-natural-interactionsview-transitions | issues | high | The inspected MPA pages use ordinary navigation and DOM/CSS inspection found no view-transition-name or @view-transition rules. F04 low: Primary route changes have no continuity. |
implement-natural-interactionsscroll-driven-animations | issues | high | The animation probe found long-running CSS animations (3–15 seconds), but no authored animation-timeline usage was found. F05 low: Animations are timer-driven rather than scroll/state-driven. |
implement-natural-interactionsphysical-gestures | issues | high | Visual and DOM inspection found click handlers and generic Bootstrap animation, but no snap, gesture, overscroll or physics-based interaction on the card-heavy landing surface. F06 low: Interactive cards and media do not provide natural direct-manipulation feedback. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The mobile landing page is 4,315 CSS pixels tall, while the screenshot shows a full-height modal and no page progress or clear continuation cue. F07 medium: Long mobile pages provide weak progress and continuation cues. |
provide-guided-navigationanchored-positioning | not-applicable | medium | No tooltip, contextual menu, anchored popover, or other floating control requiring anchor-relative positioning appears on the representative paths. |
provide-guided-navigationdirects-attention | issues | high | Both desktop and mobile first views are blocked by a large modal before the user can see or choose the main registration and tracking tasks. F08 high: Attention is captured by an automatic notice instead of guided toward the primary service. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The first screenshot at both viewport sizes shows a modal and backdrop covering the page; the notice is lengthy and not tied to a user action. F09 high: An unsolicited modal blocks all landing-page content on every fresh load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The semantic probe found the visible role=dialog had neither aria-label nor aria-labelledby; Lighthouse also failed aria-dialog-name. F10 medium: The notice dialog is unnamed and implemented as a generic role-based container. |
maximize-content-reduce-noisereduced-chrome | issues | high | The clear-page and crawler screenshots show banners, portraits, ticker, video control, floating accessibility control and multiple card treatments before core tasks; the automatic modal adds another layer. F11 medium: Competing decorative chrome obscures the core services. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Mobile layout captures at 360×800 reported 0px horizontal overflow on home, registration and tracking. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The probe found zero stylesheets containing @container; the same card/form components are tightly coupled to page-width utility classes such as w-50. F12 low: Responsiveness is viewport-only rather than component-aware. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The form probes found 19–23px-high links/radios and many controls without programmatic labels; focus was visible, but target size remains small. F13 medium: Several interactive targets are below recommended touch size and field labeling is fragile. |
support-core-task-successclear-purpose-and-primary-action | issues | high | At first load, the registration and tracking actions are outside the visible interaction layer because the automatic notice occupies the viewport. F14 high: The landing page hides its primary purpose and actions behind a notice. |
support-core-task-successprimary-flow-completion | issues | high | The registration DOM contains duplicate id values (OtpType, aadharNo, chk_OTP), 14 unlabeled controls, and onpaste handlers on Aadhaar inputs, undermining reliable completion and assistive technology. F15 high: The primary identity flow uses duplicate IDs, inaccessible controls and blocked paste. |
support-core-task-successclear-system-state-and-recovery | issues | high | The tracking page reports that home delivery is unavailable as static body copy, and the primary form controls lack the labeling/error associations needed for actionable validation recovery. F16 high: Service and validation states lack robust recovery semantics. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 8.4s, FCP 4.3s and TTI 9.5s (performance 0.63); the local trace corroborated 2.27s FCP/LCP on the faster unthrottled run. F17 high: Mobile loading performance is poor. |
be-fast-and-stablevisual-stability | issues | high | The images audit found all 14 images missing complete width/height dimensions; mobile CLS was 0.061 and showed many late shifts. F18 medium: Images do not reserve intrinsic layout space. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse estimated 293 KiB unused JavaScript; the trace recorded a 96.9ms long task and 46.9ms TBT. F19 high: The page ships substantial unused JS and records long work. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 56 requests and 1.78MB transferred, including 384KB third-party fonts; seven parser-inserted stylesheets and synchronous scripts were confirmed by HAR and the DOM probe. F20 high: Resource delivery is heavy and render-blocking. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 179 KiB unused CSS and 293 KiB unused JS, including 99.9% of animate.min.css and 88.8% of fancybox.umd.js. F21 medium: Most framework CSS and several libraries are unused on the landing route. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed dialog name, image alt and link name checks; the registration probe found 14 unlabeled controls and the images audit found two missing alt values. F22 high: Names, roles and labels are incomplete across key paths. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed on the rendered landing page. |
be-inclusivestructure-and-focus | issues | high | The home page has no doctype, lang, h1, main or nav; Lighthouse failed heading order and positive tabindex checks. F23 high: Document structure is malformed for assistive navigation. |
be-inclusivelegible-text | pass | high | Mobile screenshots show readable Devanagari body text with adequate line spacing on forms and content pages. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport uses maximum-scale=1; Lighthouse failed meta-viewport and the form probes found interactive targets only 19–23px high. F24 high: The viewport configuration restricts zoom and touch targets are too small. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit reported no console errors. |
follow-best-practicessound-document-and-assets | issues | high | The DOM probe found no doctype and Lighthouse failed the doctype audit; the image audit found 14/14 images without complete intrinsic dimensions. F25 medium: The entry document is in quirks mode and image markup omits intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | The viewport caps zoom, Aadhaar fields block paste, and all seven external scripts are classic synchronous scripts without async/defer/module. F26 medium: The page disables user capabilities and relies on legacy synchronous libraries. |
be-discoverabletitle-and-description | issues | high | Home, registration, tracking, about and privacy DOM captures all use “ई-विकास प्रणाली”; descriptions use the internal acronym “MP-FDCMS”. F27 medium: Every inspected route reuses a generic title and opaque description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The probe found visible anchors without href and href="#" placeholders; Lighthouse failed crawlable-anchors. Raw HTML coverage was only 15%, despite not being an empty JS shell. F28 high: Many visible links are not crawlable and crawler-visible content coverage is low. |
be-discoverablecanonical-and-indexing-signals | issues | high | The metadata probe found no canonical or robots meta; /robots.txt and /sitemap.xml returned the site’s HTML 404 page rather than valid files. F29 medium: Canonical, robots and sitemap signals are absent. |
be-discoverablestructured-and-shareable-metadata | issues | high | The probe found zero JSON-LD scripts and zero Open Graph tags on the landing page. F30 medium: The site provides no structured or social metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers include HTTPS, HSTS and nosniff, but CSP script-src allows unsafe-inline and unsafe-eval; Permissions-Policy is missing. F31 high: The CSP permits unsafe script execution and Permissions-Policy is absent. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Trackers found no known tracker domains; cookies found zero cookies and secrets found no exposed credentials. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No browser permission prompt was triggered on any inspected path, and identity is requested only inside the user-opened registration flow. |
be-private-and-securedefensive-browser-policies | issues | high | The headers audit found no Permissions-Policy and a weakened CSP, although frame and referrer protections were present. F32 medium: Browser policy hardening is incomplete. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 15% overlap between rendered content words and raw HTML; crawler and rendered views differ materially. F33 high: Most rendered content is not represented as equivalent raw HTML. |
be-resilientresilient-runtime-behaviour | pass | high | All five representative routes loaded without runtime failure; modal dismissal, focus, and responsive layout remained operational. |
be-resilientoffline-and-installable | not-applicable | medium | This live government transaction portal does not declare offline/installable intent; authoritative identity and stock operations require current server data. |
be-resilientnetwork-and-http-failure-states | issues | high | The tracking path displays an unavailable-service paragraph without retry, status timestamp, or alternative action; requested robots/sitemap paths return generic framework 404 HTML. F34 medium: Failure and unavailable-service states do not offer recovery actions. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The Hindi home page has no lang attribute; inner routes declare lang="Eng", which is not a valid BCP 47 code and does not match the predominantly Hindi UI. F35 high: Language declarations are missing or invalid across Hindi content. |
be-internationalisedlocale-aware-data | not-applicable | medium | Representative pages do not format dates, currency, measurements, or locale-sensitive numeric data. |
be-internationalisedtime-zone-correctness | not-applicable | medium | No scheduled user event or cross-time-zone date/time entry is exposed; the static “10:00” notice is explicitly local service information. |
be-trustworthyno-dark-patterns | issues | high | The notice appears without user initiation and blocks the task; Aadhaar fields attach onpaste handlers returning false. F36 medium: The forced notice and disabled paste reduce user control. |
be-trustworthyhumane-error-handling | issues | high | The registration controls lack programmatic labels, duplicate IDs and block paste; the tracking state gives no actionable retry. F37 high: Form constraints are enforced without accessible, humane feedback. |
be-trustworthytrustworthy-input-assistance | issues | high | Aadhaar fields use autocomplete="off" and onpaste=false; several controls lack labels and duplicate IDs. F38 high: The identity form disables useful input assistance. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | medium | No checkout, subscription, payment, cancellation, or authenticated account-management step was entered in the public representative scope. |
be-sustainableoptimised-assets | issues | high | The images audit found 12 legacy-format assets, three oversized images, six without srcset and eight below-fold images not lazy-loaded. F39 medium: Images are legacy, oversized and non-responsive. |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimated 472 KiB combined unused CSS/JS, while the reduced-motion probe found perpetual animations still running. F40 medium: The route downloads substantial code and animation work that is not needed for the core task. |
be-sustainablethird-party-and-media-budget | issues | high | HAR measured 1.78MB and 56 requests; 384KB came from third-party font origins and images transferred 581KB. F41 medium: Fonts and media lack a disciplined transfer budget. |
be-agent-readystructured-agent-capabilities | not-applicable | medium | No declared intent asks this public portal to expose WebMCP or agent-callable tools; ordinary semantic web/forms remain covered by other principles. |
be-agent-readyon-device-inference | not-applicable | medium | The inspected registration, tracking and policy tasks have no user-facing summarisation or language-model use case. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | Baseline versus post-interaction heap totals grew only 60,411 bytes (0.48%) and 299 nodes after ten modal hide/show cycles, with no Detached constructor among top retained entries. |
be-memory-efficientbounded-footprint | pass | high | Heap summary measured a 12.47MB baseline self-size for this bounded MPA page, proportionate to the observed surface. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Post-interaction heap summary showed no Detached DOM constructor among top retained entries and only bounded 0.48% total growth. |
Provenance
Canonical report: results/atomic/reports/0708-evikas_mpkrishi_mp_gov_in.json
Report SHA-256: a21a8e5592e07a9a024d39568ecb9c66411525e952ed95a769ed7f562b461c85
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/evikas_mpkrishi_mp_gov_in/2026-07-26T19-16-36-864Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/evikas_mpkrishi_mp_gov_in/2026-07-26T19-16-36-864Z
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.