Manifest position 535 · CrUX rank bucket 1000
https://www.bfmtv.com
Coverage complete
Coverage-complete representative audit of five page archetypes plus a 404 recovery state.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Dark and normal screenshots are identical and body remains white under the emulated dark preference. F01 medium: The site ignores the user’s dark colour-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned no active animations, so no non-essential motion remained. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast capture was unchanged and Lighthouse found 40 contrast failures, so essential text does not consistently survive stronger contrast needs. F08 high: Numerous text and UI combinations fail minimum colour contrast. |
implement-natural-interactionsview-transitions | issues | high | Menu video shows an immediate swap and the CSS probe found no View Transition usage. F02 low: Navigation and menu state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS probe found no scroll timelines and the inspected templates use static scrolling rather than JS-driven parallax or reveal motion. |
implement-natural-interactionsphysical-gestures | pass | high | The mobile horizontal topic/channel strips use native scrolling and CSS scroll-snap; no custom pointermove gesture layer was observed. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The compact mobile header remains legible while long pages scroll; no brittle JS scroll-toggle or obstructive chrome was observed. |
provide-guided-navigationanchored-positioning | pass | high | No tooltip or edge-sensitive anchored popover is used on the representative paths; the full-screen navigation panel does not require anchor positioning. |
provide-guided-navigationdirects-attention | pass | high | Article breadcrumbs, active topic colour, live status, and clear heading hierarchy on article/listing pages orient the reader. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Fresh-profile captures across five templates show no modal, consent wall, or interstitial obscuring content on load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | No modal flow was encountered; the navigation is exposed as a labelled button and navigation landmark rather than an unlabeled overlay div. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop screenshot shows a large empty ad/loading reservation before the lead editorial content. F03 medium: A large empty advertising/loading region pushes primary content below the first desktop viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360×800 both home and article layouts report scrollWidth=clientWidth=360 and horizontalOverflowPx=0; viewport meta is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Desktop/mobile captures show lead cards, navigation, article, live, and newsletter components recompose for their available width without clipping. |
adapt-to-the-form-factorinput-modality-aware | pass | high | The first keyboard focus target is the labelled menu button; controls remain available without hover and mobile controls are visibly touch-sized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage foregrounds the lead story; article, live, and newsletter pages each expose a descriptive H1 and obvious next action. |
support-core-task-successprimary-flow-completion | pass | high | The newsletter journey progresses from selecting a publication to a single email-and-consent form without an account wall or detour. |
support-core-task-successclear-system-state-and-recovery | issues | high | Invalid newsletter submission provides only native validity with no connected or announced recovery state. F04 medium: The newsletter form’s invalid state is not announced or connected to a recovery message. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse mobile LCP is 17.7 s and FCP 3.7 s, outside good thresholds. F05 high: Throttled mobile loading misses the good LCP range by a wide margin. |
be-fast-and-stablevisual-stability | pass | high | Layout observers measured CLS 0.00031 on home and 0.00045 on article with no visible jump in captured states. |
be-fast-and-stableefficient-main-thread | pass | high | Trace TBT was 10.32 ms with one 60.32 ms long task; Lighthouse TBT was 120 ms, both within the good responsiveness proxy range. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR/Lighthouse show 255 requests, 14.03 MB transfer, cache waste and a 2.23 s render-blocking opportunity. F06 high: The homepage loads an excessive dependency and media payload with render-blocking resources. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 656 KiB unused JS, 58 KiB unused CSS and 17 KiB legacy JS savings. F07 medium: Substantial unused JavaScript and CSS are delivered on the homepage. |
be-inclusivenames-roles-labels | issues | high | The primary newsletter email input has no label or aria-label and relies on placeholder text. F09 medium: The newsletter email field has no accessible label. |
be-inclusivesufficient-contrast | issues | high | Lighthouse identifies 40 foreground/background contrast failures. F08 high: Numerous text and UI combinations fail minimum colour contrast. |
be-inclusivestructure-and-focus | issues | high | Homepage H1 is empty, heading order fails, and the opened menu leaves aria-expanded=false. F10 medium: Heading hierarchy and menu expanded-state semantics are inconsistent. |
be-inclusivelegible-text | pass | high | Mobile screenshots show readable body sizing, wrapping, spacing, and no clipping across homepage, article, live and newsletter templates. |
be-inclusivezoom-reflow-targets-and-media | pass | high | The 360 px reflow has no horizontal page overflow, viewport permits scaling, and key controls remain touch-sized; no prerecorded speech media requiring captions was assessed in the selected flow. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with zero items. |
follow-best-practicessound-document-and-assets | issues | high | Doctype/UTF-8 pass, but image audit finds 8 unsized images and Lighthouse lists 14 affected elements. F11 medium: Several images lack explicit dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports one deprecated API warning and three missing first-party source maps. F12 medium: The page uses a deprecated API and omits source maps for large first-party scripts. |
be-discoverabletitle-and-description | pass | high | Home and article have descriptive unique titles and meta descriptions in both raw and rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Viewport and robots pass, but Lighthouse reports 12 non-crawlable anchors. F13 medium: Some navigation links are not crawlable. |
be-discoverablecanonical-and-indexing-signals | pass | high | Pages return 200, expose self-canonicals and index/follow; robots.txt returns 200 and declares three working sitemap locations. |
be-discoverablestructured-and-shareable-metadata | pass | high | Article exposes LiveBlogPosting and BreadcrumbList JSON-LD plus complete Open Graph title, description, image and dimensions matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS/nosniff/frame protection pass, but CSP and Permissions-Policy are missing and three cookies lack Secure. F14 high: Security policy headers and cookie flags are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Network evidence shows 21 third-party origins, 188 third-party requests and long-lived analytics identifiers. F15 high: The homepage has a broad tracking and third-party collection footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No geolocation/notification prompt appeared on load, and no authentication path is part of this public news site’s representative core flow. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS, X-Frame-Options and Referrer-Policy are present, but CSP and Permissions-Policy are absent. F14 high: Security policy headers and cookie flags are incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison reports 100% content visibility without JavaScript for home and article; neither is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Menu, horizontal strips, live layout and newsletter state rendered without clipping or broken shells on the narrow viewport. |
be-resilientoffline-and-installable | not-applicable | high | BFM is a public, continuously updated news publication rather than an install-oriented web app; offline/installability was judged out of scope while progressive enhancement was still tested. |
be-resilientnetwork-and-http-failure-states | pass | high | A nonexistent URL returns a genuine HTTP 404 and a clear French “Page introuvable” state with site navigation and recovery links. |
be-internationalisedlang-dir-and-logical-properties | pass | high | HTML declares lang=fr; DOM/CSS probe found logical properties, and the left-to-right layout matches French content. |
be-internationalisedlocale-aware-data | pass | high | Rendered publication strings are idiomatic French and machine-readable <time datetime> values retain full ISO timestamps. |
be-internationalisedtime-zone-correctness | pass | high | Article dateTime values include an explicit +02:00 offset while visible live-update times are consistently localized for the French audience. |
be-trustworthyno-dark-patterns | pass | high | The newsletter selection and optional marketing/partner consent checkboxes are clear, unselected by default, and include unsubscribe/data-rights text. |
be-trustworthyhumane-error-handling | issues | high | Empty-email submission has no aria-invalid, associated error, live announcement, or focus recovery. F04 medium: The newsletter form’s invalid state is not announced or connected to a recovery message. |
be-trustworthytrustworthy-input-assistance | issues | high | Newsletter email input omits autocomplete=email. F16 low: The newsletter email field does not advertise its autofill purpose. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription payment, authentication, or account-management flow is present in the selected public-news and newsletter paths. |
be-sustainableoptimised-assets | issues | high | Image audit found legacy formats, missing srcset/lazy loading, oversized assets and 479 KiB estimated savings. F17 medium: Image delivery leaves meaningful byte and rendering savings. |
be-sustainableno-wasteful-work | issues | high | Homepage starts fetching repeated live-stream segments without an explicit play interaction, dominating the load. F18 high: Live media and third-party work consume a disproportionate homepage budget before explicit user intent. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party/media bytes reach 12.16 MB of a 14.03 MB homepage load, disproportionate for a news landing page. F18 high: Live media and third-party work consume a disproportionate homepage budget before explicit user intent. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The publisher explicitly disallows mainstream AI assistants and crawlers in robots.txt, so it does not intend to expose agent-facing tools; public browser navigation remains conventional. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the selected news-reading and newsletter paths needs on-device inference, and the site policy does not target agent/AI experiences. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 menu open/close cycles, heap self-size fell from 39,432,209 to 39,394,225 bytes; DOM element count remained exactly 3,780. |
be-memory-efficientbounded-footprint | pass | high | Heap summary is about 39.4 MB for a media-rich homepage; the post-interaction snapshot did not increase total self-size. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Ten menu cycles produced zero DOM node-count delta; closure count changed only 30,303→30,317 and no Detached* constructor appears among retained top constructors. |
Provenance
Canonical report: results/atomic/reports/0535-www_bfmtv_com.json
Report SHA-256: bc6899a6aa31b1e2473cc526ef6f3e8dd278ed7a94b6697e436856a71416e1de
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_bfmtv_com/2026-07-21T10-26-43-711Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_bfmtv_com/2026-07-21T10-26-43-711Z
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.