Manifest position 127 · CrUX rank bucket 1000
https://www.ad.nl
Coverage complete
Coverage complete across five representative paths. Login failure is reported as a directly observed issue, not an evidence blocker.
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 | The dark-condition screenshot is pixel-equivalent to the light capture, and computed html color-scheme remains normal with a light #f6f6f6 surface. F01 medium: The site ignores the user’s dark color-scheme preference |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce matched, the probe still found seven 1.5s livefeed-pulse animations and two 121.34s ticker/swap animations running. F02 high: Long-running motion continues under reduced-motion |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse accessibility scored 98 and the screenshots retained clear high-contrast red, white and black text/control boundaries. |
implement-natural-interactionsview-transitions | issues | high | The modern CSS probe found no view-transition CSS or authored startViewTransition integration even though the homepage exposes many document navigations. F03 low: Route changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | pass | high | The CSS/motion probe found no authored scroll-linked animation, so no main-thread scroll animation anti-pattern was present. |
implement-natural-interactionsphysical-gestures | pass | high | The mobile page uses native document scrolling and exposed no custom pointermove or swipe surface that fought platform gestures. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage is 18,403px tall, while the CSS signal probe found no scroll-state queries, progress indicator, or authored scroll-timeline cue. F04 low: Long pages lack scroll-state-aware navigation cues |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, menu overlay or other anchored floating surface was exposed on the representative public paths. |
provide-guided-navigationdirects-attention | pass | high | Desktop and mobile screenshots show persistent labelled navigation, an active section treatment, and clear 404 recovery CTA. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No content-obscuring interstitial or full-viewport overlay appeared on homepage, listing or article captures. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No modal or transient overlay appeared in the audited public paths, so there was no overlay primitive to judge. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop screenshots devote roughly the first 390px below navigation to blank advertising space before the leading story, reducing content density. F05 medium: Reserved advertising space delays visible content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, layout reported scrollWidth 360, clientWidth 360 and zero horizontal overflow; mobile screenshot remained usable. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Rendered CSS includes container-type:inline-size and an @container rule for a reusable notification component, while mobile cards reflow to a list. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found outline:none and no box shadow on the main navigation links; it also found 29 of 80 sampled targets below 24px in one dimension. F06 high: Keyboard focus is not visibly exposed on primary navigation |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly identifies AD news and presents current lead stories with descriptive headlines and section navigation. |
support-core-task-successprimary-flow-completion | issues | high | Following the header sign-in action redirects to login2.ad.nl and produces “Inlogpoging geblokkeerd” with HTTP-like status 406, so the primary account journey cannot complete in this session. F07 high: The sign-in journey ends at a blocked state |
support-core-task-successclear-system-state-and-recovery | pass | high | The tested invalid URL presents a clear Dutch not-found explanation and a prominent action back to the latest news. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured 3.6s LCP and 2.6s FCP on the consent redirect path. A direct trace was better at 2.19s LCP, showing the redirect/first-visit path is the risk. F08 medium: Mobile LCP misses the good threshold in the redirected first-visit path |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observation measured CLS 0.0136 with only three small shifts, comfortably within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | The direct trace found two long tasks, 71.59ms maximum, and only 25.69ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 117 requests and 11,668,883 transferred bytes; 8.44 MB came from live-streaming video segments, while Lighthouse flagged redirects, cache lifetime, document latency and render blocking. F09 high: The homepage transfers an excessive 11.67 MB on load |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The HAR recorded 38 scripts and Lighthouse estimated 58 KiB unused JavaScript; video player, tag manager, experimentation and advertising libraries all load on the homepage. F10 medium: Third-party and unused JavaScript add avoidable cost |
be-inclusivenames-roles-labels | issues | high | The images primitive reported missing alt on all 100 sampled images. The form probe found the first email input had no associated label or aria-label. F11 high: News images and a newsletter field lack accessible alternatives |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility scored 98 and no contrast failure appeared in its failing audit list; visual captures show strong text contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed heading-order and accessible-name/visible-label matching; the focus probe found no visible outline on sampled primary links. F12 high: Focus treatment and heading semantics are inconsistent |
be-inclusivelegible-text | pass | high | Article and listing captures use large, readable headlines and comfortable body measure without clipping at desktop or mobile widths. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360px the page reflows without overflow, but the target probe found 29 of 80 sampled interactive elements under 24px in width or height. F13 medium: Many controls are too compact for reliable touch use |
follow-best-practicesno-console-errors | pass | high | Lighthouse did not report the console-errors or runtime-exception audit among failures during the audited load. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found five images without explicit dimensions and five without srcset; Lighthouse also failed the unsized-images audit. F14 medium: Some images do not reserve intrinsic space |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported DevTools Inspector issues and three BFCache failure reasons on the first-visit route. F15 medium: Browser diagnostics report lifecycle and inspector problems |
be-discoverabletitle-and-description | pass | high | Direct rendered probe found a descriptive homepage title and meta description; the article has a unique title and detailed description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Discoverability fetched only 7,861 bytes, found 0% rendered-content coverage and identified a JS shell; the crawler screenshot contains no page content. Direct robots and sitemap requests were also blocked by the WAF from this audit origin. F16 critical: Non-JavaScript crawlers receive a privacy shell instead of news content |
be-discoverablecanonical-and-indexing-signals | pass | high | Rendered homepage and article expose self-referencing canonicals, and the article robots meta permits full snippets and previews. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage has two JSON-LD blocks and Open Graph metadata; article JSON-LD includes NewsArticle and BreadcrumbList with seven OG tags. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS and nosniff are present, but CSP permits unsafe-inline and unsafe-eval; 25 of 27 cookies were reported without Secure, including long-lived analytics identifiers. F17 high: Cookie and CSP defaults weaken otherwise strong transport security |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker scan observed 45 third-party origins and 11 known tracker domains. The HAR attributed 108 of 117 requests and 11.41 MB to third parties. F18 critical: The homepage has an extreme tracking and third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The sign-in route is blocked and only describes email-code authentication; no passkey or WebAuthn UI could be reached or observed. F19 medium: The authentication surface offers no observable phishing-resistant sign-in |
be-private-and-securedefensive-browser-policies | issues | high | Headers include HSTS, DENY framing and strict-origin referrer policy, but CSP allows unsafe-inline/unsafe-eval and Permissions-Policy only declares two client-hint features. F20 medium: Defensive policies remain overly permissive |
be-resilientprogressive-enhancement | issues | high | The raw-HTML discoverability comparison found 0% content overlap, no raw title, h1 or description, and classified the response as a JavaScript shell/privacy gate. F21 critical: Core news content is unavailable without JavaScript |
be-resilientresilient-runtime-behaviour | pass | high | Representative homepage, article and listing rendered complete content with stable native navigation; no clipped open menu or broken async shell appeared. |
be-resilientoffline-and-installable | not-applicable | high | AD is a continuously updated public news publication rather than an offline-first application; offline installability was judged out of scope. |
be-resilientnetwork-and-http-failure-states | pass | high | The deliberate invalid path renders an intentional 404-style page with explanation and a direct route to current news. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=nl and ltr, and rendered CSS contains logical-property usage; Dutch reading order is correct. |
be-internationalisedlocale-aware-data | issues | high | Article time elements use human text such as “18 juli 2026, 14:52” and “Laatste update: 16:08” directly in datetime rather than valid ISO date/time values; no Intl usage was observed in the rendered article. F22 medium: Published times are not machine-readable or locale-robust |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited news surfaces did not expose cross-zone scheduling, recurring events or user-entered time concepts. |
be-trustworthyno-dark-patterns | pass | high | Premium labels and the newsletter purpose are visible in captures, and the not-found/account messages do not use confirmshaming. |
be-trustworthyhumane-error-handling | pass | high | The observed blocked sign-in state explains the security reason and gives code-based recovery instructions without blaming the user. |
be-trustworthytrustworthy-input-assistance | issues | high | Both sampled newsletter email inputs reported an empty autocomplete value; the first also lacked a programmatic label. F23 medium: Email fields omit autocomplete assistance |
be-trustworthysafe-commercial-and-account-flows | issues | high | The sign-in endpoint shows a status 406 block and textual instructions but no visible control to return, switch to email-code sign-in, or retry. F24 high: Account access is not recoverable from the blocked screen |
be-sustainableoptimised-assets | pass | high | The image audit found no oversized images, all below-fold images were lazy, and 95 of 100 sampled images had srcset and dimensions. |
be-sustainableno-wasteful-work | issues | high | The HAR shows ten live-streaming requests transferring 8.44 MB during a six-second homepage capture, despite no player being visible in the first desktop or mobile viewport. F25 high: An offscreen live stream downloads megabytes without user intent |
be-sustainablethird-party-and-media-budget | issues | high | Third parties transferred 11.41 MB across 108 requests, including 8.44 MB of live video, which is disproportionate for a news landing page before interaction. F26 critical: Media and third parties dominate the page budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent or transactional agent capability was found, so emerging WebMCP support is not required for this run. |
be-agent-readyon-device-inference | not-applicable | high | No declared on-device AI intent or user workflow requiring built-in inference was found. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten repeated top-to-bottom scroll cycles, heap totals decreased from 53.68 MB/872,921 nodes to 52.67 MB/855,104 nodes rather than growing. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary contained 872,921 nodes, 3,637,944 edges and 53,675,080 self-size bytes, high for a news landing page before extended interaction. F27 high: The initial page has a very large DOM and heap footprint |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The before/after heap summaries showed lower node and edge totals after repeated scrolling, with no aggregate accumulation signal. |
Provenance
Canonical report: results/atomic/reports/0127-www_ad_nl.json
Report SHA-256: 145eedfb2486de0f4812a23ea9544fb07e9c85adba5307fe793db041e0198bfd
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ad_nl/2026-07-18T15-09-50-647Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ad_nl/2026-07-18T15-09-50-647Z
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.