Manifest position 374 · CrUX rank bucket 1000
https://fr.wikipedia.org
Coverage complete
Atomic coverage complete across 58 checks and four representative paths.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Dark emulation remains visually light and computed color-scheme is normal. f01 medium: The anonymous desktop experience does not follow the system dark-color preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The preference matched and zero active animations were present. |
respect-user-preferencesrespects-contrast | pass | medium | Loaded CSS includes forced-colors handling and Lighthouse color-contrast passed; essential UI remains visible in screenshots. |
implement-natural-interactionsview-transitions | issues | high | No view-transition rules are present for cross-document article navigation. f02 low: Cross-document article navigation swaps abruptly. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, reveal, carousel, or other scroll-linked motion exists to implement. No JS scroll animation anti-pattern was observed. |
implement-natural-interactionsphysical-gestures | pass | medium | Reading uses native scrolling and links; no custom pointer handlers, hijacked scrolling, or gestures that fight platform behavior were observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The article main region is 86,786px tall and no progress or scroll-state CSS was found. f03 low: Very long articles provide no scroll-position progress cue. |
provide-guided-navigationanchored-positioning | issues | high | Menus are present but no CSS anchor positioning declarations are loaded. f04 low: Menus and transient controls do not use CSS anchor positioning. |
provide-guided-navigationdirects-attention | pass | medium | Current location tabs, article headings/table of contents, language control, and a visible focused skip link provide orientation and attention cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No pop-up, consent wall, ad, or interstitial obscures primary content on load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Mobile main navigation uses a checkbox with role=button rather than a button plus disclosure/popover primitive. f05 medium: The mobile navigation trigger is a checkbox presented as a button instead of a semantic disclosure/popover control. |
maximize-content-reduce-noisereduced-chrome | pass | high | The anonymous homepage and article prioritize encyclopedia content; chrome is compact and there are no ads. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The desktop response declares width=1120 and is scaled down instead of reflowed. f06 high: The desktop skin fixes its layout viewport at 1120px and scales down at a 360px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No container query rules are present for reused card/navigation components. f07 low: Reusable components rely on page/viewport rules rather than container queries. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focus is visible, but several article links have target dimensions/separation below 24px. f08 medium: Some article links have touch targets below the recommended minimum. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The encyclopedia purpose, article title, search/navigation, and login action are explicit and visually prominent. |
support-core-task-successprimary-flow-completion | pass | high | Core content is available without an account and article links are real crawlable hrefs; login has a concise labelled form. |
support-core-task-successclear-system-state-and-recovery | pass | high | The missing-page state clearly says the article does not exist and offers search, similarly titled pages, help, and creation paths. |
be-fast-and-stablegood-core-web-vitals | issues | high | Article LCP was 6.6s and FCP 4.7s; homepage LCP was 2.42s. f09 high: The representative article loads too slowly under Lighthouse mobile conditions. |
be-fast-and-stablevisual-stability | pass | high | Homepage observed CLS was 0.00043 and article Lighthouse CLS was 0. |
be-fast-and-stableefficient-main-thread | pass | high | Homepage trace had no long tasks/TBT; article Lighthouse TBT was 83ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | Script bytes dominate and early parser-inserted resources plus a 328KB script delay the content path. f10 medium: Large startup bundles and blocking styles delay primary content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 91KiB unused JS and 45KiB unused CSS. f11 medium: The article ships substantial unused JavaScript and CSS. |
be-inclusivenames-roles-labels | issues | high | The article has unnamed images/links and a mis-exposed menu checkbox. f12 high: The article template contains unnamed links/images and an incorrectly exposed menu toggle. |
be-inclusivesufficient-contrast | issues | high | Inline links fail the non-color distinction requirement against surrounding text. f13 medium: Inline links are distinguished from surrounding prose by color alone with insufficient non-text contrast. |
be-inclusivestructure-and-focus | pass | medium | One H1, hierarchical section headings, main/nav landmarks, a skip link, and a 2px solid visible focus outline were observed. |
be-inclusivelegible-text | pass | medium | Body text has comfortable line-height and content width on the purpose-built mobile article skin; no clipping was reported by Lighthouse. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Viewport permits scaling and article reflows for mobile UA, but multiple touch targets are too small. f08 medium: Some article links have touch targets below the recommended minimum. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed. |
follow-best-practicessound-document-and-assets | issues | medium | Doctype/charset are valid and aspect ratios pass, but the homepage has one image missing dimensions and oversized assets. f17 medium: The homepage leaves many below-fold and legacy-format images unoptimized. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Deprecated API and BFCache audits pass, but Lighthouse reports missing/broken source maps for large first-party scripts and a cookie issue in DevTools. f11 medium: The article ships substantial unused JavaScript and CSS. f15 high: A session-labelled cookie lacks Secure and the CSP permits unsafe script execution modes. |
be-discoverabletitle-and-description | issues | high | Titles are descriptive, but meta description is absent on homepage and representative article. f14 medium: Public pages omit a meta description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | All 659 homepage anchors have hrefs, Lighthouse crawlable-anchors/robots passed, and the mobile article has a viewport meta tag. |
be-discoverablecanonical-and-indexing-signals | pass | high | Pages return 200, homepage has a canonical URL, Lighthouse canonical and hreflang pass, and robots.txt declares the REST sitemap. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Homepage exposes Open Graph tags; MediaWiki articles use semantic headings, image metadata and canonical links consistent with visible content, with no misleading schema found. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS/nosniff and no secrets are good, but CSP allows unsafe-inline/unsafe-eval and a session-labelled cookie is not Secure. f15 high: A session-labelled cookie lacks Secure and the CSP permits unsafe script execution modes. |
be-private-and-securedata-minimisation-and-third-parties | pass | medium | No known tracker domains were found; third-party requests are limited to Wikimedia-operated upload/auth origins and no sensitive secret was exposed. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No permission prompt appears on load; login uses username webauthn plus current-password autocomplete, indicating passkey-capable conditional authentication. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS/nosniff pass, but frame-ancestors/X-Frame-Options, Referrer-Policy and Permissions-Policy are absent. f16 medium: Several browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | high | 98% of rendered content words are present in raw HTML; title and H1 survive without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | No uncaught errors or BFCache blocker was detected; navigation and recovery work as documents/links without fragile shell state. |
be-resilientoffline-and-installable | not-applicable | high | No manifest is linked on desktop; anonymous Wikipedia is a public reference content site, not an installed app journey. |
be-resilientnetwork-and-http-failure-states | pass | high | The missing route produces a clear, content-rich recovery state with search/help/navigation rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=fr and dir=ltr and exposes 347 language variants; the UI uses localized French labels. |
be-internationalisedlocale-aware-data | pass | medium | Dates, number grouping and interface strings are rendered in French locale conventions across homepage/article UI. |
be-internationalisedtime-zone-correctness | not-applicable | high | No booking, scheduling, recurring event, or time-zone-sensitive primary flow exists on the audited templates. |
be-trustworthyno-dark-patterns | pass | high | No ads, confirmshaming, forced continuity, consent nagging or disguised actions were present; donation/account actions are plainly labelled. |
be-trustworthyhumane-error-handling | pass | medium | Blank login preserves the simple labelled form without blame, and missing content gives specific recovery links and search. |
be-trustworthytrustworthy-input-assistance | pass | high | Username uses autocomplete="username webauthn" and password uses current-password; both have visible labels. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | No commercial commitment exists; sign-in is optional for reading, session persistence is an unchecked explicit choice, and help/recovery links are visible. |
be-sustainableoptimised-assets | issues | high | 15 below-fold images lack lazy loading; 16 use legacy formats; three are oversized. f17 medium: The homepage leaves many below-fold and legacy-format images unoptimized. |
be-sustainableno-wasteful-work | issues | high | The anonymous reading path downloads large optional bundles and measurable unused code. f10 medium: Large startup bundles and blocking styles delay primary content. f11 medium: The article ships substantial unused JavaScript and CSS. |
be-sustainablethird-party-and-media-budget | pass | medium | No autoplay audio/video or advertising tracker is present; Wikimedia image/auth origins account for 205,869 third-party bytes and directly support page content/account state. |
be-agent-readystructured-agent-capabilities | pass | medium | 98% raw-HTML content coverage, semantic headings and real hrefs make encyclopedia content reliably machine-readable; MediaWiki also exposes canonical structured endpoints even though no WebMCP tool is declared. |
be-agent-readyon-device-inference | not-applicable | high | No on-device inference feature is offered or required for the audited reading/login paths. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | JS object count changed 9,582→9,595 and closures 7,942→7,944; growth was concentrated in native objects loaded by scrolling, not accumulating JS state. |
be-memory-efficientbounded-footprint | pass | medium | Baseline self size was 19.46MB with 241,701 nodes, proportionate to the content-rich homepage; common JS constructors remained modest. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appears among retained constructors; Object and closure populations were effectively stable after ten cycles. |
Provenance
Canonical report: results/atomic/reports/0374-fr_wikipedia_org.json
Report SHA-256: 066f21c3bdd6336722c5a76e24c50bd8bbaf85ba399cc322e4612fc3cf771028
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/fr_wikipedia_org/2026-07-20T08-04-32-814Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/fr_wikipedia_org/2026-07-20T08-04-32-814Z
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.