Manifest position 85 · CrUX rank bucket 1000
https://ncode.syosetu.com
Coverage complete
Complete atomic audit of 58/58 checks across four representative templates. Excluded: registration, authenticated authoring, purchase/external partner flows, and every novel instance because they require accounts or duplicate audited templates.
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 pixel-identical in size to the default capture and remains light; the CSS probe found no prefers-color-scheme rule. F-001 medium: The interface ignores the user’s dark colour preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce active, the probe found a running 300 ms animation and no reduced-motion CSS. F-002 medium: Motion still runs when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/high-contrast capture kept primary text and controls visible. |
implement-natural-interactionsview-transitions | issues | high | The rendered page has hundreds of JavaScript pseudo-links for ranking state, while the CSS probe found no view-transition usage. F-003 low: Interactive state changes use abrupt legacy swaps rather than View Transitions. |
implement-natural-interactionsscroll-driven-animations | issues | high | DOM and HAR show Slick/jQuery scripts, while the CSS probe found no animation-timeline or scroll-driven CSS. F-004 low: Carousel and scroll-linked behaviour is implemented with legacy scripting rather than declarative timelines. |
implement-natural-interactionsphysical-gestures | pass | high | No custom pointer gesture handlers or gesture-only core flow were observed; core navigation uses native links and scrolling. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Long mobile captures show fixed desktop chrome with no progress or scroll-position cue; the CSS probe found no scroll-state mechanism. F-005 low: Navigation chrome does not respond to scroll state. |
provide-guided-navigationanchored-positioning | issues | high | DOM loads jQuery UI and global_menu.js; the CSS probe found no anchor-name or position-anchor support. F-006 low: Menus use legacy manually scripted positioning. |
provide-guided-navigationdirects-attention | issues | high | The home page exposes 294 JavaScript pseudo-links and no View Transition or highlight mechanism. F-007 low: Dynamic ranking navigation does not visibly guide focus after state changes. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a full-page dimmed overlay before users can browse; its root is fixed at z-index 2147483645. F-008 high: A consent interstitial blocks the entire primary experience on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The overlay probe identifies .fc-consent-root as a DIV with no role or aria-modal; the page has no dialog or popover elements. F-009 high: The consent modal is a custom div without dialog semantics. |
maximize-content-reduce-noisereduced-chrome | issues | high | Mobile screenshots show a scaled desktop grid and the novel page’s content interrupted by blocking consent chrome; HAR records 152 third-party requests. F-010 medium: Dense navigation, promotions and ads crowd the reading and discovery surfaces. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 emulation, layoutViewport.clientWidth is 1088 and the screenshots show tiny desktop text; viewport content is width=1088. F-011 critical: Mobile pages render a 1088 px desktop canvas scaled down to 360 px. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The same fixed-width desktop cards and columns are merely scaled on mobile, and the CSS probe found no @container rules. F-012 medium: Components do not adapt at container level. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The target probe found 22 visible controls below 24 px high, including header links at 16 px; the focused logo anchor had outline-style none. F-013 high: Many interactive targets are too short and keyboard focus is inconsistent. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The home title/description state the service purpose, search is visible, and the novel page presents title and chapter links. |
support-core-task-successprimary-flow-completion | issues | high | Home, search and novel screenshots all show the same blocking consent wall over the primary content. F-014 high: Consent blocks browsing, searching and reading before the user can complete the core flow. |
support-core-task-successclear-system-state-and-recovery | issues | high | Submitting the empty login form reports checkValidity=true, no invalid controls and no aria-live/alert region. F-015 medium: The login flow provides no client-side invalid state or accessible recovery message. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 14.2 s, FCP 4.5 s and performance 0.52; the independent trace measured LCP 6.57 s. F-016 high: Primary content loads too slowly. |
be-fast-and-stablevisual-stability | pass | high | Lighthouse CLS was 0.072 and mobile layout probes measured 0.009 on home, 0.025 on novel and 0.0004 on search. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reports 3.0 s main-thread work, 1.3 s JavaScript execution and 230 ms TBT. F-017 medium: Third-party and legacy scripting consumes substantial main-thread time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR lists ten VeryHigh/High parser-inserted CSS/JS candidates; Lighthouse estimates 2.39 s render-blocking savings and 1.70 MiB image savings. F-018 high: The critical path includes many parser-blocking resources and poorly prioritised images. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 470 KiB unused JavaScript; HAR records 26 scripts totalling 1.10 MB. F-019 medium: The page ships substantial unused and third-party JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found 12 images without alt and 3 untitled frames; login text/password inputs have zero associated labels. F-020 high: Images, iframes and form fields lack accessible names or associations. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports 319 failing colour-contrast nodes. F-021 high: Text and controls fail colour-contrast requirements at scale. |
be-inclusivestructure-and-focus | issues | high | The login page has no h1 or landmarks; the home h1 is empty; the focused home logo reports outline-style none. F-022 high: Landmark, heading and focus structure is incomplete. |
be-inclusivelegible-text | issues | high | All 360 px screenshots show the 1088 px layout reduced to roughly one-third scale, making navigation and novel text difficult to read. F-023 critical: Text becomes extremely small on phones because the desktop canvas is scaled. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse fails meta-viewport because maximum-scale=1 is below 5; target probe found 22 controls under 24 px high. F-024 high: Viewport and target sizing prevent robust zoom/reflow use. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured 17 console-error items. F-025 medium: The page emits numerous browser errors. |
follow-best-practicessound-document-and-assets | issues | high | Image audit found all 46 images missing width/height, 19 oversized, 44 without srcset and 46 in legacy formats. F-026 medium: Image delivery and document assets are poorly sized. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found one deprecated API warning and an Inspector Issues failure; the page loads jQuery 1.12.4. F-027 medium: Deprecated APIs and DevTools issues remain. |
be-discoverabletitle-and-description | pass | high | Home and novel probes found descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The probe counted 294 anchors with no usable href; Lighthouse fails crawlable anchors and the viewport uses width=1088. F-028 high: Hundreds of navigation actions are not crawlable and mobile metadata forces a desktop layout. |
be-discoverablecanonical-and-indexing-signals | issues | high | The home probe found no canonical URL and /sitemap.xml returned 404; robots.txt is present. F-029 medium: Canonical and sitemap signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | The novel probe found complete Open Graph fields but zero JSON-LD blocks for the literary work. F-030 low: Novel pages have social cards but no structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The page is HTTPS but has no CSP, HSTS or nosniff; 6 of 6 observed cookies were flagged insecure. F-031 critical: Baseline transport defenses and cookie flags are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker audit found 33 third-party origins and 8 known trackers; HAR attributes 152 requests and 3.33 MB to third-party origins. F-032 critical: The page has an outsized advertising and tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login DOM contains only ID/password fields with no autocomplete tokens or WebAuthn/passkey affordance; no on-load permission prompt was observed. F-033 medium: Authentication is password-only and lacks modern credential support. |
be-private-and-securedefensive-browser-policies | issues | high | Headers audit found no clickjacking protection, Referrer-Policy or Permissions-Policy in addition to missing CSP/HSTS. F-034 critical: Browser-enforced defense headers are absent. |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200 and substantive content; pages are not JS shells, with crawler screenshots retaining content. |
be-resilientresilient-runtime-behaviour | pass | high | Core navigation and reading are server-rendered links and remain available without fragile client routing. |
be-resilientoffline-and-installable | not-applicable | high | This public MPA is a content service rather than an installed app; offline installability is contextual and was not treated as required. |
be-resilientnetwork-and-http-failure-states | pass | high | A missing sitemap returned a branded server-rendered error document rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The service is deliberately Japanese-only and no alternate-language or bidirectional surface was found; internationalisation checks are out of scope for this run. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative public paths are Japanese-only and expose no user-selectable locale or currency flow. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, cross-zone event, or user-facing time-zone flow exists on the representative public paths. |
be-trustworthyno-dark-patterns | issues | high | The first view is blocked by consent while tracker evidence records 33 third-party origins; the primary buttons emphasise Consent and Manage options rather than a direct reject choice. F-035 high: The consent experience is a nagging, blocking wall backed by immediate tracking activity. |
be-trustworthyhumane-error-handling | issues | high | The empty form is considered valid and has no alert/live error region. F-036 medium: Login inputs do not prevent or explain empty submission errors. |
be-trustworthytrustworthy-input-assistance | issues | high | Both ID and password inputs have empty autocomplete values and no associated labels. F-037 medium: Sign-in fields omit autocomplete and label associations. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Login offers only ID/password with no passkey/WebAuthn option, although recovery and registration links are visible. F-038 medium: The account sign-in flow lacks phishing-resistant authentication. |
be-sustainableoptimised-assets | issues | high | The image audit found 19 oversized images, no modern formats, 44 missing responsive sources and 29 below-fold images not lazy-loaded. F-039 high: Images are oversized and unoptimised for their rendered use. |
be-sustainableno-wasteful-work | issues | high | HAR records 62 XHR/fetch requests and tracker scan shows 33 third-party origins during initial load. F-040 high: Advertising performs extensive background fetching with little direct user value. |
be-sustainablethird-party-and-media-budget | issues | high | 152 of 154 requests and 3.33 of 3.36 MB transferred were classed third-party; scripts alone transferred 1.10 MB. F-041 high: Third-party code dominates the page budget. |
be-agent-readystructured-agent-capabilities | issues | high | Lighthouse agentic browsing scored the rendered tree highly, but the probe found 294 JavaScript pseudo-links and no WebMCP evidence. F-042 low: Core search and reading capabilities are not exposed as structured agent tools. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generation feature is offered, so on-device inference has no existing task to evaluate. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten representative ranking interactions, heap size rose only about 0.31 MB (30.19 to 30.50 MB) and node count about 0.25%; no unbounded growth was demonstrated. |
be-memory-efficientbounded-footprint | pass | medium | Heap self-size was about 30.2 MB and post-scroll used JS heap about 23.2 MB, proportionate for the rendered page despite heavy third-party content. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The before/after heap summaries showed only small aggregate growth after ten interactions and no Detached constructor signal in the summary. |
Provenance
Canonical report: results/atomic/reports/0085-ncode_syosetu_com.json
Report SHA-256: e1a2a72e211429e72fbe7d97aca9012be113f1776830fef525966e01b620bbc0
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ncode_syosetu_com/2026-07-18T07-21-50-969Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ncode_syosetu_com/2026-07-18T07-21-50-969Z
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.