Manifest position 868 · CrUX rank bucket 1000
https://ja.wikipedia.org
Coverage complete
Coverage-complete representative audit of four public templates/journeys. Not covered: authenticated editing, account creation, donation/payment completion, media playback, and every language/template variant because they require credentials, external transactions, or duplicate the selected archetypes.
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 screenshot captured with prefers-color-scheme: dark remains a white, light-themed page, despite the stylesheet containing prefers-color-scheme rules. F01 medium: The default experience does not follow the operating-system dark preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation matched true; the article reported zero active animations and zero smooth-scrolling elements. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse color contrast passed on both templates; the page uses native controls and high-contrast text in captured states. |
implement-natural-interactionsview-transitions | issues | high | The article probe found no view-transition CSS signal, while article navigation is a core cross-document interaction. F02 low: Cross-document article and search navigation swaps abruptly. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS inspection found no scroll animation timeline and trace/layout evidence found no sustained scroll-driven main-thread work. |
implement-natural-interactionsphysical-gestures | pass | high | The representative browse surfaces use native scrolling and links, with no custom pointermove or swipe interaction fighting platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The long article exposes a persistent table of contents and current-page chrome; article screenshots and DOM show orientation controls remain available. |
provide-guided-navigationanchored-positioning | pass | high | Observed menus and appearance controls remain attached to their triggers in desktop captures with no clipping or drift. |
provide-guided-navigationdirects-attention | pass | high | Active page tabs use underline/state styling, the skip link focuses visibly, and search navigation lands on a clearly titled article. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | All initial screenshots show content immediately with no modal, consent wall, interstitial or obscuring banner. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | DOM inspection found no modal flows on audited read surfaces; disclosures are native labelled checkbox/menu controls with clear close state. |
maximize-content-reduce-noisereduced-chrome | pass | high | Desktop screenshots devote the main region to encyclopedia content; controls are compact and peripheral. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 emulated viewport, layout reported clientWidth and scrollWidth of 1120 and the DOM probe found meta viewport content="width=1120"; screenshots show tiny desktop columns. F03 high: Mobile pages use a fixed 1120 CSS-pixel layout and are scaled down instead of reflowing. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no @container rules, and the 360px screenshots show the desktop composition uniformly scaled rather than cards and infoboxes recomposing. F04 medium: Reusable portal and article components do not adapt independently to their available width. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse failed target-size on the article; the probe measured theme radios at 20x20px and repeated visible controls at 22x22px. F05 medium: Many article controls and links are too small for reliable touch input. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home and article screenshots have clear headings, descriptive lead content, search, and obvious blue article links. |
support-core-task-successprimary-flow-completion | pass | high | The search journey for ウェブ completed and resolved to the World Wide Web article with coherent title and content. |
support-core-task-successclear-system-state-and-recovery | pass | high | Search visibly lands on a result article; the intentionally missing route returned an explicit HTTP 404 document rather than a blank shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured article LCP at 6.0s, FCP at 3.9s and performance score 0.64; the lighter home trace measured LCP 1.05s, showing the article template is the high-risk path. F06 high: The representative long article misses a good loading-performance bar. |
be-fast-and-stablevisual-stability | pass | high | Layout measured CLS 0.0023 on home and Lighthouse measured 0.022, both within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Home trace found one 98ms long task and 48ms TBT; article Lighthouse TBT was 150ms, below the 200ms lab proxy threshold. |
be-fast-and-stableefficient-resource-delivery | pass | high | HAR recorded 644,433 transferred bytes, compressed text, no HTTP errors and a short set of three parser stylesheets; delivery was functional though optimization opportunities are separately reported. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 123 KiB unused JavaScript and 64 KiB unused CSS on the article; HAR shows one ResourceLoader script transferring 259,136 bytes. F07 medium: Pages ship substantial JavaScript and CSS unused during initial rendering. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed image-alt and label on home, and image-alt, label and link-name on the article; the image probe counted four images without alt and the DOM probe found an unlabeled secondary search input. F08 high: Some images, links and form controls lack accessible alternatives or labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed link-in-text-block on the home page even though its numeric color-contrast audit passed. F09 medium: Inline links rely on color alone for identification. |
be-inclusivestructure-and-focus | pass | high | Lighthouse heading-order and landmark audits passed; focused skip link had a visible 2px solid outline. |
be-inclusivelegible-text | pass | high | Desktop article and login captures use readable line height, clear Japanese typography and stable content alignment. |
be-inclusivezoom-reflow-targets-and-media | pass | high | The fixed-width mobile scaling and Lighthouse target-size failure make zoom/reflow and touch use materially weaker. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console passed on home and article; no uncaught load error was observed. |
follow-best-practicessound-document-and-assets | pass | high | DOM reported HTML doctype and UTF-8; Lighthouse image aspect-ratio passed and images are served as sized thumbnails. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed valid-source-maps and inspector-issues on both home and article templates. F10 low: Production JavaScript lacks usable source maps and triggers DevTools inspector issues. |
be-discoverabletitle-and-description | issues | high | Lighthouse failed meta-description on home and article, and the article DOM probe returned description: null. F11 medium: Public pages omit meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Discoverability found 100% rendered-word coverage and real href links; robots.txt returned 200. Mobile viewport quality is reported under form-factor. |
be-discoverablecanonical-and-indexing-signals | pass | high | Both tested public pages returned 200, exposed self-canonicals and hreflang passed in Lighthouse; robots.txt was available. |
be-discoverablestructured-and-shareable-metadata | pass | high | Article probe found one JSON-LD block and five Open Graph properties aligned with the visible article. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found script-src unsafe-inline and unsafe-eval; the cookies primitive found jawikimwuser-sessionId without Secure or HttpOnly and reported SameSite=None. F12 high: The CSP permits unsafe script execution modes and one session-named cookie is not Secure. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker capture found no known tracking domains; third-party requests were Wikimedia-owned upload/auth/meta services and secrets scan found no credentials. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; login uses autocomplete="username webauthn" and current-password for conditional passkey-capable authentication. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found no frame-ancestors/X-Frame-Options, Permissions-Policy, or HTTP Referrer-Policy; only in-document referrer metadata was present. F13 medium: Several browser-enforced policy headers are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% content visibility without JavaScript with title and H1 in raw HTML; crawler and browser captures both contain content. |
be-resilientresilient-runtime-behaviour | pass | high | Menus, navigation and article content rendered without cut-off overlays or runtime errors on the exercised routes. |
be-resilientoffline-and-installable | not-applicable | high | Wikipedia is a public content MPA rather than an install-oriented application; offline installation is not necessary for the audited browse/search journey. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately missing path returned a styled HTTP 404 document with a clear Not Found state rather than a misleading success or shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | DOM reported html lang="ja" and dir="ltr"; CSS probe found logical inline/block properties and 328 language variants are exposed. |
be-internationalisedlocale-aware-data | pass | high | The Japanese main and article templates render dates, counts and language labels in Japanese locale conventions; no hand-rolled client formatting error was observed. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited read, search and sign-in surfaces expose no scheduled event or time-zone-sensitive transaction to test. |
be-trustworthyno-dark-patterns | pass | high | No ads, consent nag, forced continuity, disguised controls or confirmshaming appeared across home, article, search and login. |
be-trustworthyhumane-error-handling | pass | high | The audited search and login forms use clear persistent labels and predictable actions; no premature error state appeared before interaction. |
be-trustworthytrustworthy-input-assistance | pass | high | Login probe found username webauthn and current-password autocomplete tokens and visible associated labels. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Login is plainly labelled, offers password recovery and help, and does not introduce upsells or hidden commitments. |
be-sustainableoptimised-assets | issues | high | The images primitive found 25 below-fold images without loading="lazy" among 32 images; HAR recorded 38 image requests and 215,393 transferred image bytes. F14 medium: Most below-fold home images are fetched eagerly. |
be-sustainableno-wasteful-work | pass | high | Trace found only one long task on home and no autoplay/background media; network activity settled after load. |
be-sustainablethird-party-and-media-budget | pass | high | HAR total was 644KB with no audio/video and third-party bytes were 200KB from Wikimedia-owned infrastructure, proportionate to a media-rich portal. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The emerging WebMCP capability is not an intended surface of the audited public encyclopedia experience; machine-readable HTML and metadata were judged under discoverability. |
be-agent-readyon-device-inference | not-applicable | high | No user-facing summarisation or language-model feature is offered on these surfaces, so on-device inference has no applicable task. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After toggling the real main-menu control 20 times, heap node count changed from 184,961 to 184,512 and self size from 14,781,945 to 14,783,113 bytes, showing no retained growth trend. |
be-memory-efficientbounded-footprint | pass | high | Home heap was 14.8MB self size / 184,961 nodes and the much longer article was 34.1MB / 485,053 nodes, proportionate to the rendered content. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Repeated menu interaction reduced node count by 449 with only 1,168 bytes self-size delta; no accumulating detached-node population was indicated. |
Provenance
Canonical report: results/atomic/reports/0868-ja_wikipedia_org.json
Report SHA-256: e5330f4895015e03bd1b7b4e1b0655e75b56bc5b3b176ed924cc18d5abf8b0d3
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ja_wikipedia_org/2026-07-23T13-01-25-750Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ja_wikipedia_org/2026-07-23T13-01-25-750Z
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.