Manifest position 682 · CrUX rank bucket 1000
https://kakuyomu.jp
Coverage complete
Coverage complete across 58 catalog checks and six representative public 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 | Dark-emulated screenshots of both the home and reading surfaces remain white, and computed color-scheme is normal. 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 probe found zero active animations and no auto-advancing animation requiring suppression. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast screenshot is effectively unchanged, while Lighthouse reports color-contrast failures. F02 medium: High-contrast preferences are not comprehensively supported. |
implement-natural-interactionsview-transitions | issues | high | The CSS/runtime probe found no view-transition rules, while the representative journey spans listing, work, and episode pages. F03 low: Route and state changes do not expose declarative view transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked visual effect was observed, so there is no scroll-handler implementation to judge. |
implement-natural-interactionsphysical-gestures | pass | high | The observed carousel exposes conventional previous/next controls and the reading surface uses native scrolling rather than custom pointer handlers. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The episode is over 10,000 CSS px high, but CSS inspection found no scroll timeline or scroll-state rules and the reader screenshot has no progress indicator. F04 low: Long reading and listing pages provide no scroll-state-aware progress cue. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or transient anchored overlay was present in the representative anonymous paths. |
provide-guided-navigationdirects-attention | pass | high | Explore and work screenshots show clear active tabs, section headings, and a marked current episode that preserve orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | All first-load screenshots show content immediately with no interstitial, consent wall, or viewport-obscuring popup. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No modal or disclosure overlay appeared before interaction on the representative paths. |
maximize-content-reduce-noisereduced-chrome | pass | high | The reading surface gives the majority of the desktop viewport to prose with restrained persistent reader controls. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360 px, layout captures report 825 px overflow on home and explore, 640 px on work, and 380 px on the episode. Screenshots show clipped headings, navigation, controls, and content. F05 critical: Core public templates render desktop-width layouts on mobile. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no container queries and multiple templates retain wide desktop component geometry at 360 px. F06 medium: Components do not adapt at their reuse boundary. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse fails target-size and link-name audits; the carousel button probe shows two icon-only buttons without aria-label. F07 high: Some controls have inaccessible names or undersized touch targets. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The home hero states write/read/share and exposes registration; work pages expose a prominent “read from episode 1” action. |
support-core-task-successprimary-flow-completion | pass | high | The anonymous journey from home to work detail to episode completed without an account wall and the episode prose rendered. |
support-core-task-successclear-system-state-and-recovery | pass | high | The deliberate 404 displays a specific error explanation, search/discovery content, and links back to useful destinations. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse reports LCP 3.1 s, TBT 740 ms, interactive at 24.9 s, and a performance score of 0.72. F08 high: Mobile load responsiveness misses the performance baseline. |
be-fast-and-stablevisual-stability | pass | high | All five mobile layout captures report CLS 0; no observed layout shifts occurred during the capture window. |
be-fast-and-stableefficient-main-thread | issues | high | The trace records two long tasks up to 140 ms and 177 ms TBT; Lighthouse under throttling reports 740 ms TBT. F09 high: Long JavaScript tasks block the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR records 139 requests, seven parser-inserted high-priority stylesheets, and major images without cache headers. F10 medium: The critical delivery path is fragmented and cache hygiene is weak. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 519 KiB unused JavaScript; HAR attributes 1.30 MB and 85 requests to third parties. F11 high: The page ships substantial unused JavaScript and third-party code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse fails image-alt, frame-title, link-name, and label-content-name-mismatch; its accessibility score is 0.72. F12 high: Several images, frames, and links lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse’s axe-backed color-contrast audit fails on the home page. F13 high: Text does not consistently meet WCAG contrast minimums. |
be-inclusivestructure-and-focus | issues | high | Lighthouse fails landmark-one-main and link-name; DOM probing found zero main and zero nav elements, and only a 1 px dotted focus outline on the first link. F14 high: The home page lacks a main landmark and has weak control semantics. |
be-inclusivelegible-text | issues | high | Mobile screenshots clip long headings, tabs, metadata, and reader content because templates are 740 to 1,185 px wide. F15 high: Mobile clipping makes text difficult or impossible to read. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Every inspected public page declares maximum-scale=1.0 and user-scalable=no; Lighthouse fails meta-viewport and target-size. F16 critical: The viewport explicitly disables user zoom. |
follow-best-practicesno-console-errors | issues | high | Lighthouse records a CORS failure, net::ERR_FAILED, and React hydration error #418 in the console. F17 medium: Production load emits browser and React errors. |
follow-best-practicessound-document-and-assets | issues | high | The work-page image audit finds 27 of 31 images without width/height and 11 oversized images. F18 medium: Image markup does not reserve dimensions consistently. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports one deprecated API, three BFCache failure reasons, missing source maps for large first-party JavaScript, and inspector issues. F19 medium: The page has deprecations, BFCache blockers, and missing source maps. |
be-discoverabletitle-and-description | pass | high | Home and work probes show descriptive unique titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | All 305 home anchors have hrefs, robots allows public content, and a viewport meta is present; mobile layout quality is recorded separately. |
be-discoverablecanonical-and-indexing-signals | issues | high | The home metadata probe finds no canonical URL and /sitemap.xml returns 404, although robots permits crawling. F20 medium: Indexing signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | The work page has Open Graph metadata but no JSON-LD, and the home probe also finds no structured-data scripts. F21 medium: Content pages provide social metadata but no structured entity data. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP and HSTS are absent; 9 of 9 observed cookies are flagged insecure and several use SameSite=None. F22 high: Transport policy and cookie attributes are unsafe by default. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe sees 35 third-party origins and 14 known trackers; HAR records 85 third-party requests and 1.30 MB transferred. F23 high: The anonymous home page has a large tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load, and the login entry prominently offers passkey authentication. |
be-private-and-securedefensive-browser-policies | issues | high | Headers lack CSP, HSTS, Referrer-Policy, and Permissions-Policy, while clickjacking and nosniff protections are present. F24 high: Several browser-enforced defenses are missing. |
be-resilientprogressive-enhancement | pass | high | Crawler screenshots render the home and episode content without JavaScript; the episode title and prose remain visible. |
be-resilientresilient-runtime-behaviour | issues | high | Menus and content extend hundreds of pixels beyond the mobile viewport on four public templates. F25 high: Runtime layout is not robust at narrow viewport edges. |
be-resilientoffline-and-installable | not-applicable | high | This public publishing/content site supplies a browser manifest but is not presented as an installable offline application; offline installation is contextual. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberate invalid route renders an explanatory, actionable 404 with discovery and top-page recovery links. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The audited service and corpus are deliberately Japanese-language and left-to-right; multi-language layout was not part of the observed product scope. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited public paths are deliberately Japanese-locale and expose no locale-switching or user-entered locale-sensitive data. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative reading paths show publication dates rather than cross-zone scheduling or recurring-event functionality. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, confirmshaming, disguised action, forced continuity, or surprise commitment appeared in the anonymous paths. |
be-trustworthyhumane-error-handling | not-applicable | high | The inspected login entry uses identity-provider and passkey actions with no editable form or validation state to exercise. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No editable input appears until a user selects a separate email-auth path, which was outside the anonymous entry-flow coverage. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, cancellation, or authenticated account-management flow was available in anonymous scope. |
be-sustainableoptimised-assets | issues | high | The image audit flags 11 oversized work-page images; HAR’s largest image is 483 KB and major images lack cache headers. F26 medium: Several assets are oversized or lack efficient delivery metadata. |
be-sustainableno-wasteful-work | issues | high | HAR logs 34 fetch/XHR requests, many ad-auction and conversion calls, and 85 third-party requests on an anonymous landing page. F27 high: Background advertising and analytics create disproportionate work. |
be-sustainablethird-party-and-media-budget | issues | high | Of 3.24 MB transferred, 1.30 MB is third-party; Google Tag Manager and Facebook alone transfer about 924 KB. F28 high: Third-party scripts dominate the page budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing capabilities are emerging and no explicit agent transaction intent was declared for this public reading site. |
be-agent-readyon-device-inference | not-applicable | high | On-device inference is an optional emerging enhancement and is not required for the core read/discover journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 next/previous carousel cycles, heap self size was 50.2 MB versus 48.4 MB baseline, a bounded 3.8% difference across fresh captures with no runaway signal. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary contains 869,025 nodes and 48.4 MB self size before extended interaction. F29 medium: The initial memory footprint is heavy for a content landing page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap summaries contain no Detached constructor among top populations, and repeated carousel cycling did not show unbounded retained growth. |
Provenance
Canonical report: results/atomic/reports/0682-kakuyomu_jp.json
Report SHA-256: f39a254019210da0d752f7d573ac94fc9bd4b690a6a48441ac1c9354fc723d98
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/kakuyomu_jp/2026-07-22T09-30-35-490Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/kakuyomu_jp/2026-07-22T09-30-35-490Z
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.