Manifest position 40 · CrUX rank bucket 1000
https://newsdig.tbs.co.jp
Coverage complete
Coverage complete across 58 registered checks and six representative paths. No local project config applied; repository playground config is unrelated to this remote site.
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 byte-identical to the light capture and the CSS preference probe found no prefers-color-scheme rule. F-01 medium: Dark preference is ignored |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation reported zero active animations; no auto-advance motion was observed. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse failed color-contrast and the focused-control probe found no visible outlines on sampled controls. F-02 medium: Contrast is insufficient in key UI |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no View Transition declarations while primary navigation is cross-document. F-03 low: Route changes are abrupt |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked decorative motion was observed and the CSS probe found no scroll timeline requiring a main-thread substitute. |
implement-natural-interactionsphysical-gestures | pass | high | The tested pages rely on native scrolling and ordinary links; no custom pointer-driven gesture layer was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long homepage has static navigation and the preference/CSS probe found no scroll-state or scroll-timeline rules. F-04 low: Page chrome does not communicate scroll state |
provide-guided-navigationanchored-positioning | pass | high | No tooltip or anchored-menu interaction was present on the representative reading paths; the consent dialog is centered rather than attached to an anchor. |
provide-guided-navigationdirects-attention | pass | high | Clear section headings, selected navigation styling, breadcrumbs on articles, and descriptive links guide reading. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile load screenshots show a modal consent wall covering the news; on mobile its content is clipped horizontally. F-05 critical: Consent wall obscures all content on first load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The area probe reports consent controls plus multiple injected h1 elements and dialogs in the page structure. F-06 medium: Consent UI creates duplicate document structure |
maximize-content-reduce-noisereduced-chrome | issues | high | The first viewport is dominated by two navigation rows and the consent layer; the homepage exposes 100 images and many competing sections. F-07 medium: Dense chrome competes with news content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At viewport 360x800, layout measured scrollWidth 1241 and 881 px horizontal overflow; the consent dialog is visibly clipped. F-08 critical: Mobile layout renders at desktop width |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The 360px evidence retains a 1241px layout and the CSS probe found no container-query rules. F-09 medium: Components do not adapt to their available width |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found outline none on sampled links/buttons and a visible search button measured only 16x16 px. F-10 high: Focus and target affordances are weak |
support-core-task-successclear-purpose-and-primary-action | pass | high | The TBS NEWS DIG identity, トップニュース heading, lead headline and category navigation clearly communicate the news-reading purpose. |
support-core-task-successprimary-flow-completion | issues | high | Every fresh-path screenshot opens behind the consent wall, requiring a detour before reading an article or forecast. F-11 high: Consent interrupts the primary reading journey |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberately invalid URL produced a localized not-found explanation and routes back to the news home/categories. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 6.2s, FCP 4.1s, TBT 450ms and performance 0.50; trace LCP was 3.03s. F-12 high: Loading performance misses the modern baseline |
be-fast-and-stablevisual-stability | pass | high | Layout observation measured CLS 0.0056 and Lighthouse measured 0.021, both within the good range. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse recorded 3.4s main-thread work, 1.5s JS execution, 450ms TBT and 29s time to interactive. F-13 high: Main-thread work delays interactivity |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 218 requests and 3.28MB, including 49 font requests; Lighthouse found render-blocking requests with 880ms savings and weak cache lifetimes. F-14 high: Resource delivery is excessively complex |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 644KiB unused JavaScript and 84KiB unused CSS; HAR recorded 46 script requests. F-15 high: Large unused bundles ship on first load |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed link-name; the image primitive found 54 images without alt and the homepage H1 is empty. F-16 high: Some links and images lack accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed its color-contrast audit. F-17 medium: Text contrast fails automated testing |
be-inclusivestructure-and-focus | issues | high | The homepage has an empty H1, consent injection adds multiple H1s, and sampled focused controls retained outline none. F-18 high: Heading and keyboard-focus structure is unreliable |
be-inclusivelegible-text | issues | high | The 360px screenshot cuts off consent copy and controls because the document remains 1241px wide. F-19 high: Mobile text is clipped outside the viewport |
be-inclusivezoom-reflow-targets-and-media | issues | high | Layout has 881px overflow at 360px and a search control measured 16x16px. F-20 high: Reflow and target sizing fail on mobile |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console. F-21 medium: Browser errors are logged |
follow-best-practicessound-document-and-assets | issues | high | Doctype/UTF-8 are valid, but the main H1 is empty and image inspection found 54 missing alt attributes and 29 images without srcset. F-22 medium: Document semantics and image assets need cleanup |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported a deprecated API, Inspector issues and five BFCache failure reasons. F-23 medium: Deprecated APIs and browser lifecycle blockers remain |
be-discoverabletitle-and-description | pass | high | Home and article probes found unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links, viewport metadata, robots.txt and a sitemap index were present; Lighthouse SEO scored 1.00. |
be-discoverablecanonical-and-indexing-signals | pass | high | HTTP 200, canonical URLs, permissive general indexing rules and a current sitemap index were observed. |
be-discoverablestructured-and-shareable-metadata | pass | high | The article exposes matching NewsArticle/Breadcrumb JSON-LD plus complete Open Graph metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS/nosniff are present, but CSP is missing and all 15 observed cookies were flagged insecure; many use SameSite=None. F-24 high: Cookie and CSP posture is weak |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 67 third-party origins and 15 known tracker domains; HAR recorded 218 requests before a consent choice. F-25 high: Tracking footprint is disproportionate |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Notification permission remained default with no prompt on load, and no authentication flow exists on the sampled public news paths. |
be-private-and-securedefensive-browser-policies | issues | high | Headers include HSTS, nosniff and SAMEORIGIN, but lack CSP, Referrer-Policy and Permissions-Policy. F-26 medium: Defensive response policies are incomplete |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 20% raw-content coverage on home and 18% on the article; the raw article lacked its title and H1. F-27 high: Most core article content is absent without JavaScript |
be-resilientresilient-runtime-behaviour | issues | high | The mobile screenshot clips the modal and layout reports 881px overflow. F-28 high: Top-layer consent UI breaks at narrow widths |
be-resilientoffline-and-installable | issues | high | A service worker and manifest exist, but manifest display is browser and no offline fallback was exposed by the inspected configuration. F-29 low: Manifest and service worker do not provide an installable app presentation |
be-resilientnetwork-and-http-failure-states | pass | high | The invalid route shows a clear Japanese not-found message and useful home/category recovery links. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang="ja" and the sampled Japanese layout follows the expected left-to-right reading order. |
be-internationalisedlocale-aware-data | pass | high | Rendered publication dates use Japanese year/month/day conventions and article metadata uses an unambiguous ISO offset. |
be-internationalisedtime-zone-correctness | pass | high | NewsArticle datePublished/dateModified include +09:00 offsets, avoiding ambiguous publication times. |
be-trustworthyno-dark-patterns | issues | high | The blocking consent wall foregrounds Consent and delays access to public-interest news; mobile content is unreadable behind it. F-30 high: Consent design pressures acceptance before reading |
be-trustworthyhumane-error-handling | not-applicable | high | No required data-entry or submission form exists in the sampled public news, article, weather, listing, or area-selection journey. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The sampled site has only optional search inputs, not address, payment, sign-in or sign-up fields requiring autofill assistance. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication or account-management flow is offered on the representative public paths. |
be-sustainableoptimised-assets | issues | high | Image evidence found 29 images without srcset and 79 below-fold images not marked lazy; Lighthouse estimated image savings. F-31 medium: Asset delivery is not consistently optimized |
be-sustainableno-wasteful-work | issues | high | HAR recorded 218 requests, 46 scripts and 67 XHR/fetch requests; Lighthouse measured 3.4s main-thread work. F-32 high: Substantial background/vendor work runs on entry |
be-sustainablethird-party-and-media-budget | issues | high | The page contacted 67 third-party origins and downloaded 49 font resources within a 3.28MB transfer. F-33 high: Third-party and font budgets are excessive |
be-agent-readystructured-agent-capabilities | issues | high | Article raw-HTML coverage is 18%, while robots explicitly disallows ChatGPT-User, GPTBot, CCBot, Google-Extended and PerplexityBot. F-34 low: News content is difficult for permitted agents to consume |
be-agent-readyon-device-inference | issues | high | Capabilities probe found no built-in AI surface on a long-form news product where optional local summarization could add value. F-35 low: No privacy-preserving on-device summary affordance is exposed |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten top-to-bottom scroll cycles, heap self size rose about 1.4% (45.86MB to 46.51MB), not evidence of unbounded retained growth in this short run. |
be-memory-efficientbounded-footprint | issues | high | Baseline heap summary reported 794,000 nodes and 45.9MB self size before extended interaction. F-36 medium: Initial memory footprint is high for a news landing page |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap summaries did not surface Detached* constructors among top retained constructors; the short repeated-scroll run showed bounded growth. |
Provenance
Canonical report: results/atomic/reports/0040-newsdig_tbs_co_jp.json
Report SHA-256: b0f00b73417c9e60d50a9ec334b03020533c2ad1ba71b85cadc2cae7d732f527
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/newsdig_tbs_co_jp/2026-07-18T00-21-50-574Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/newsdig_tbs_co_jp/2026-07-18T00-21-50-574Z
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.