Manifest position 839 · CrUX rank bucket 1000

https://nlab.itmedia.co.jp

Coverage complete

Coverage complete: all 58 catalog checks received one conclusive outcome. Scope covers five representative page archetypes/conditions; search, login/member-only, subscription and destructive account flows were not exercised because they were not part of the anonymous primary reading journey.

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	The prefers-color-scheme: dark screenshot is pixel-identical to the light capture, the live CSS probe found no prefers-color-scheme or forced-colors/prefers-contrast rules, and Lighthouse also found default-state contrast failures. F01 medium: The site does not adapt its palette to dark or increased-contrast preferences.
respect-user-preferences `respects-reduced-motion`	pass	high	Reduced-motion emulation reported zero active animations, so no nonessential motion persisted.
respect-user-preferences `respects-contrast`	issues	high	The live stylesheet probe found no prefers-contrast or forced-colors handling, while Lighthouse found baseline color-contrast failures, increasing the risk that metadata and controls remain hard to perceive. F27 medium: The site does not explicitly preserve UI visibility under increased-contrast preferences.
implement-natural-interactions `view-transitions`	issues	high	The stylesheet probe found no view-transition rules on this multi-page news site; route changes therefore use abrupt document swaps. F02 low: Page and state changes have no View Transition treatment.
implement-natural-interactions `scroll-driven-animations`	pass	high	CSS inspection found scroll-snap but no script-driven scroll-animation evidence or active animations; the sampled pages do not use scrollytelling effects.
implement-natural-interactions `physical-gestures`	pass	high	CSS inspection found native scroll-snap and no evidence of custom pointer-driven gesture handling on the sampled reading paths.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	The DOM/CSS probe found fixed/sticky chrome but no scroll-state container queries or scroll-timeline behavior. F03 low: Persistent page chrome does not expose scroll-state-aware behavior.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No site-owned tooltip, popover or anchored menu was present on the representative paths.
provide-guided-navigation `directs-attention`	pass	high	Visible category navigation, descriptive article links, canonical article headings and breadcrumb structured data provide clear navigation context.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	Desktop and mobile screenshots show a full-page consent wall plus a push-notification prompt layered over it before interaction; on mobile the notification panel covers the consent title and content. F04 critical: Two simultaneous unsolicited overlays obscure the primary content on every sampled path.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	The rendered DOM exposes consent headings but the semantic probe found 0 dialog, 0 popover and 0 details elements while six fixed/sticky elements were present. F05 high: Overlay experiences are not represented by native dialog/popover semantics.
maximize-content-reduce-noise `reduced-chrome`	issues	high	Across homepage, category, article and 404 screenshots, the actual content is dimmed and mostly hidden behind consent and notification UI. F06 high: Advertising and prompt chrome dominates the first viewport.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	Home, category and article layout probes at 360px all reported 0px horizontal overflow and a viewport meta tag.
adapt-to-the-form-factor `component-level-responsiveness`	pass	high	The same listing/article surfaces reflowed to 360px without overflow, demonstrating working component adaptation across sampled widths.
adapt-to-the-form-factor `input-modality-aware`	issues	high	A focused primary anchor computed to outline-style none with no box shadow; Lighthouse failed target-size. F07 high: Keyboard focus and touch-target affordances are insufficient.
support-core-task-success `clear-purpose-and-primary-action`	issues	high	All first-load screenshots foreground consent and push prompts rather than the page purpose, headline or next reading action. F08 critical: The primary reading journey is blocked before users can understand or use the page.
support-core-task-success `primary-flow-completion`	issues	high	All first-load screenshots foreground consent and push prompts rather than the page purpose, headline or next reading action. F08 critical: The primary reading journey is blocked before users can understand or use the page.
support-core-task-success `clear-system-state-and-recovery`	issues	high	The 404 page contains recovery content, but the screenshot shows it dimmed beneath the same two overlays, preventing immediate recovery. F09 high: System and error states are obscured by unrelated prompts.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured LCP 14.1 s, CLS 0.172 and performance 0.55; the first-party trace measured LCP 4.04 s. F10 high: Load performance misses the Core Web Vitals bar.
be-fast-and-stable `visual-stability`	issues	high	Mobile layout captures measured CLS 0.203 on the category page and 0.117 on the article; Lighthouse measured 0.172 on home. F11 high: Category and article templates shift visibly after load.
be-fast-and-stable `efficient-main-thread`	pass	high	The first-party trace recorded one 79.9ms long task and 29.9ms total blocking time; mobile layout probes saw one bounded long task per path.
be-fast-and-stable `efficient-resource-delivery`	issues	high	The HAR recorded 94 requests and 2.11 MB, including 1.95 MB third-party bytes; Lighthouse estimated 950 ms render-blocking savings and 610 KiB cache savings. F12 high: Critical resource delivery is dominated by third-party and render-blocking work.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 429 KiB unused JavaScript and 35 KiB unused CSS; 32 scripts transferred 1.58 MB in the HAR. F13 medium: Substantial unused JavaScript and CSS are shipped on first load.
be-inclusive `names-roles-labels`	issues	high	The image probe found 97 of 100 images without alt; Lighthouse failed image-alt, button-name and link-name. F14 high: Images and controls lack accessible names.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse color-contrast audit failed on the rendered homepage. F15 high: Text and essential UI fail minimum color contrast.
be-inclusive `structure-and-focus`	issues	high	Lighthouse failed heading-order; the DOM probe found no main landmark and a heading sequence beginning H3, H2 with multiple consent H1s injected alongside page headings. F16 high: Heading and landmark structure is not coherent.
be-inclusive `legible-text`	pass	high	Underlying Japanese headline and body text uses readable sizing and wrapping; all narrow layouts reflowed without clipping or horizontal overflow.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	Lighthouse failed meta-viewport because maximum-scale is 1 and failed target-size, although 360px layouts did avoid horizontal overflow. F17 high: Viewport scaling policy and small targets impair zoom/reflow use.
follow-best-practices `no-console-errors`	pass	high	Lighthouse did not report the console-errors audit among failed audits during the sampled load.
follow-best-practices `sound-document-and-assets`	pass	high	The server HTML has an HTML5 doctype/UTF-8 metadata, and the image probe found all 100 images had explicit dimensions, limiting aspect-ratio instability.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse failed notification-on-start and inspector-issues. F18 medium: The page triggers notification permission on startup and logs browser inspector issues.
be-discoverable `title-and-description`	pass	high	Homepage and article probes found descriptive, route-specific titles and meta descriptions.
be-discoverable `crawlable-and-mobile-friendly`	pass	high	All sampled anchors had hrefs, viewport metadata was present and robots.txt allows crawling while naming the sitemap.
be-discoverable `canonical-and-indexing-signals`	pass	high	Pages returned 200, expose canonical URLs, robots allows crawling and the declared sitemap index was fetched successfully during recon.
be-discoverable `structured-and-shareable-metadata`	pass	high	The article exposes NewsArticle and BreadcrumbList JSON-LD plus matching Open Graph title, description, URL and image.
be-private-and-secure `secure-transport-and-headers`	issues	high	HTTPS and nosniff are present, but headers evidence found no CSP or HSTS; cookie evidence found 10 cookies flagged insecure, including several without Secure and many SameSite=None. F19 high: Transport and cookie defenses are incomplete.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	Tracker evidence found 27 third-party origins and seven known trackers; HAR attributed 75 of 94 requests and 1.95 of 2.11 MB to third parties before consent. F20 high: Third-party tracking is disproportionate to the first-load reading task.
be-private-and-secure `in-context-permissions-and-modern-auth`	issues	high	The initial screenshot shows a notification-acquisition overlay before user intent, and Lighthouse failed notification-on-start. F21 high: Notification permission is requested out of context on load.
be-private-and-secure `defensive-browser-policies`	issues	high	Headers evidence found no HSTS, Referrer-Policy, Permissions-Policy or CSP; X-Frame-Options SAMEORIGIN was present. F22 high: Several browser-enforced defensive policies are absent.
be-resilient `progressive-enhancement`	pass	high	Discoverability captures found non-shell server HTML (232-244KB) with substantial text and metadata on home and article, so core content is server delivered rather than an empty JS mount.
be-resilient `resilient-runtime-behaviour`	issues	high	At 360x800 the notification panel overlaps and clips the consent experience, hiding its title and upper controls. F23 medium: Overlay composition is not resilient at narrow viewports.
be-resilient `offline-and-installable`	not-applicable	high	This public news publication is document-oriented rather than an installable application; offline installation is not a core stated journey.
be-resilient `network-and-http-failure-states`	pass	high	The unknown URL rendered a dedicated Japanese 404 explanation and recovery link content rather than a blank shell.
be-internationalised `lang-dir-and-logical-properties`	pass	high	All sampled documents declare lang=ja, matching the Japanese content and reading direction.
be-internationalised `locale-aware-data`	pass	high	Article structured data exposes machine-readable ISO publication/modification values while visible content is localized for the Japanese audience.
be-internationalised `time-zone-correctness`	pass	high	NewsArticle metadata uses explicit +0900 offsets, avoiding ambiguous stored publication times.
be-trustworthy `no-dark-patterns`	issues	high	Initial screenshots show primary Consent and Manage options buttons but no visible Reject all action, while a second unsolicited notification panel competes above it. F24 high: Consent presents acceptance prominently without an equally direct reject choice and is paired with notification nagging.
be-trustworthy `humane-error-handling`	not-applicable	high	No user-authored form was present in the sampled public reading journeys.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	No address, payment, sign-in or sign-up fields were present in the sampled public reading journeys.
be-trustworthy `safe-commercial-and-account-flows`	issues	high	Initial screenshots show primary Consent and Manage options buttons but no visible Reject all action, while a second unsolicited notification panel competes above it. F24 high: Consent presents acceptance prominently without an equally direct reject choice and is paired with notification nagging.
be-sustainable `optimised-assets`	issues	high	The image probe found 37 legacy-format images, no detected modern-format images and one oversized image; the sampled elements generally lacked srcset. F25 medium: Editorial image delivery is not consistently modern or responsive.
be-sustainable `no-wasteful-work`	issues	high	HAR measured 1.95 MB third-party transfer out of 2.11 MB total; ad code alone included a 642 KiB script and trackers reported 27 third-party origins. F26 high: Third-party scripts consume most transferred bytes for a text/news landing page.
be-sustainable `third-party-and-media-budget`	issues	high	HAR measured 1.95 MB third-party transfer out of 2.11 MB total; ad code alone included a 642 KiB script and trackers reported 27 third-party origins. F26 high: Third-party scripts consume most transferred bytes for a text/news landing page.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	No declared agent-facing transactional capability exists; emerging WebMCP exposure is not required for this public news reading surface.
be-agent-ready `on-device-inference`	not-applicable	high	No on-device inference use case is required to complete the core news-reading journey.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After ten full-page scroll down/up cycles, heap node count fell by 56 and retained self-size changed only +47,884 bytes (+0.12%), with object/closure populations flat.
be-memory-efficient `bounded-footprint`	pass	high	The sampled content-heavy home page retained 38.7MB in the heap summary; the footprint remained bounded after repeated scrolling.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Before/after summaries showed closures decreased 26 and objects decreased 39 after repeated scrolling, with no growth signal in top constructor populations.

Provenance

Canonical report: results/atomic/reports/0839-nlab_itmedia_co_jp.json
Report SHA-256: b09f1e9658a2df6ce37376f8ffc3f15bde3196b6c03588e4ecdc30143d9d8eee
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/nlab_itmedia_co_jp/2026-07-23T08-36-11-395Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/nlab_itmedia_co_jp/2026-07-23T08-36-11-395Z
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.