Manifest position 725 · CrUX rank bucket 1000
https://www.aajtak.in
Coverage complete
Coverage-complete model-led audit of five representative public-news paths. Not covered: authenticated/account and commercial flows (none exposed in representative public paths), live-video playback, and robots-disallowed search results.
Attempts
1 / 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 | Dark emulation remained a light white/grey surface and CSS inspection found no color-scheme support. F01 high: The interface ignores system appearance and motion preferences |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce active, two 40,000ms animations remained running; no reduced-motion CSS was present. F01 high: The interface ignores system appearance and motion preferences |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found contrast failures down to 1.82:1 and CSS inspection found no contrast/forced-colors adaptation. F01 high: The interface ignores system appearance and motion preferences |
implement-natural-interactionsview-transitions | issues | medium | CSS inspection found no view-transition usage across the multi-page navigation experience. F02 low: Navigation and carousel interactions use legacy abrupt/hand-rolled behavior |
implement-natural-interactionsscroll-driven-animations | issues | medium | No animation-timeline or scroll-timeline rules were present while the page implements long feeds and carousel motion. F02 low: Navigation and carousel interactions use legacy abrupt/hand-rolled behavior |
implement-natural-interactionsphysical-gestures | issues | medium | No scroll-snap/overscroll gesture primitive was found for the carousel-like story controls. F02 low: Navigation and carousel interactions use legacy abrupt/hand-rolled behavior |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | Long 17,004-24,694px pages expose no scroll-state/progress styling in the rendered CSS. F03 low: Navigation chrome does not expose modern position/state cues |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-sensitive anchored menu interaction was identified in the representative core reading paths. |
provide-guided-navigationdirects-attention | issues | medium | No view-transition, highlight, or directional-transition treatment was found for route/state changes. F03 low: Navigation chrome does not expose modern position/state cues |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A consent interstitial covers essentially the full viewport before news can be read on desktop and mobile. F04 critical: A full-screen consent wall blocks the news on every tested entry surface |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The page contains four role=dialog overlays but zero native dialog, popover or details elements; the initial consent modal has no direct dismiss/reject control. F04 critical: A full-screen consent wall blocks the news on every tested entry surface |
maximize-content-reduce-noisereduced-chrome | issues | high | Initial content is dominated by the consent wall and a large advertisement slot rather than news. F04 critical: A full-screen consent wall blocks the news on every tested entry surface |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All tested 360px templates reported scrollWidth=clientWidth=360, viewport metadata, and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Rendered stylesheet inspection found no @container support on a page with reused cards and chrome across templates. F05 medium: Mobile layout fits, but component and input adaptation is weak |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused first link had outline-style none, and many visible header/ticker links measured only 15-30px high. F05 medium: Mobile layout fits, but component and input adaptation is weak |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage and article expose descriptive Hindi headlines, a Hindi News H1 and recognizable section navigation once content is visible. |
support-core-task-successprimary-flow-completion | issues | high | Opening the representative article is blocked by the consent wall before the core reading task can proceed. F06 high: The core reading journey is interrupted before content access |
support-core-task-successclear-system-state-and-recovery | pass | high | The invalid-route test renders a clear Page Not Found title, latest stories, home and section recovery links rather than a blank shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse reported LCP 8.4s, TBT 390ms and TTI 19.9s; these exceed a good interactive experience. F07 high: Slow LCP and heavy main-thread/network work delay useful content |
be-fast-and-stablevisual-stability | pass | high | CLS was 0 in Lighthouse and approximately 0.011 in three mobile layout observations, with no horizontal shift. |
be-fast-and-stableefficient-main-thread | issues | high | Trace recorded three long tasks, an 886ms longest task and 867ms total blocking time. F07 high: Slow LCP and heavy main-thread/network work delay useful content |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR found 120 requests/3.17MB and confirmed parser-inserted styles plus non-deferred jQuery/Swiper scripts; four fonts cost 352KB. F07 high: Slow LCP and heavy main-thread/network work delay useful content |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 784KiB unused JavaScript and 33KiB unused CSS, with multiple duplicate gtag payloads. F07 high: Slow LCP and heavy main-thread/network work delay useful content |
be-inclusivenames-roles-labels | issues | high | Lighthouse found a focusable WhatsApp link without a discernible name; image sampling separately found 16 missing alt attributes. F08 high: Accessibility defects affect names, contrast, focus and heading structure |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 2.86:1 top-menu text and 1.82:1 consent text, below WCAG minimums. F08 high: Accessibility defects affect names, contrast, focus and heading structure |
be-inclusivestructure-and-focus | issues | high | Lighthouse found skipped heading levels and the active keyboard target computed outline-style none. F08 high: Accessibility defects affect names, contrast, focus and heading structure |
be-inclusivelegible-text | issues | high | Top navigation uses 11px low-contrast text, and consent content becomes cramped in a viewport-height scrolling modal on mobile. F08 high: Accessibility defects affect names, contrast, focus and heading structure |
be-inclusivezoom-reflow-targets-and-media | issues | high | Viewport allows scaling to 5 and mobile reflow fits, but many interactive header links measure only 15-30px high, below comfortable touch targets. F08 high: Accessibility defects affect names, contrast, focus and heading structure |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured CORS and failed-network console errors from the recommendation collector. F09 medium: Console, browser-policy and asset hygiene checks fail |
follow-best-practicessound-document-and-assets | issues | high | Doctype/UTF-8 are valid, but image sampling found 8 missing dimensions, 20 oversized images and Lighthouse found low-resolution assets. F09 medium: Console, browser-policy and asset hygiene checks fail |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found notification permission requested on load, cookie inspector issues and a BFCache blocker. F09 medium: Console, browser-policy and asset hygiene checks fail |
be-discoverabletitle-and-description | pass | high | Homepage and article have unique descriptive titles and meta descriptions in Hindi/English. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse SEO scored 1.0; links are crawlable, viewport metadata is present, robots.txt is valid, and raw HTML retains core content. |
be-discoverablecanonical-and-indexing-signals | pass | high | Both tested public pages returned 200 with self-referential canonicals; robots allows public paths and declares dedicated sitemap endpoints. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage has Organization/WebPage/ItemList JSON-LD; article has NewsArticle JSON-LD and complete Open Graph title, description, URL and image. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS/nosniff/frame protection are present, but CSP allows unsafe-inline/unsafe-eval and 11 cookies were flagged insecure. F10 high: Tracking and browser defenses are not privacy-preserving by default |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker probe found 34 third-party origins and eight known trackers; HAR attributed 3.02MB and 115 requests to third parties. F10 high: Tracking and browser defenses are not privacy-preserving by default |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Lighthouse showed notification permission requested on page load. Authentication was not present, but the applicable permission behavior fails. F10 high: Tracking and browser defenses are not privacy-preserving by default |
be-private-and-securedefensive-browser-policies | issues | high | Referrer-Policy and Permissions-Policy are absent, CSP is permissive, and SameSite=None cookies are used widely. F10 high: Tracking and browser defenses are not privacy-preserving by default |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200 and preserved 82% of homepage and 77% of article rendered content, including title, H1 and description. |
be-resilientresilient-runtime-behaviour | pass | high | Consent overlay remained within both desktop and 360px viewports, mobile layouts did not overflow, and core content was server-rendered. |
be-resilientoffline-and-installable | issues | high | Manifest and active service workers exist, but Cache Storage contained no cache keys after load, providing no evidence of an offline content fallback. F11 medium: Installability exists but offline support is not evidenced |
be-resilientnetwork-and-http-failure-states | pass | high | The representative missing route produced a useful recovery screen with latest stories and explicit section links. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang is hi, but no logical CSS properties were found and no dir strategy was exposed. F12 medium: Hindi localization is incomplete in layout and date presentation |
be-internationalisedlocale-aware-data | issues | high | The Hindi page displays its global date as English “Jul 22, 2026” and exposes no time/datetime markup or locale-aware evidence. F12 medium: Hindi localization is incomplete in layout and date presentation |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, event coordination, user-entered time, or recurring-time workflow was present in the representative news-reading paths. |
be-trustworthyno-dark-patterns | issues | high | First-layer consent provides Consent and Manage options but no equally direct reject action, while describing 212 partners and precise geolocation processing. F13 high: Consent choice is asymmetric and burdens refusal |
be-trustworthyhumane-error-handling | not-applicable | high | No user-submittable form was present in the representative homepage, section, article, visual-story or error paths. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, sign-up or other user input fields were present in the representative paths. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription purchase, authentication or account-management flow was present in the audited public-news scope. |
be-sustainableoptimised-assets | issues | high | Image audit found 73 below-fold images not lazy-loaded, 67 missing srcset, 64 legacy formats and 20 oversized images. F14 high: The page ships disproportionate image, script and third-party weight |
be-sustainableno-wasteful-work | issues | high | Trace found 867ms blocking time and Lighthouse estimated 784KiB unused JavaScript, largely advertising/analytics code. F14 high: The page ships disproportionate image, script and third-party weight |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 115 third-party requests and 3.02MB third-party transfer; one hero JPG alone transferred 694KB. F14 high: The page ships disproportionate image, script and third-party weight |
be-agent-readystructured-agent-capabilities | issues | medium | Content is server-rendered and structured, but no WebMCP/agent tool registration was found for search, save or content actions. F15 low: Machine-readable content is strong, but agent actions are not exposed |
be-agent-readyon-device-inference | not-applicable | high | The audited public news-reading journeys do not require an on-device generative feature to complete their core task; absence is not a quality failure. |
be-memory-efficientno-leak-under-repeated-interaction | issues | high | Ten repeated bottom/top feed traversals increased retained snapshot size from 41.46MB/713k nodes to 84.23MB/1.394m nodes. F16 high: Repeated feed traversal produces a very large retained footprint and listener growth |
be-memory-efficientbounded-footprint | issues | high | Post-interaction heap reached 84.23MB, 1.394m heap nodes, 379k native nodes and 196k objects for a news homepage. F16 high: Repeated feed traversal produces a very large retained footprint and listener growth |
be-memory-efficientno-detached-dom-or-unbounded-listeners | issues | high | No Detached* constructor appeared in the top constructor list, but repeated-scroll instrumentation observed 1,126 listener adds vs 76 removals and three net intervals. F16 high: Repeated feed traversal produces a very large retained footprint and listener growth |
Provenance
Canonical report: results/atomic/reports/0725-www_aajtak_in.json
Report SHA-256: a0ef2cfe011e49ce589fe7e5465c370ce16f20816c5f72ab9860fd6d6ad4626b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_aajtak_in/2026-07-22T16-15-47-674Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_aajtak_in/2026-07-22T16-15-47-674Z
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.