Manifest position 435 · CrUX rank bucket 1000
https://pl.wikipedia.org
Coverage complete
Coverage-complete representative audit of five public templates and one recovery state.
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 visually identical to the default light surface: white page, near-black text, and light infobox chrome. F01 medium: System dark preference leaves the article in a light theme |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation matched true and document.getAnimations() returned an empty list on the article. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast: more screenshot is pixel-equivalent in visible styling to the default capture, and captured CSS contained no prefers-contrast or forced-colors rule. F02 low: High-contrast preference is not reflected in the rendered theme |
implement-natural-interactionsview-transitions | issues | high | Runtime/CSS inspection found no view-transition usage, while navigation among home, article, category, search and login is entirely cross-document. F03 low: Article and route changes swap abruptly |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation, parallax, carousel, or scrollytelling surface exists on the representative templates, so there is no scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | high | Screenshots and runtime inspection show standard browser scrolling/links and no custom pointer-driven gesture layer that fights platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 90,608px article layout has static top chrome and no scroll-state container-query/progress implementation in captured CSS. F04 low: Long articles lack scroll-state-aware orientation chrome |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, contextual popover, or viewport-edge floating menu was exposed in the representative read, search, login, category, and error states. |
provide-guided-navigationdirects-attention | pass | high | Article/category/search templates expose descriptive headings, active tab underlines, in-page contents, and clear blue link affordances. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Home, article, category, search, login and error captures load directly into content with no interstitial or obscuring banner. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No content-obscuring modal, dialog, picker, or transient popover appears in the exercised states; standard navigation disclosures do not take over the content. |
maximize-content-reduce-noisereduced-chrome | pass | high | The article and main page dedicate the viewport to text and reference material; global chrome is compact and secondary. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At the 360x800 condition the screenshot compresses the full desktop layout into tiny text; layout measured scrollWidth 2,539 CSS px and 1,099px horizontal overflow (desktop capture also measured 1,519px overflow). F05 critical: The article is rendered as a scaled desktop canvas on a phone-sized viewport |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Captured CSS reported no @container/container-type usage; the large infobox remains desktop-sized and contributes to the scaled mobile presentation. F06 medium: Reused content components do not adapt at component level |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse target-size failed; citation links were measured at 12x12px with 0-3px safe spacing, and the runtime probe listed many visible targets under 24px high. F07 high: Many article links and citations are too small for touch |
support-core-task-successclear-purpose-and-primary-action | pass | high | Each template has a specific title and obvious read, search, login, or create action; the Poland article opens directly on content. |
support-core-task-successprimary-flow-completion | pass | high | The search URL resolves directly to the Warszawa article, article links are real URLs, and the login form exposes a single predictable submit flow. |
support-core-task-successclear-system-state-and-recovery | pass | high | The nonexistent-page state clearly says the article does not exist and offers create, search, sister-project, and home recovery links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.4s and FCP 2.7s on the representative Poland article; CLS was 0 and TBT was 0ms. F08 medium: Largest Contentful Paint is outside the good range in the lab run |
be-fast-and-stablevisual-stability | pass | high | Lighthouse measured CLS 0 and the layout observer measured only 0.0045, both within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Lighthouse measured 0ms TBT; the layout observer saw only two load tasks at 125ms and 63ms on a very large article. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse found render-blocking requests with about 250ms potential savings, a network dependency chain, and about 51KiB of cache-lifetime savings across 48 requests. F09 medium: Render-blocking and cache-lifetime opportunities delay first render |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 54KiB unused CSS and 89KiB unused JavaScript on a 697KB transfer. F10 medium: The article ships substantial unused CSS and JavaScript |
be-inclusivenames-roles-labels | issues | high | Lighthouse/axe reported the main-menu checkbox label as hidden and its aria-labelledby target as hidden/empty, leaving the form control unnamed. F11 high: The mobile main-menu checkbox has no usable associated label |
be-inclusivesufficient-contrast | pass | high | Lighthouse/axe color-contrast audit passed and text remained legible in default and contrast captures. |
be-inclusivestructure-and-focus | issues | high | Lighthouse/axe found the Poland infobox uses a colspan cell as its caption instead of a caption element, reducing table navigation context for screen readers. F12 medium: The article infobox uses a fake table caption |
be-inclusivelegible-text | pass | high | Desktop article typography uses readable line length, clear serif headings and stable body text without clipping. |
be-inclusivezoom-reflow-targets-and-media | issues | high | User scaling is allowed, but the 360x800 capture scales a desktop-width article to tiny text and Lighthouse finds undersized touch targets. F05 critical: The article is rendered as a scaled desktop canvas on a phone-sized viewport F07 high: Many article links and citations are too small for touch |
follow-best-practicesno-console-errors | pass | high | Lighthouse reported no browser console errors. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse found donate-banner__gif without explicit width and height. Although current measured CLS is low, the element has no reserved aspect ratio. F13 low: A lazy donation image lacks intrinsic dimensions |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed valid-source-maps for large first-party JavaScript; console errors, BFCache, paste and permission-on-load checks passed. F14 low: Large first-party JavaScript lacks valid source maps |
be-discoverabletitle-and-description | issues | high | Lighthouse SEO failed meta-description on the Poland article, while the title was descriptive and unique. F15 medium: Public article pages have no meta description |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found five rendered interlanguage anchors with href=javascript:void(0), so crawlers cannot follow those destinations; robots and viewport audits otherwise passed. F16 medium: Some interlanguage links use javascript:void(0) |
be-discoverablecanonical-and-indexing-signals | pass | high | The page returned HTTP 200, exposed a valid canonical URL, a non-blocking robots meta policy, and Lighthouse passed canonical/robots checks. |
be-discoverablestructured-and-shareable-metadata | pass | high | Runtime inspection found one JSON-LD block and five Open Graph properties describing the article. |
be-private-and-securesecure-transport-and-headers | issues | high | The HTTPS response has HSTS and nosniff, but its CSP script-src includes unsafe-inline and unsafe-eval plus many third-party host wildcards. F17 high: The CSP permits unsafe inline script and eval across a very broad source list |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Lighthouse reported NetworkProbeLimit and WMF-Uniq on auth.wikimedia.org and intake-analytics.wikimedia.org; response headers also set SameSite=None cookies, including WMF-Uniq with a one-year expiry. F18 medium: Cross-site authentication and analytics set third-party cookies |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Lighthouse passed notification/geolocation-on-load checks; login uses autocomplete="username webauthn" and current-password, exposing conditional WebAuthn assistance. |
be-private-and-securedefensive-browser-policies | issues | high | The main response has HSTS, CSP and nosniff but no frame-ancestors/X-Frame-Options, Referrer-Policy, or Permissions-Policy header. F19 high: Clickjacking and privacy-policy response headers are absent |
be-resilientprogressive-enhancement | pass | high | The server returned 2,044,082 bytes of complete article HTML with HTTP 200, and article content is present before enhancement rather than in an empty app shell. |
be-resilientresilient-runtime-behaviour | pass | high | Read, category, search and login states rendered coherently; no cut-off overlay or blank reactive shell was observed. |
be-resilientoffline-and-installable | not-applicable | high | Wikipedia is a public content MPA rather than an installed app flow; offline/installability is contextual and was not treated as a requirement. |
be-resilientnetwork-and-http-failure-states | pass | high | The nonexistent article route renders an actionable recovery page rather than a blank shell or misleading success state. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang="pl" and dir="ltr"; captured CSS includes logical inline/block properties, and the UI exposes 306 language variants. |
be-internationalisedlocale-aware-data | pass | high | Dates, numbers and labels on the representative Polish article are rendered in Polish conventions, and language switching is prominently available. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited templates render encyclopedic content and login/search controls but no time-zone-sensitive scheduling or event flow. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, disguised advertising, forced continuity, confirmshaming, or nagging interruption appeared on any exercised path. |
be-trustworthyhumane-error-handling | pass | high | The login form uses visible labels, preserves a conventional single-submit flow, and provides password/login help links; the nonexistent-page state offers recovery choices. |
be-trustworthytrustworthy-input-assistance | pass | high | Login fields use username webauthn and current-password autocomplete tokens and have associated visible labels. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, cancellation, or sensitive account-management action was in scope; login itself was inspected under the dedicated auth checks. |
be-sustainableoptimised-assets | pass | high | Lighthouse passed responsive image sizing and total transfer was 697KB for a very long, image-rich national article; the sole unsized image was an empty lazy donation asset. |
be-sustainableno-wasteful-work | issues | high | For a text article, Lighthouse identified 143KiB combined unused CSS/JS, about one fifth of the 697KB load. F20 low: Unused front-end code creates avoidable transfer and processing |
be-sustainablethird-party-and-media-budget | pass | high | The 48-request, 697KB load contains no autoplay background video and no third-party media payload dominating the article; visible media supports the encyclopedic content. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing transactional capability or WebMCP surface was present; this emerging capability is optional for a read-oriented encyclopedia. |
be-agent-readyon-device-inference | not-applicable | high | The read/search experience does not require an on-device inference feature; absence is an emerging opportunity rather than a failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten open/close menu cycles, heap nodes decreased from 155,695 to 155,440 and self-size decreased from 10,102,133 to 10,077,479 bytes. |
be-memory-efficientbounded-footprint | pass | high | The login page heap was about 10.1MB across roughly 155k nodes, proportionate to the rendered MediaWiki shell and form. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Repeated menu interaction did not produce total retained growth; closure count changed only from 5,956 to 5,969 while overall nodes and bytes fell. |
Provenance
Canonical report: results/atomic/reports/0435-pl_wikipedia_org.json
Report SHA-256: 9ba81d848b7d07bd830bc76feabf982a1b5880bb4d75a5848431a50034557ca7
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/pl_wikipedia_org/2026-07-20T19-36-31-839Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/pl_wikipedia_org/2026-07-20T19-36-31-839Z
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.