Manifest position 312 · CrUX rank bucket 1000

https://ru.wikipedia.org

Coverage complete

Coverage-complete audit of five representative public templates/journeys. Authenticated editing/account flows, every article variant, multimedia playback and write operations were not covered.

Attempts

1 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	Under prefers-color-scheme: dark, the probe reported a light body (rgb(248,249,250)), color-scheme: normal, and the screenshot remained visually identical to light mode. The Appearance panel shows Light selected even though an Automatic option exists. F01 medium: The anonymous default fixes the site to light mode instead of following the operating-system color preference.
respect-user-preferences `respects-reduced-motion`	pass	high	The preference probe found a global reduced-motion rule reducing animation and transition durations; no active animations remained.
respect-user-preferences `respects-contrast`	pass	high	Forced-colors/increased-contrast emulation produced white text on black with a cyan 2px focus outline.
implement-natural-interactions `view-transitions`	issues	high	The recorded homepage-to-Moscow search flow completes, but the CSS probe found no view-transition rules and the video shows a direct page swap. F02 low: Primary cross-document navigation changes state abruptly without a declarative view transition.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	The audited encyclopedia templates have no scrollytelling, carousel, parallax, or scroll-triggered state that needs a scroll timeline.
implement-natural-interactions `physical-gestures`	not-applicable	high	The audited read, list, search and recovery journeys expose no swipe, drag, pull-to-refresh or snap interaction to judge.
provide-guided-navigation `scroll-state-aware-chrome`	pass	high	The long article exposes a table of contents and sticky pinned containers plus a sticky header.
provide-guided-navigation `anchored-positioning`	pass	high	Desktop screenshots show appearance and article chrome placed inside the viewport without covering primary content.
provide-guided-navigation `directs-attention`	pass	high	Article headings, 1,492 fragment links, a visible table of contents and clear search destination orient users.
maximize-content-reduce-noise `no-intrusive-interruptions`	pass	high	All five initial screenshots had no full-viewport overlay; DOM probes found no visible full-viewport interruption.
maximize-content-reduce-noise `semantic-dismissible-primitives`	pass	high	No modal flow appeared in the representative journeys; disclosure controls use labelled native checkbox controls and remain dismissible.
maximize-content-reduce-noise `reduced-chrome`	pass	high	Desktop pages devote the central viewport to article/list content with restrained navigation and no ads.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	issues	high	Every page probe reported meta viewport content="width=1120". At a 360x800 device viewport, layout measured a 1120 to 1294 CSS-pixel viewport and the screenshots show a full desktop article scaled to unreadably small text. F03 high: The pages advertise a fixed 1120px viewport, causing desktop layouts and tiny text to be scaled into narrow mobile screens.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	Every page probe reported meta viewport content="width=1120". At a 360x800 device viewport, layout measured a 1120 to 1294 CSS-pixel viewport and the screenshots show a full desktop article scaled to unreadably small text. F03 high: The pages advertise a fixed 1120px viewport, causing desktop layouts and tiny text to be scaled into narrow mobile screens.
adapt-to-the-form-factor `input-modality-aware`	issues	high	Lighthouse failed target-size; examples include a 60x16 History link and 12x12 citation links. The page probe lists many 14 to 17px-high interactive targets. F04 medium: Many inline links and citation controls are too small or tightly spaced for touch.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	The homepage identifies Wikipedia as a free encyclopedia and prominently presents search; article and category H1s identify their purpose.
support-core-task-success `primary-flow-completion`	pass	high	The recorded search journey submits “Москва” and reaches the Moscow article successfully.
support-core-task-success `clear-system-state-and-recovery`	pass	high	A real missing URL returns HTTP 404, noindex/nofollow, explains that no article exists and offers search and creation recovery links.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured FCP 4.5s, LCP 4.5s, Speed Index 5.7s and performance 0.71. Layout also observed a 459ms main-thread task during article startup, although CLS stayed near zero and TBT was only 50ms. F05 high: The representative article misses the good LCP range under Lighthouse mobile conditions.
be-fast-and-stable `visual-stability`	pass	high	Layout observation measured CLS from 0 to 0.0038 across all templates; Lighthouse article CLS was 0.
be-fast-and-stable `efficient-main-thread`	issues	high	Lighthouse measured FCP 4.5s, LCP 4.5s, Speed Index 5.7s and performance 0.71. Layout also observed a 459ms main-thread task during article startup, although CLS stayed near zero and TBT was only 50ms. F05 high: The representative article misses the good LCP range under Lighthouse mobile conditions.
be-fast-and-stable `efficient-resource-delivery`	issues	high	Lighthouse identified three render-blocking stylesheets and estimated 54 KiB savings from efficient cache lifetimes; key ResourceLoader CSS and startup JS had five-minute cache lifetimes. F06 medium: Short-lived cache entries and render-blocking styles add avoidable work to article startup.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 162 KiB of unused JavaScript and 89 KiB of unused CSS, including a roughly 400 KiB ResourceLoader JavaScript response. F07 medium: The article ships substantial JavaScript and CSS unused during the measured load.
be-inclusive `names-roles-labels`	issues	high	Lighthouse accessibility scored 0.89 and failed label because the checkbox references an aria-hidden label. It also failed table-fake-caption because the Russia infobox starts with a colspan cell instead of caption. F08 high: The mobile navigation toggle lacks a usable label in the accessibility tree, and an infobox uses a fake table caption.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse failed link-in-text-block on article links such as “Россия (значения)”, reporting only 1.32:1 contrast against surrounding text and no persistent non-color styling. F09 medium: Inline links rely on color alone and do not reach 3:1 contrast against surrounding text.
be-inclusive `structure-and-focus`	issues	high	Lighthouse accessibility scored 0.89 and failed label because the checkbox references an aria-hidden label. It also failed table-fake-caption because the Russia infobox starts with a colspan cell instead of caption. F08 high: The mobile navigation toggle lacks a usable label in the accessibility tree, and an infobox uses a fake table caption.
be-inclusive `legible-text`	issues	high	Every page probe reported meta viewport content="width=1120". At a 360x800 device viewport, layout measured a 1120 to 1294 CSS-pixel viewport and the screenshots show a full desktop article scaled to unreadably small text. F03 high: The pages advertise a fixed 1120px viewport, causing desktop layouts and tiny text to be scaled into narrow mobile screens.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	Every page probe reported meta viewport content="width=1120". At a 360x800 device viewport, layout measured a 1120 to 1294 CSS-pixel viewport and the screenshots show a full desktop article scaled to unreadably small text. Lighthouse failed target-size; examples include a 60x16 History link and 12x12 citation links. The page probe lists many 14 to 17px-high interactive targets. Lighthouse failed unsized-images. The article probe found 277 images, 73 without an alt attribute and one without complete width/height attributes; category and 404 templates also each had one image missing dimensions. F03 high: The pages advertise a fixed 1120px viewport, causing desktop layouts and tiny text to be scaled into narrow mobile screens. F04 medium: Many inline links and citation controls are too small or tightly spaced for touch. F10 medium: Some article images lack dimensions or useful alternatives.
follow-best-practices `no-console-errors`	pass	high	Lighthouse found no console-error items during the article load.
follow-best-practices `sound-document-and-assets`	issues	high	Lighthouse failed unsized-images. The article probe found 277 images, 73 without an alt attribute and one without complete width/height attributes; category and 404 templates also each had one image missing dimensions. F10 medium: Some article images lack dimensions or useful alternatives.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse failed valid-source-maps and inspector-issues for the representative article. F11 low: Large first-party bundles lack valid source maps and Chrome recorded Inspector issues.
be-discoverable `title-and-description`	issues	high	Lighthouse failed meta-description. Probes found no description on homepage, Russia article, category, Moscow article or 404; the category also had no JSON-LD and only og:title/og:type, while the article had JSON-LD and an OG image. F12 medium: Public article and listing templates omit meta descriptions, and structured/share metadata is inconsistent across templates.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Every page probe reported meta viewport content="width=1120". At a 360x800 device viewport, layout measured a 1120 to 1294 CSS-pixel viewport and the screenshots show a full desktop article scaled to unreadably small text. F03 high: The pages advertise a fixed 1120px viewport, causing desktop layouts and tiny text to be scaled into narrow mobile screens.
be-discoverable `canonical-and-indexing-signals`	pass	high	Public templates return 200 with self-canonical URLs; robots.txt publishes a sitemap and the 404 correctly returns 404 with noindex/nofollow.
be-discoverable `structured-and-shareable-metadata`	issues	high	Lighthouse failed meta-description. Probes found no description on homepage, Russia article, category, Moscow article or 404; the category also had no JSON-LD and only og:title/og:type, while the article had JSON-LD and an OG image. F12 medium: Public article and listing templates omit meta descriptions, and structured/share metadata is inconsistent across templates.
be-private-and-secure `secure-transport-and-headers`	issues	high	Headers show CSP with unsafe-inline and unsafe-eval plus broad source lists, no Referrer-Policy, Permissions-Policy or X-Frame-Options/frame-ancestors. Cookie audit found ruwikimwuser-sessionId without Secure and with SameSite=None. F13 high: Transport is HTTPS and HSTS-protected, but browser defenses are weakened by a broad unsafe CSP, missing policies and one insecure first-party session identifier cookie.
be-private-and-secure `data-minimisation-and-third-parties`	pass	high	Tracker capture found no known trackers; third-party origins were Wikimedia infrastructure and Lighthouse measured only 1.4 KiB third-party transfer.
be-private-and-secure `in-context-permissions-and-modern-auth`	pass	high	No permission prompt or permission-dependent behavior occurred on load or in public read/search flows; authentication was not required for core content.
be-private-and-secure `defensive-browser-policies`	issues	high	Headers show CSP with unsafe-inline and unsafe-eval plus broad source lists, no Referrer-Policy, Permissions-Policy or X-Frame-Options/frame-ancestors. Cookie audit found ruwikimwuser-sessionId without Secure and with SameSite=None. F13 high: Transport is HTTPS and HSTS-protected, but browser defenses are weakened by a broad unsafe CSP, missing policies and one insecure first-party session identifier cookie.
be-resilient `progressive-enhancement`	pass	high	Discoverability found 100% rendered-word coverage in raw server HTML, with title and H1 present and no JavaScript shell.
be-resilient `resilient-runtime-behaviour`	pass	high	Menus could be repeatedly opened and closed, search navigation completed, and no overlay remained stuck after 30 cycles.
be-resilient `offline-and-installable`	not-applicable	high	This public multi-page encyclopedia is not presented as an installable application; offline installation is contextual and not required for the audited public reading scope.
be-resilient `network-and-http-failure-states`	pass	high	The representative missing route returns a correct 404 and supplies clear search and creation recovery.
be-internationalised `lang-dir-and-logical-properties`	pass	high	All templates declare lang=ru and dir=ltr; CSS inspection found logical properties in use.
be-internationalised `locale-aware-data`	pass	high	Russian-language headings, dates, article counts and interface text are rendered with locale-appropriate forms across templates.
be-internationalised `time-zone-correctness`	not-applicable	high	The representative pages contain reference prose and localized calendar dates, not a scheduling or event-time workflow requiring user time-zone conversion.
be-trustworthy `no-dark-patterns`	pass	high	No ads, consent wall, disguised action, forced continuity or confirmshaming appeared on any representative public path.
be-trustworthy `humane-error-handling`	pass	high	The 404 state is plain-language, returns the right status, preserves the query and offers several recovery options without blaming the user.
be-trustworthy `trustworthy-input-assistance`	issues	high	DOM probes across templates found autocomplete="off" on the primary search input, despite search being a repeated, non-sensitive task. F14 low: Search inputs explicitly disable browser autocomplete.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	No commercial flow exists, and optional authenticated account management was excluded from the public read/search audit scope.
be-sustainable `optimised-assets`	pass	high	Lighthouse total transfer was 934 KiB and image-delivery reported no savings; media does not autoplay.
be-sustainable `no-wasteful-work`	issues	high	Lighthouse estimated 162 KiB unused JavaScript and 89 KiB unused CSS. Total transfer was otherwise proportionate at 934 KiB and no autoplay media or known trackers were observed. F15 medium: The reading view downloads roughly a quarter-megabyte of code and styles unused in the measured journey.
be-sustainable `third-party-and-media-budget`	pass	high	No known trackers were detected, Lighthouse third-party transfer was about 1.4 KiB, and article audio/video did not autoplay.
be-agent-ready `structured-agent-capabilities`	issues	medium	Discoverability measured 100% raw-HTML content coverage and article JSON-LD is present, but probes found no WebMCP or agentic tool registration. F16 low: Wikipedia is highly relevant to agents and serves crawlable structured content, but exposes no explicit safe agent capabilities for search or article operations.
be-agent-ready `on-device-inference`	not-applicable	high	The representative read/search journeys do not require local generative inference; adding it is an optional product choice rather than necessary functionality.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	Across 30 menu cycles DOM nodes rose once from 2,429 to 3,324 then stayed flat; JS heap fell from 26.0 MB after 20 cycles to 14.1 MB after GC at 30 cycles.
be-memory-efficient `bounded-footprint`	pass	high	Baseline category heap was 15.0 MB self size with 214,847 heap nodes, proportionate to a large encyclopedia template.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Heap summaries listed no Detached constructors and DOM node count stayed exactly 3,324 after cycles 10, 20 and 30.

Provenance

Canonical report: results/atomic/reports/0312-ru_wikipedia_org.json
Report SHA-256: 13c0282b8c48b70125f173adb009be884c73dc78fe3ac690ecaacc73fae3b331
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ru_wikipedia_org/2026-07-19T21-43-10-288Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ru_wikipedia_org/2026-07-19T21-43-10-288Z
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.