Manifest position 243 · CrUX rank bucket 1000
https://www.ladepeche.fr
Coverage complete
Coverage complete across 58 atomic checks. Representative coverage: homepage, article, section listing, agenda form, search results, 404 recovery, and account login entry. Excluded: paid checkout completion, authenticated account management, destructive actions, and locale variants because they require credentials/payment or do not exist publicly.
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-mode screenshot is byte-identical to the default screenshot, body remains white, computed color-scheme is normal, and CSS inspection found no prefers-color-scheme rule. F01 medium: The site does not adapt to the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, the probe found two running 1-second rotation animations and no prefers-reduced-motion CSS rules. F02 medium: Animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | medium | The prefers-contrast screenshot retained visible text, borders, icons, and controls without clipping. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection across the MPA templates found no view-transition declarations or view-transition-name usage. F03 low: Cross-document navigation uses abrupt swaps rather than progressive View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | medium | No scroll-linked/parallax/reveal motion was present, so there was no main-thread scroll-animation anti-pattern to replace. |
implement-natural-interactionsphysical-gestures | pass | medium | Navigation and content use native scrolling/taps; no custom pointermove gesture layer was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The DOM reports a 120px sticky header, while CSS inspection found no scroll-state query, progress indicator, or shrinking-header behavior. F04 low: The large sticky navigation does not adapt to scroll state. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, attached popover, or edge-positioned transient overlay was present on the representative templates; the full-screen menu/search issue is judged under semantic overlays. |
provide-guided-navigationdirects-attention | pass | medium | Breadcrumbs, current-section styling, sticky navigation, and clear search-result headings preserve orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | medium | No modal consent wall or full-viewport interstitial obscured content on initial captures. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The probe found visible fixed .search-overlay and .side-nav elements but zero dialog, popover, or details elements. F05 medium: Menu and search overlays are custom fixed divs rather than semantic overlay primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and mobile first-view screenshots show a large blank region between the 120px navigation and the lead story; the page prioritizes empty ad chrome over news content. F06 high: Reserved advertising space pushes primary content far below the navigation. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | At 360px, home/article/listing all reported scrollWidth=clientWidth=360 and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container or container-type usage across reused cards and navigation, although mobile layouts otherwise reflow. F07 low: Responsive templates rely on viewport rules rather than component-level adaptation. |
adapt-to-the-form-factorinput-modality-aware | pass | medium | The sampled focusable anchor had a visible auto 1px outline and primary mobile targets measured about 40–59px. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Home leads with a clearly labelled story, article has a descriptive H1, agenda/search have explicit H1s and controls. |
support-core-task-successprimary-flow-completion | pass | medium | Search returned 10,000 results with article links; article content loaded; agenda controls and account/subscribe destinations were reachable. |
support-core-task-successclear-system-state-and-recovery | pass | medium | The 404 page clearly says the page does not exist and offers search, home/navigation, and subscription links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 13.5s on the homepage and 11.7s on the article, with performance scores of 0.56 and 0.57. The raw-CDP trace was fast in an unconstrained run, so the issue is specifically constrained mobile delivery. F08 high: Cold mobile loading misses the good LCP range on core templates. |
be-fast-and-stablevisual-stability | pass | medium | Home/article/listing layout observers all measured CLS 0 with no captured shifts. |
be-fast-and-stableefficient-main-thread | pass | medium | Trace TBT was 124ms with two long tasks; Lighthouse TBT was 160ms home and 80ms article, within a reasonable range. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 123 requests and 2.83MB, with parser-blocking stylesheets and scripts; Lighthouse estimated 350ms render-blocking savings and 826KiB cache-lifetime savings. F09 high: Render-blocking and weakly cached resources delay content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 380KiB unused JavaScript and 61KiB unused CSS on home; HAR shows 43 scripts, including 330KB Taboola and 187KB GTM. F10 high: Large third-party and legacy bundles ship substantial unused code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found unnamed home/account/social/share controls, untitled iframes, links without names, and images without alt. The agenda probe found visible text, checkbox, select, and date controls with no associated label or aria-label. F11 high: Important controls, links, frames, images, and agenda fields lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found the white “ABONNÉS” label on #f2c94c at 1.58:1 and multiple red/white controls at 4.37:1, below the required 4.5:1. F12 high: Brand and subscriber UI colors fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | The structure probe found an empty H1 and zero main elements on the homepage. Lighthouse reports an accessibility tree that is not well formed, although the sampled keyboard focus outline is visible. F13 high: The homepage lacks a meaningful H1 and main landmark. |
be-inclusivelegible-text | pass | medium | Mobile screenshots show readable body/headline typography with clean wrapping and no clipping. |
be-inclusivezoom-reflow-targets-and-media | pass | medium | Viewport permits scaling (no maximum-scale/user-scalable=no), layouts reflow at 360px, and key targets are adequately sized. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a 404 for /cdn-cgi/challenge-platform/scripts/jsd/main.js and the HAR recorded it as aborted. F15 low: The homepage logs a failed resource request. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found all 100 img elements missing width/height, 57 missing srcset, 80 legacy-format images, and 14 oversized images; Lighthouse also failed unsized-image checks. F14 medium: Image markup omits intrinsic dimensions and responsive delivery on a content-heavy page. |
follow-best-practicesbrowser-platform-hygiene | pass | medium | Lighthouse best-practices scored 0.92; no deprecated API, paste prevention, or on-load permission prompt failure was reported. |
be-discoverabletitle-and-description | pass | medium | Home, article, agenda, and search have descriptive titles; public content templates include descriptions, with strong article metadata. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found a LinkedIn share anchor without href on the article and multiple empty-name links on home and article. The viewport and robots configuration otherwise support indexing. F16 medium: Some actionable links are not crawlable and several links have no descriptive text. |
be-discoverablecanonical-and-indexing-signals | pass | medium | Main responses are 200, canonicals match, robots allows general crawling, and sitemap.xml returns 200. |
be-discoverablestructured-and-shareable-metadata | pass | medium | The article has matching NewsArticle JSON-LD, breadcrumbs, canonical, Open Graph title/description/image, author and dates. |
be-private-and-securesecure-transport-and-headers | issues | high | Cookie inspection found 7 cookies, 7 reported insecure, including long-lived atauthority/atuserid; CSP is only “frame-ancestors”, providing no script/style XSS policy. HSTS is present. F17 high: Cookies are set without Secure and the CSP protects framing only. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture saw 34 third-party origins and known Google Tag Manager, Facebook, and nine Taboola endpoints; HAR shows these parties among the largest scripts. F18 high: The initial page load exposes users to an unusually broad tracking surface. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login probe found correctly labeled username/current-password/new-password fields but no WebAuthn or passkey integration. F19 medium: Account authentication is password/social-provider only with no phishing-resistant passkey option. |
be-private-and-securedefensive-browser-policies | issues | high | Headers inspection found no X-Content-Type-Options, Referrer-Policy, or Permissions-Policy. Clickjacking protection and HSTS are present. F20 medium: Several browser-enforced defenses are absent. |
be-resilientprogressive-enhancement | pass | medium | Raw HTML contains 96% of rendered home words and 100% of article words; neither page is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Representative mobile templates rendered menus/content without clipping or blank shells. |
be-resilientoffline-and-installable | issues | high | A manifest and service worker are registered, but the 311-byte worker only imports the Batch push SDK and has no fetch handler or CacheStorage usage. F21 medium: The installable news experience has no offline navigation fallback. |
be-resilientnetwork-and-http-failure-states | pass | medium | The deliberate 404 renders a useful recovery page rather than a blank screen or infinite spinner. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The page correctly declares lang=fr, while stylesheet inspection found no logical inline/block properties and no explicit direction handling. F22 low: The document language is correct but the CSS is not writing-mode resilient. |
be-internationalisedlocale-aware-data | pass | medium | French dates and counts are rendered in locale-appropriate forms and agenda uses native date inputs. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited editorial and agenda surfaces showed dates but no event times, recurring cross-zone events, or user-entered time-zone data to model. |
be-trustworthyno-dark-patterns | pass | medium | Subscriber content is marked “ABONNÉS” with a lock and subscribe/account actions are explicitly labelled; no confirmshaming or forced continuity was observed. |
be-trustworthyhumane-error-handling | pass | medium | The tested 404 state explains the problem without blame and provides recovery; search and agenda do not validate prematurely. |
be-trustworthytrustworthy-input-assistance | pass | medium | The account form uses username, current-password, and new-password autocomplete tokens with associated labels. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | Subscription/account destinations are consistently and visibly labelled, premium content is marked before entry, and no preselected marketing checkbox was observed. |
be-sustainableoptimised-assets | issues | high | Of 100 images, 80 use legacy formats, 57 lack srcset, 71 below-fold images lack native lazy loading, and 14 are oversized. F23 high: Image delivery is wasteful for a text-led news homepage. |
be-sustainableno-wasteful-work | issues | high | The initial HAR includes 43 scripts and 34 third-party origins, while Lighthouse estimates 380KiB unused JavaScript on the homepage. F24 high: Background recommendation, ad, video, experimentation, and analytics work starts before user intent. |
be-sustainablethird-party-and-media-budget | issues | high | HAR transferred 2.83MB over 123 requests; the largest resources include Taboola, GTM, Digiteka video, Facebook, identity, consent, and experimentation scripts. F25 high: Third-party scripts dominate a disproportionate share of a news page’s transfer budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing or transactional capability exists; this emerging contextual check is not required for the public news-reading experience. |
be-agent-readyon-device-inference | not-applicable | high | No declared product feature requires on-device inference; the editorial content is already exposed as raw HTML and NewsArticle structured data. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten menu open/close cycles, heap fell from 37,739,623 to 37,625,904 bytes and node count fell from 592,498 to 588,221. |
be-memory-efficientbounded-footprint | pass | medium | A 37.7MB heap is proportionate to this large news homepage; no single constructor dominated unexpectedly. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The post-interaction heap did not grow and no Detached* constructor appeared in either compact summary. |
Provenance
Canonical report: results/atomic/reports/0243-www_ladepeche_fr.json
Report SHA-256: 1fbcd0da0e2a4b908d7fa578af2cff0019fb8a20cd2a9e867f48fb58f6a714b6
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ladepeche_fr/2026-07-19T09-50-45-981Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ladepeche_fr/2026-07-19T09-50-45-981Z
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.