Manifest position 617 · CrUX rank bucket 1000
https://pt.wikipedia.org
Coverage complete
Coverage-complete representative audit of four MediaWiki templates/flows. Excluded authenticated editing/account flows and page archetypes sharing the same Vector/MediaWiki shell.
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 light screenshot, and computed styles report color-scheme: normal with a light body surface. F-01 high: The interface does not follow the system dark-color preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion capture plus getAnimations() found no active animation or auto-advance. |
respect-user-preferencesrespects-contrast | pass | high | High-contrast preference capture retained visible text and controls. |
implement-natural-interactionsview-transitions | issues | high | The live CSS probe found no view-transition usage although the browser supports it. F-02 low: Page navigations and state changes swap without View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked visual motion exists on the representative templates, so there is no implementation to move off-thread. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The reading, category and search templates expose no custom swipe, pull, carousel or snap gesture. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | After scrolling 1200px, the table of contents remained at y=72 while the article header moved offscreen. |
provide-guided-navigationanchored-positioning | issues | high | The live CSS probe found no anchor-name or position-anchor rules on an interface with multiple menus. F-03 low: Menus and transient controls do not use CSS anchor positioning. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show active page tabs, selected appearance controls, section hierarchy and persistent table of contents cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No load-time overlay or interstitial obscured any of the four representative pages. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The live semantic probe found 0 dialog, 0 popover, and 0 details elements despite menu/disclosure controls in the page chrome. F-04 low: Transient/disclosure UI is not built with modern semantic overlay primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Article and category desktop screenshots prioritize content, with slim global chrome and no advertising. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At requested viewport 360x800, every layout capture reports innerWidth/clientWidth 1120 and meta viewport width=1120; mobile screenshots show unreadably small text and controls. F-05 critical: The site forces a 1120 CSS-pixel viewport on phones, producing a tiny scaled desktop layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The live CSS probe found no @container usage across the article interface. F-06 medium: Components do not use container-level adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The live probe counted 2,829 rendered targets below 24px in at least one dimension; Lighthouse target-size failed. Keyboard focus was visible. F-07 high: Thousands of links and controls are too small for reliable touch input. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, article, category and search screenshots have explicit headings and clear read/search/navigation actions. |
support-core-task-successprimary-flow-completion | pass | high | Article reading, category navigation and search submission all completed without an account wall or dead end. |
support-core-task-successclear-system-state-and-recovery | pass | high | The no-results search clearly states that no result was produced and preserves the query with controls to retry or refine. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.6s (score 0.18), despite a warm desktop trace measuring 808ms, indicating a material mobile/cold-load problem. F-08 high: Mobile Largest Contentful Paint is slow. |
be-fast-and-stablevisual-stability | pass | high | Layout observer measured CLS 0.00023 on the article and 0 on the other templates. |
be-fast-and-stableefficient-main-thread | pass | high | Trace measured one 118.56ms task and 68.56ms TBT, with no sustained long-task pattern. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 130 requests and 3,193,306 transferred bytes, including 116 images/2,575,721 bytes; Lighthouse reports 177KiB cache and 150ms render-blocking savings. F-09 medium: The article loads a large eager image set and avoidable blocking/cache cost. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 49KiB unused CSS and 86KiB unused JavaScript. F-10 medium: The page ships avoidable unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed image-alt and label; the live probe found one unlabelled form control, and the image audit reported many null alt values. F-11 high: Images and a form control lack accessible alternatives or labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed link-in-text-block, showing that links in body text are not distinguishable without color. F-12 medium: Inline links rely on color alone. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed table-fake-caption and agent-accessibility-tree. The page otherwise has one main landmark and visible focused-link outline. F-13 medium: Parts of the accessibility structure are malformed. |
be-inclusivelegible-text | issues | high | At 360px the forced 1120px layout renders body text at roughly one-third scale, materially harming reading comfort. F-05 critical: The site forces a 1120 CSS-pixel viewport on phones, producing a tiny scaled desktop layout. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport probe returns width=1120 and Lighthouse target-size fails; 360px screenshots render a scaled-down desktop canvas. F-14 high: The fixed 1120px viewport prevents normal mobile reflow and leaves targets undersized. |
follow-best-practicesno-console-errors | pass | high | Lighthouse console-errors audit passed with zero logged errors. |
follow-best-practicessound-document-and-assets | issues | high | Image primitive reports 2 missing-dimension images and Lighthouse unsized-images fails; Lighthouse estimates 96KiB image-delivery savings. F-15 medium: Some images omit intrinsic dimensions and image delivery is inefficient. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed inspector-issues and valid-source-maps, while deprecations, BFCache, permission-on-load and paste checks passed. F-16 low: DevTools reports unresolved inspector and source-map hygiene issues. |
be-discoverabletitle-and-description | issues | high | The live probe and discoverability primitive found a descriptive title but no meta description; Lighthouse meta-description failed. F-17 medium: Public article pages omit a meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | All 4,269 anchors have hrefs and robots allows indexing, but the viewport is fixed to width=1120 rather than mobile-friendly. F-05 critical: The site forces a 1120 CSS-pixel viewport on phones, producing a tiny scaled desktop layout. |
be-discoverablecanonical-and-indexing-signals | pass | high | Article returned HTTP 200, canonical matched, robots allowed indexing and Lighthouse canonical/robots/hreflang audits passed. |
be-discoverablestructured-and-shareable-metadata | pass | high | The article exposes one JSON-LD block and five Open Graph fields aligned to visible article content. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show CSP with unsafe-inline and unsafe-eval. Cookie evidence shows six Secure cookies all marked SameSite=None. F-18 medium: The CSP permits unsafe script/style execution and cookies use SameSite=None broadly. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker scan found no known trackers or analytics domains; third-party origins were Wikimedia infrastructure and no secrets were exposed. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Lighthouse confirms no notification or geolocation prompt on load; the audited public reading/search flows require no authentication. |
be-private-and-securedefensive-browser-policies | issues | high | Header evidence finds no frame-ancestors/X-Frame-Options, Referrer-Policy, or Permissions-Policy, while HSTS and nosniff are present. F-19 medium: Several defensive browser policies are absent. |
be-resilientprogressive-enhancement | pass | high | Raw server HTML contains 100% of rendered content words and retains title and h1 without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Search, navigation and sticky table-of-contents behavior remained coherent in exercised states with no console errors. |
be-resilientoffline-and-installable | not-applicable | high | Wikipedia is a public content MPA rather than an installable app; offline installation is not required for the audited reading journey. |
be-resilientnetwork-and-http-failure-states | pass | high | The search empty state provides an explicit message, retained query and retry/refinement controls; server-rendered pages avoid a blank client shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The Portuguese article declares html lang=pt and dir=ltr and renders localized navigation/content. |
be-internationalisedlocale-aware-data | pass | medium | Portuguese labels, numeric separators and article date presentation are localized consistently on sampled templates. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative encyclopedia reading, category and search paths do not schedule events or expose user-sensitive time-zone calculations. |
be-trustworthyno-dark-patterns | pass | high | No ads, consent wall, confirmshaming, forced continuity or disguised controls appeared on any sampled path. |
be-trustworthyhumane-error-handling | pass | high | The no-results search uses neutral language, preserves the query, and offers advanced-search refinement rather than blaming the user. |
be-trustworthytrustworthy-input-assistance | pass | high | The only user-entered field in scope is search; it has type=search, an accessible search interface and retained query state. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, payment, consent, or account-management flow is part of the audited public encyclopedia journey. |
be-sustainableoptimised-assets | issues | high | Images evidence reports 80 below-fold images without lazy loading and 98 legacy-format derivatives; HAR attributes 2.58MB to images. F-20 medium: The article eagerly requests many legacy-format, below-fold images. |
be-sustainableno-wasteful-work | pass | high | Trace showed only one bounded long task and tracker scan found no analytics/background beacon churn. |
be-sustainablethird-party-and-media-budget | issues | high | The HAR transfers 3.19MB, of which 2.54MB is from upload.wikimedia.org, before the reader scrolls through the long article. F-21 medium: Resource use is disproportionate for an initial text-article view. |
be-agent-readystructured-agent-capabilities | issues | high | Discoverability reports 100% raw-HTML coverage and JSON-LD exists, but Lighthouse agent-accessibility-tree fails and no structured agent tool interface was detected. F-22 low: Machine-readable content is strong, but interactive semantics are not fully agent-ready. |
be-agent-readyon-device-inference | not-applicable | high | Server-rendered reference content does not need on-device generation or summarization to complete its core reading/search tasks. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten menu toggles the snapshot delta was +1,427 nodes (+0.36%) and +2.09MB; no unbounded trend or Detached constructor appeared in the retained summary. |
be-memory-efficientbounded-footprint | issues | high | Post-interaction heap summary contains 395,360 nodes and 30,547,712 self-size bytes. Ten menu toggles changed totals by +1,427 nodes and +2,087,663 bytes, without a clear Detached constructor signal. F-23 medium: The memory footprint is heavy for a mostly static article. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither baseline nor post summary exposed a Detached constructor among retained top constructors after ten toggles. |
Provenance
Canonical report: results/atomic/reports/0617-pt_wikipedia_org.json
Report SHA-256: f018f227c8132a9e98e27d299c04314eb14d1e689653fa7e87b94ab2e2cc5c6f
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/pt_wikipedia_org/2026-07-21T23-23-15-739Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/pt_wikipedia_org/2026-07-21T23-23-15-739Z
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.