Manifest position 954 · CrUX rank bucket 1000
https://es.wikipedia.org
Coverage complete
Atomic coverage complete across five representative templates and active conditions.
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-mode screenshot is visually identical to the light capture; the preference probe reports prefers-color-scheme: dark=true, root color-scheme "normal", body background rgb(248,249,250), and dark text. F-001 high: The default experience does not follow the system dark-color preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned an empty list and no auto-advance or media was present. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot retains readable white text and yellow links/controls with visible outlines. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no view-transition declaration or CSS, while navigation is an MPA of ordinary article links. F-002 low: Article and navigation changes are abrupt full-document swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface exists on the sampled templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The sampled encyclopedia reading, search, login and error flows have no gesture-driven interaction to evaluate. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Article DOM exposes fixed/sticky chrome and a table-of-contents navigation surface for long-page orientation. |
provide-guided-navigationanchored-positioning | issues | high | The navigation probe found nine aria-haspopup controls implemented mainly as input role=button checkboxes and zero anchor positioning rules. F-003 low: Dropdown navigation relies on checkbox-driven custom controls rather than anchored positioning. |
provide-guided-navigationdirects-attention | pass | high | Article heading hierarchy, table of contents, current tab styling and direct fragment links provide clear attention cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | All five first-load screenshots show content immediately with no obscuring popup or interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Across the article DOM there were zero popover, dialog, or details elements; navigation identified multiple checkbox inputs exposed as buttons. F-004 medium: Transient menus use custom checkbox controls instead of semantic popover primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Desktop article and homepage screenshots devote the main surface to reference content with compact persistent chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Every 360x800 layout capture reported viewport meta width=1120, innerWidth=1120 and visual scale 0.3214. Screenshots show a desktop multi-column UI scaled down to unreadably small text rather than reflowed. F-005 high: The desktop skin fixes its layout viewport at 1120 CSS pixels on a 360px emulated screen. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe found zero container-query rules; the narrow screenshot remains the same desktop composition at a reduced visual scale. F-006 medium: Reusable article chrome does not expose container-based adaptation. |
adapt-to-the-form-factorinput-modality-aware | pass | high | Lighthouse target-size passed; primary menu controls are 44px and sampled primary links/controls displayed a 1-2px focus outline. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, article, search, login and error screenshots have descriptive headings and clear next actions. |
support-core-task-successprimary-flow-completion | pass | high | Exact search completed to the matching article; search results and login forms loaded with predictable actions and no account wall for reading. |
support-core-task-successclear-system-state-and-recovery | issues | high | After actively clicking Acceder with both fields empty, the captured form remained unchanged with no inline error, required-field cue, or summary. F-007 medium: Submitting the empty sign-in form produces no visible validation or recovery message. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 3.8s and FCP 3.2s (performance 0.82). The direct trace was faster at 1.21s LCP, showing variability rather than a consistently fast load. F-008 high: Cold-load LCP misses the good Core Web Vitals range. |
be-fast-and-stablevisual-stability | pass | high | Five layout captures measured CLS from 0 to 0.00043; Lighthouse measured CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | Direct trace recorded one 72ms long task and 22ms TBT; Lighthouse measured 4.5ms TBT. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR identified three VeryHigh-priority parser-inserted stylesheets and ten image responses without useful cache headers; Lighthouse also flagged render-blocking requests and estimated 101KiB cache savings. F-009 medium: Render-blocking styles and weak image cache delivery add avoidable work. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 86KiB unused JavaScript and 43KiB unused CSS; one 242KiB module bundle was 36% unused and two stylesheet groups were 80-97% unused. F-010 medium: The article ships substantial code not used during the initial reading task. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility scored 0.83 and reported two content images without alt, their wrapping links without discernible names, and a checkbox menu whose associated label is hidden from assistive technology. The image probe found 10 img elements with no alt attribute. F-011 high: Images, image links, and a menu control lack dependable accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found link-to-surrounding-text contrast of 1.32:1 on hatnotes and captions, below the 3:1 differentiation threshold, with no underline. F-012 medium: Inline links rely on color that is too similar to surrounding text. |
be-inclusivestructure-and-focus | issues | high | The homepage probe found h1 “Wikipedia:Portada” and h1 “Bienvenidos a Wikipedia”. The focus probe found multiple focusable nav links with computed outline none, while other controls correctly displayed a 2px focus ring. F-013 medium: The homepage exposes two h1 elements and some focused navigation links lack a visible indicator. |
be-inclusivelegible-text | pass | high | Desktop screenshots show comfortable article measure, clear serif/sans hierarchy and no clipping in the sampled content. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a 360px emulated screen, browser layout remained 1120 CSS pixels wide and was scaled to 0.3214; dense text and controls become extremely small even though no horizontal scrollbar appears. F-014 high: Narrow-screen reflow is defeated by a fixed 1120px viewport. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no logged browser errors. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive and Lighthouse both found an unsized Wikipedia wordmark/donation image; Lighthouse specifically reported an img without width and height. F-015 low: At least one rendered image has no intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse best-practices scored 0.77; valid-source-maps failed for large first-party bundles with 404/invalid maps, and the Issues panel audit logged cookie issues. F-016 low: Production JavaScript source maps are broken or absent and DevTools records cookie issues. |
be-discoverabletitle-and-description | issues | high | Homepage, article, search, login and error probes all returned description=null; Lighthouse’s meta-description audit failed. F-017 medium: Public pages have descriptive titles but no meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Links have real href values, viewport metadata is present, robots.txt is valid, and raw HTML contains the article links/content. |
be-discoverablecanonical-and-indexing-signals | issues | medium | Canonical and hreflang signals passed Lighthouse and robots.txt is valid, but a direct request to /sitemap.xml returned HTTP 404. F-018 low: The conventional sitemap endpoint returns 404. |
be-discoverablestructured-and-shareable-metadata | pass | high | The article exposes structured data and social metadata matching its visible World Wide Web entity. |
be-private-and-securesecure-transport-and-headers | pass | high | HTTPS, HSTS preload, nosniff and a CSP are present; no exposed secrets or mixed-content error was found. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Lighthouse reported three third-party cookies. The cookie probe found six cookies, all SameSite=None, including one non-Secure, non-HttpOnly session-id cookie; the HAR recorded a CentralAutoLogin redirect and 15 cross-origin requests. No known commercial trackers or exposed secrets were found. F-020 medium: Anonymous article loads create cross-subdomain cookie and auto-login dependencies. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; login inputs use username webauthn and current-password autocomplete tokens. |
be-private-and-securedefensive-browser-policies | issues | high | Headers include strong HSTS and nosniff, but CSP permits unsafe-inline and unsafe-eval across a very broad host list; no frame-ancestors/X-Frame-Options, Referrer-Policy, or Permissions-Policy was observed. F-019 high: The CSP is broad and key defensive policies are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability capture found 99% raw-HTML content coverage, title and h1 present, and no JS shell. |
be-resilientresilient-runtime-behaviour | issues | medium | The navigation probe found multiple input role=button elements with aria-haspopup but null aria-expanded and aria-controls, increasing the risk that visual and accessibility state diverge. F-021 medium: Custom checkbox menus lack explicit expanded/control state relationships. |
be-resilientoffline-and-installable | issues | high | Homepage and article probes found no manifest and no controlling service worker. The content itself is strongly server-rendered, but a disconnected revisit has no explicit fallback. F-022 low: The public reference experience has no manifest, service worker, or offline fallback. |
be-resilientnetwork-and-http-failure-states | pass | high | The nonexistent-page route presents a specific explanation plus links to search, related pages, cache recovery and create flow. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Pages declare lang=es and dir=ltr, provide extensive language alternatives, and the CSS probe found logical properties. |
be-internationalisedlocale-aware-data | pass | high | The server-rendered Spanish experience localizes labels, number formatting and language navigation consistently on all sampled templates. |
be-internationalisedtime-zone-correctness | not-applicable | high | The sampled pages render reference prose and forms but no user-facing scheduled or transactional time data. |
be-trustworthyno-dark-patterns | pass | high | No ads, consent nag, forced continuity, pricing ambiguity or obstructive cancellation pattern appeared in sampled public and login flows. |
be-trustworthyhumane-error-handling | pass | medium | Representative screenshots, DOM probes, Lighthouse and active path review found direct support for this check on the sampled templates. |
be-trustworthytrustworthy-input-assistance | pass | high | Login fields have labels and autocomplete="username webauthn" / "current-password"; search fields use the search input type. |
be-trustworthysafe-commercial-and-account-flows | pass | high | No commercial flow exists; the sampled account entry clearly labels sign-in, recovery and account-creation actions without an upsell. |
be-sustainableoptimised-assets | issues | high | The image probe found 14 legacy-format images, 10 below-fold images without lazy loading, one oversized asset and two without responsive sources. HAR transfer was 1.32MB, including an individual PNG of 464KB and 874KB total image transfer. F-023 medium: The article transfers oversized legacy images and does not defer most below-fold media. |
be-sustainableno-wasteful-work | pass | high | Direct trace showed only one modest long task and no ongoing animation; tracker probe found no known analytics trackers. |
be-sustainablethird-party-and-media-budget | pass | high | No autoplay audio/video or known tracker was present; cross-origin bytes are predominantly user-valued Wikimedia article images. |
be-agent-readystructured-agent-capabilities | not-applicable | high | WebMCP and agent actions are emerging and this public encyclopedia exposes no transactional capability that needs agent tool registration. |
be-agent-readyon-device-inference | not-applicable | high | No summarization or language-model feature is offered; the emerging on-device inference opportunity is not required for core reading. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten menu toggles, nodes rose only 378 (0.19%) and native nodes/closures were flat; the 1.95MB total increase was almost entirely strings, with no detached-node signal in summaries. |
be-memory-efficientbounded-footprint | pass | high | Article heap was 13.6MB self size and about 199k nodes, proportionate to a long illustrated article with nearly 700 links. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Baseline/post summaries show native nodes 106,767 to 106,761 and closures 5,827 to 5,824; no Detached* constructor appeared among retained populations. |
Provenance
Canonical report: results/atomic/reports/0954-es_wikipedia_org.json
Report SHA-256: 14666d53dcd225c92063e60d920f160ef0c556e2014163b10cb915f8b4ea8a5d
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/es_wikipedia_org/2026-07-24T02-56-14-816Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/es_wikipedia_org/2026-07-24T02-56-14-816Z
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.