Manifest position 758 · CrUX rank bucket 1000

https://lottery.sambad.com

Coverage complete

Atomic coverage complete across 58 checks and five representative paths. Not covered: authenticated account completion, camera scanning hardware, payment/prize-claim workflows, and the separate /pwa/ shell because they require credentials, device permissions or represent a distinct scoped app.

Attempts

1 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	Pixel-identical light/dark screenshots and computed body #fff demonstrate no adaptation. F001 medium: The UI stays light when the user requests a dark colour scheme.
respect-user-preferences `respects-reduced-motion`	issues	high	Reduced-motion probe still found three running 2.8–3s animations. F002 medium: Loading animations continue under reduced-motion.
respect-user-preferences `respects-contrast`	issues	high	Contrast-emulated capture and CSS inspection found no preference handling. F003 low: High-contrast preferences receive no dedicated adaptation.
implement-natural-interactions `view-transitions`	issues	high	MPA/result navigation has no view-transition CSS. F004 low: Page and result-state changes use abrupt swaps rather than View Transitions.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	No parallax, scrollytelling, entry/exit reveal, or other scroll-linked animation exists on the representative templates, so there is no scroll handler/timeline implementation to assess.
implement-natural-interactions `physical-gestures`	pass	high	CSS inspection found scroll-snap and the tested controls use native scrolling/click semantics without custom pointer-drag handlers.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	The 8,988px mobile page has no scroll-state/progress treatment. F005 low: Long pages provide no scroll-state-aware navigation cue.
provide-guided-navigation `anchored-positioning`	not-applicable	high	The tested templates expose no tooltip or edge-attached transient menu that requires anchor positioning; the navigation drawer is viewport chrome.
provide-guided-navigation `directs-attention`	pass	high	Breadcrumbs on the article, explicit draw tabs, dates and selected-state colour consistently orient the tested journeys.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	Fresh result route was obscured by the captured consent wall. F006 high: A consent wall obscures the primary result on a fresh visit.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	Consent UI is custom, creates extra h1s and uses no dialog/popover. F007 medium: The consent overlay is custom chrome rather than a semantic dialog.
maximize-content-reduce-noise `reduced-chrome`	pass	high	Screenshots show content-dominant layouts with compact top chrome and no persistent side rails.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	Layout measured 360px scrollWidth/clientWidth and zero horizontal overflow; viewport meta is present.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	No container query declarations were found on reused result/card modules. F008 low: Reusable cards adapt only through global layout rules, not container queries.
adapt-to-the-form-factor `input-modality-aware`	issues	high	Focused search input had no outline or shadow; multiple visible controls were under 24px in one dimension. F009 high: Keyboard focus can be invisible and several controls have undersized hit areas.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	First viewport identifies today’s result, draw tabs, ticket area and scan action clearly.
support-core-task-success `primary-flow-completion`	pass	high	Entering 56215 and pressing Search produced a specific first-prize match and series guidance.
support-core-task-success `clear-system-state-and-recovery`	pass	high	Invalid search shows a direct five-digit correction; valid search replaces it with a result; 404 offers a homepage recovery link.
be-fast-and-stable `good-core-web-vitals`	pass	high	Lighthouse measured LCP 1.1s, CLS 0 and TBT 0ms; trace measured FCP/LCP 516ms and zero blocking.
be-fast-and-stable `visual-stability`	pass	high	Both layout observers measured CLS 0 and no shifts over five seconds.
be-fast-and-stable `efficient-main-thread`	pass	high	Trace and layout observers found no long tasks and 0ms total blocking time.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR recorded 9 requests, 61KB transferred, no render-blocking candidates, redirects or HTTP errors; one image optimization gap remains separately recorded. F010 low: One below-fold example image lacks intrinsic dimensions and is oversized.
be-fast-and-stable `trim-unused-and-duplicate-code`	pass	high	Lighthouse unused JS/CSS audits passed and the HAR contains no third-party script payload.
be-inclusive `names-roles-labels`	issues	high	Primary ticket input and hidden auth fields rely on placeholders; #srch has no label or accessible naming attribute. F011 high: The primary ticket-number field has no programmatic label.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse/axe enumerated eight failing colour combinations with ratios as low as 1.84:1. F012 high: Multiple text and control combinations fail WCAG contrast.
be-inclusive `structure-and-focus`	issues	high	No main landmark is present and the focused primary input has no visible focus treatment. F013 medium: The homepage lacks a main landmark and focus styling.
be-inclusive `legible-text`	pass	high	Mobile screenshots show readable 16–18px body copy, comfortable article line length and no clipping.
be-inclusive `zoom-reflow-targets-and-media`	pass	high	360px reflow has no overflow and viewport permits scaling; no time-based media requires captions, though undersized controls are recorded.
follow-best-practices `no-console-errors`	pass	high	Lighthouse observed no browser console errors or uncaught exceptions.
follow-best-practices `sound-document-and-assets`	pass	high	HTML doctype, UTF-8 charset and modern AVIF/WebP assets are present; the one missing intrinsic image size is separately recorded.
follow-best-practices `browser-platform-hygiene`	pass	high	Lighthouse passed deprecation, BFCache, console and source-map diagnostics; no permission prompt appeared on load.
be-discoverable `title-and-description`	pass	high	All four representative content templates expose unique descriptive titles and descriptions.
be-discoverable `crawlable-and-mobile-friendly`	pass	high	Real href links, viewport meta and permissive robots.txt were directly observed.
be-discoverable `canonical-and-indexing-signals`	pass	high	200 pages expose matching canonicals; robots allows crawling and declares three sitemaps with current result URLs.
be-discoverable `structured-and-shareable-metadata`	pass	high	Homepage/listing JSON-LD and article Article JSON-LD plus 12 Open Graph tags accurately match visible content.
be-private-and-secure `secure-transport-and-headers`	issues	high	HTTPS/cookies are secure, but CSP is missing. F014 medium: Browser-enforced security policy is incomplete.
be-private-and-secure `data-minimisation-and-third-parties`	pass	high	HAR found zero third-party requests/bytes, tracker scan found no known tracker and the only analytics call is a small first-party pageview request.
be-private-and-secure `in-context-permissions-and-modern-auth`	pass	medium	No permission prompt appears on load; authentication is delegated to Google rather than an exposed password-only primary flow.
be-private-and-secure `defensive-browser-policies`	pass	high	HSTS, SAMEORIGIN, nosniff and strict-origin referrer policy pass, but CSP and Permissions-Policy are absent.
be-resilient `progressive-enhancement`	pass	high	Discoverability measured 100% content coverage without JavaScript on homepage and article, with title/h1/description intact.
be-resilient `resilient-runtime-behaviour`	pass	high	Native links/forms and the tested disclosure/search states remained stable; mobile captures show no clipped core menu or result controls.
be-resilient `offline-and-installable`	issues	high	Manifest is complete, but the audited public page has no controlling service worker/offline evidence. F015 medium: The public app surface is not controlled by a service worker.
be-resilient `network-and-http-failure-states`	pass	high	Unknown route renders a concise 404 with an actionable homepage link; invalid search provides retry guidance.
be-internationalised `lang-dir-and-logical-properties`	issues	high	lang=en-IN is correct, but dir and logical CSS properties are absent and physical positioning is common. F016 low: Direction and logical layout support are incomplete.
be-internationalised `locale-aware-data`	pass	medium	Visible dates, rupee amounts and draw times are consistently formatted for the declared en-IN audience; no mixed-locale output was observed.
be-internationalised `time-zone-correctness`	not-applicable	high	The audited content publishes fixed local draw schedules and dates, not user-specific or cross-time-zone events; no DST-sensitive workflow exists.
be-trustworthy `no-dark-patterns`	issues	high	Consent first layer has accept/manage but no equivalent reject control. F017 high: Consent choices are asymmetrical on the first layer.
be-trustworthy `humane-error-handling`	issues	high	Search error is understandable but lacks aria-invalid, description linkage and live announcement. F018 medium: Ticket-search validation is visual only and not announced.
be-trustworthy `trustworthy-input-assistance`	pass	high	Auth fields use email/new-password/current-password tokens; ticket number intentionally disables irrelevant autofill and constrains numeric input.
be-trustworthy `safe-commercial-and-account-flows`	pass	high	The consent flow is not proportionate because refusal is hidden behind Manage options.
be-sustainable `optimised-assets`	issues	high	Image audit found missing responsive delivery, dimensions and lazy loading on below-fold assets. F019 low: Below-fold image delivery wastes avoidable bytes/work.
be-sustainable `no-wasteful-work`	pass	high	HAR has only 9 requests/61KB, trace has no long tasks, and no third-party background work was observed.
be-sustainable `third-party-and-media-budget`	pass	high	No third-party bytes, fonts, video, audio or autoplay media were loaded; all active network traffic was first party.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	No declared agent-facing surface exists. The public content is crawlable and the emerging WebMCP opportunity is not treated as an obligation.
be-agent-ready `on-device-inference`	not-applicable	high	No summarisation or generative task is part of the site’s core result-checking flow, so built-in AI would add no necessary user value.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After 100 open/close disclosure cycles in one session, JS heap, DOM node count and animation count each had delta 0.
be-memory-efficient `bounded-footprint`	pass	high	Baseline heap was 3.51MB across 60,326 nodes and runtime DOM contained 663 elements, proportionate to the long content page.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	medium	One-session 100-cycle probe kept DOM and animation counts unchanged; heap post snapshot remained small (3.81MB) with no unbounded trend.

Provenance

Canonical report: results/atomic/reports/0758-lottery_sambad_com.json
Report SHA-256: dbcdc6403cb345baade6b45c5c3fa0049e92360296198ee7cc8a0dc55f7dcc17
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/lottery_sambad_com/2026-07-22T21-17-49-292Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/lottery_sambad_com/2026-07-22T21-17-49-292Z
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.