Manifest position 194 · CrUX rank bucket 1000
https://topics.smt.docomo.ne.jp
Coverage complete
Atomic coverage complete across 58 checks and five representative paths.
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-emulated screenshot is pixel-identical in appearance and file size to the light capture; white surfaces and dark text remain unchanged. F01 medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, the active-animation probe reported zero animations; no auto-advance or essential motion appeared on representative pages. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse measured date/time text at 2.95:1 (#969696 on white), while the prefers-contrast: more capture retained the same palette. F02 medium: Low-contrast metadata does not adapt for contrast preferences. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS probe found no `view-transition` CSS on this multi-page news site; representative category, ranking, and article navigations perform full abrupt swaps. F03 low: Cross-document navigation swaps abruptly. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, reveal, or other scroll-linked animation exists on the audited templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited news templates expose ordinary links and scrolling, with no custom swipe, pull, draggable, or carousel gesture surface. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Screenshots show long multi-section pages, while CSS inspection found no scroll-state container-query or progress treatment; page chrome does not communicate reading position. F04 low: The long news pages provide no scroll-state-aware navigation or progress cue. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, menu, or popover overlay was present in the audited states. |
provide-guided-navigationdirects-attention | pass | high | Selected category tabs use a strong blue state, breadcrumbs identify location on inner pages, and content headings clearly cue the destination after navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load-state screenshots across home, category, ranking, and article show content immediately with no consent wall, interstitial, or obscuring popup. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No transient overlay, modal flow, or custom disclosure was present in the audited states. |
maximize-content-reduce-noisereduced-chrome | pass | high | Screenshots show compact global navigation and predominantly news lists/article copy; chrome does not obscure the content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360×800 viewport, layout metrics reported `innerWidth: 769`, visual scale 0.46875, and the screenshot shows desktop columns and tiny text compressed into the screen. The viewport meta is only `width=device-width`. F05 high: Mobile viewports receive a scaled-down 768px tablet layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The probe found no `@container`; the same cards stay in tablet-scale columns on 360px instead of reflowing for the narrow container. F06 medium: Repeated news components do not respond to their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe repeatedly returned outline style `none`; Lighthouse also found 16px-tall publisher links with less than the 24px WCAG 2.2 target-size floor. The scaled tablet viewport further shrinks effective controls. F07 high: Keyboard focus is suppressed and some touch targets are undersized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The H1, selected news tab, category labels, ranking heading, and article headline make each page purpose and next link clear. |
support-core-task-successprimary-flow-completion | pass | high | The representative flow from listing/category to a direct article URL completed and exposed the full article plus publisher/context links without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | A nonexistent route displays a specific Japanese not-found explanation, preserved global navigation, and a prominent “ニューストップへ” recovery link. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 7.4s, LCP 11.6s, Speed Index 13.5s, TBT 360ms, and a performance score of 47. The separate trace still measured LCP 3.35s, above the 2.5s good threshold. F08 high: Cold mobile loading is far outside the good LCP range. |
be-fast-and-stablevisual-stability | pass | high | Layout observation measured CLS 0.00017 on home and 0 on ranking; Lighthouse measured CLS 0.009, all within the ≤0.1 good range. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported 5.3s main-thread work, 3.1s JavaScript execution, TTI 28s, and TBT 360ms; the trace recorded a 79ms long task. F09 high: Third-party and legacy JavaScript consume substantial main-thread time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR plus DOM confirmation found six classic scripts in `<head>` with neither async nor defer, including 282KB `swiper.js`; Lighthouse estimated 4.64s render-blocking savings and flagged cache, font-display, HTTP, and dependency-tree issues. F10 high: Parser-blocking scripts and weak delivery delay content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,392KiB unused JavaScript, 157KiB unused CSS, 130KiB legacy JavaScript, and 82KiB unminified JavaScript; HAR attributes 1.30MB to scripts. F11 medium: The page ships large amounts of unused and legacy code. |
be-inclusivenames-roles-labels | issues | high | axe reported a critical `label` violation for `input#search`; Lighthouse independently found unlabeled search input `#queryft`. F12 high: A search field lacks an accessible label. |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured repeated 12px timestamp text at 2.95:1 against white, below the required 4.5:1. F13 medium: News timestamps fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | axe found skipped heading levels and non-unique landmarks; the probe ends an H1/H2/H3 sequence with H4 and found no visible computed outline on focused controls. F14 medium: Heading/landmark structure and focus presentation are inconsistent. |
be-inclusivelegible-text | issues | high | All representative 360px screenshots show the 768px tablet design scaled to roughly 47%, producing very small article metadata, navigation, and list copy. F15 high: Text is not legible at a narrow mobile viewport. |
be-inclusivezoom-reflow-targets-and-media | issues | high | See linked finding. F16 high: The experience fails narrow reflow and includes undersized targets. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured repeated CORS failures to `hb.adingo.jp` plus unresolved/failed resources; the HAR also recorded ORB-blocked scripts. F17 medium: Advertising requests produce repeated console/network errors. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found all 15 images missing at least one dimension and all 15 served as PNG/JPEG; eight below-fold images were not lazy-loaded. F18 medium: Image markup omits intrinsic dimensions and uses only legacy formats. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found three deprecations, including the main-frame unload listener, and confirmed that handler blocks BFCache restoration; source-map and Inspector Issues audits also failed. F19 medium: Deprecated APIs and an unload handler reduce platform compatibility. |
be-discoverabletitle-and-description | pass | high | Home and article probes found unique descriptive titles and populated descriptions that match the visible Japanese content. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Recon found many article links using `/redirector?...`; robots.txt disallows `/redirector` for all crawlers. Some header actions also expose empty href values. F20 high: Primary story links route through URLs explicitly blocked from crawling. |
be-discoverablecanonical-and-indexing-signals | issues | high | The home probe found no `rel=canonical`, although the page redirects to `?redirect=1`; the article template does provide a correct canonical and sitemaps are present. F21 low: The homepage lacks a canonical URL. |
be-discoverablestructured-and-shareable-metadata | issues | high | The article has accurate title, description, canonical, and Open Graph values, but the probe found zero JSON-LD blocks and no semantic `<time datetime>` values. F22 medium: Article pages omit NewsArticle structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no CSP, HSTS, nosniff, frame protection, Referrer-Policy, or Permissions-Policy. Cookie audit found five insecure cookies, including three 400-day analytics cookies. F23 high: Security headers are absent and several cookies are not Secure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 13 third-party origins and Google Analytics, GTM, Facebook, and Google ads; Lighthouse observed 18 third-party cookies. HAR attributes 52/55 requests and 1.61MB/1.63MB transferred bytes to third parties. F24 high: The page starts a broad tracking/advertising footprint before any visible choice. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No permission prompt fired on load, and no authentication surface exists in the representative public news-reading paths. |
be-private-and-securedefensive-browser-policies | issues | high | Header inspection found no clickjacking protection, Referrer-Policy, Permissions-Policy, CSP/Trusted Types foundation, or HSTS. F25 medium: Browser-enforced defensive policies are not configured. |
be-resilientprogressive-enhancement | pass | high | Discoverability fetched HTTP 200 raw HTML with title, H1, description, and 100% measured home content coverage without JavaScript; article raw HTML was substantial and crawler screenshot retained content. |
be-resilientresilient-runtime-behaviour | pass | high | Representative navigation/list/article templates loaded without clipped overlay state; links remain ordinary server navigations and no fragile overlay/async control was found. |
be-resilientoffline-and-installable | not-applicable | high | No manifest or service worker exists, but this continuously updated public news portal is primarily a content MPA rather than an install-oriented application. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested missing route provides an explanatory state and direct recovery link instead of a blank shell or infinite spinner. |
be-internationalisedlang-dir-and-logical-properties | pass | high | All templates declare valid `lang="ja"`; Japanese reading order is correct for the deliberately Japanese service. |
be-internationalisedlocale-aware-data | issues | high | Article metadata is rendered as `7/19(日) 11:04`; the article probe found no `<time datetime>` values, preventing unambiguous machine/locale interpretation. F26 medium: Publication dates are presented as unstructured locale-specific strings. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled cross-zone event, user-entered time, recurrence, or DST-sensitive flow exists in the representative news-reading paths. |
be-trustworthyno-dark-patterns | pass | high | Load and article/listing screenshots show no confirmshaming, forced continuity, consent nag, disguised control, or hidden pricing/account commitment. |
be-trustworthyhumane-error-handling | not-applicable | high | The audited core flow has no user-data form; the only form is a basic search and no submitted invalid-data workflow was required. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The only text input is generic site search; address, payment, authentication, and profile autofill are not relevant. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent choice, sign-in, or account-management flow is part of this public news-reading surface. |
be-sustainableoptimised-assets | issues | high | All 15 audited images are JPEG/PNG, eight below-fold images are eager, and every image lacks at least one intrinsic dimension; Lighthouse estimated 156KiB image-delivery savings. F27 medium: Image delivery misses basic efficiency controls. |
be-sustainableno-wasteful-work | issues | high | HAR shows 1.30MB of scripts and failed ORB/analytics requests; Lighthouse reports 1,392KiB unused JS and 3.1s execution time. F28 medium: Large optional scripts and failed ad requests perform wasteful work. |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 1.61MB of 1.63MB transferred from third-party origins in this capture; Lighthouse’s broader run reached 3,491KiB and identified extensive tracking/cookie activity. F29 high: Third-party code dominates the page budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | robots.txt explicitly blocks major AI agents and the site exposes no WebMCP tools, indicating no intended agent-facing capability. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, translation, generative, or other inference feature is offered in the audited news-reading experience. |
be-memory-efficientno-leak-under-repeated-interaction | not-applicable | high | The audited templates are server-navigated content pages with no modal, SPA route cycle, editor, or infinite feed interaction suitable for a meaningful ten-cycle leak test. |
be-memory-efficientbounded-footprint | pass | high | The steady home snapshot reported 313,587 heap nodes and 16.85MB self size; Performance memory reported about 14.0MB used heap, proportionate to this content page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The single-state heap constructor summary showed no Detached* constructor among dominant populations; no repeated long-lived interaction exists on these MPA templates. |
Provenance
Canonical report: results/atomic/reports/0194-topics_smt_docomo_ne_jp.json
Report SHA-256: cbf1f9ed535326b20d56641f1efd03c28370288fe73dee11fe0eb1f749a6a447
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/topics_smt_docomo_ne_jp/2026-07-19T02-06-26-214Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/topics_smt_docomo_ne_jp/2026-07-19T02-06-26-214Z
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.