Manifest position 857 · CrUX rank bucket 1000
https://www.alphapolis.co.jp
Coverage complete
Coverage-complete representative audit of six public templates plus a deliberate 404 recovery state. Excluded: authenticated account management, paid manga reading/payment completion and author publishing because they require credentials or purchases.
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 remains the same white, light-only surface as the default capture; no dark-theme rule was found. F01 medium: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce, the hero .slick-track moved from matrix x=-1900 to x=-3198.39 in 4.5 seconds and retained a 1s transform transition. F02 high: Honours prefers-reduced-motion: non-essential animations and auto-advance are reduced or removed when the user asks for less motion. |
respect-user-preferencesrespects-contrast | issues | high | axe-core found serious color-contrast failures on ranking labels and the consent interface, with 56 additional nodes requiring review. F03 medium: Honours prefers-contrast / forced-colors: controls, text and scrollbars remain visible under high-contrast preferences. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found zero view-transition rules; page changes are traditional abrupt full-document swaps. F04 low: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling or scroll-linked reveal behavior was observed on the representative templates, so there is no scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The sampled desktop-style MPA templates expose no gesture-driven swipe/remove/pull interaction that needs a physical-gesture implementation. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Long listing/detail pages retain static dense chrome; CSS inspection found no scroll-state/container handling or progress cue. F05 low: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling. |
provide-guided-navigationanchored-positioning | not-applicable | high | No authored tooltip, transient popover or edge-positioned menu was found on sampled primary paths; the consent overlay is modal rather than anchored. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs, selected navigation underlines, ranked labels and episode lists provide visible location/sequence cues across sampled templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Every fresh-path mobile capture is obscured by a centered consent interstitial before the requested content can be used. F06 high: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM reports zero dialog/popover/details primitives while the consent UI adds multiple H1s and a custom overlay. F07 medium: Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs. |
maximize-content-reduce-noisereduced-chrome | issues | high | Mobile captures devote large portions of the page to stacked promotional sidebars, banners and navigation around much smaller primary content. F08 high: Minimise non-content chrome and borders so the content is the focus, not the application frame; expressive/decorative visuals serve the content rather than crowd it. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360px viewport, Chrome lays out a 1000-1002px desktop canvas and scales it to about 0.36; text and controls are tiny rather than reflowed. F09 critical: Layout adapts to narrow viewports with no horizontal overflow and no fixed pixel widths forcing a desktop layout on mobile; viewport meta present; fluid scaling and intrinsic sizing rather than brittle breakpoints. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe found zero @container rules, and the same multi-column desktop components are merely scaled down across all mobile captures. F10 high: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The target probe found 127 of 880 visible controls smaller than 24px; Lighthouse also failed target-size. F11 high: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Each sampled template has a descriptive title/H1 and recognizable next actions for browsing, opening a work, selecting an episode, buying or registering. |
support-core-task-successprimary-flow-completion | issues | high | The registration and content paths are immediately interrupted by consent, while scaled desktop forms make the primary journey difficult on a common mobile viewport. F12 high: The representative primary flow can be completed end-to-end with predictable steps, no avoidable dead ends, no hidden required information, and no needless detours through modals, account walls, or upsells. |
support-core-task-successclear-system-state-and-recovery | issues | high | After an empty registration submit, required controls became :invalid but no role=alert/error content appeared and focus was not moved to the first error. F13 high: Loading, empty, success, error, offline, and partial-completion states are visible and actionable; users can retry, undo, cancel, go back, or continue without losing context. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured performance 0.42 on home and 0.37 on novel detail; home CLS was 0.509 and novel-detail LCP was 17.0s with 840ms TBT. F14 critical: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | issues | high | The layout primitive observed home CLS 0.670, including one shift of 0.557; 20 images lack dimensions. F15 high: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported 5.8s main-thread work and 1.7s JavaScript execution on home, with TBT 488ms; detail/register TBT exceeded 840ms. F16 high: The main thread is not blocked by long tasks or heavy scripting; work is deferred, chunked, prioritised, or moved off-thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 201 requests and 13.45MB transferred; parser-inserted CSS/scripts are high-priority candidates and Lighthouse estimates 12.4MB cache-lifetime savings. F17 critical: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 1.39MB unused JavaScript on novel detail; home loads 39 scripts and extensive third-party code. F18 high: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | issues | high | axe found unlabeled search, select and submit controls on every sampled page, 20 unnamed links on home, two untitled frames on novel detail, and unlabeled registration confirmation/captcha fields. F19 critical: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology. |
be-inclusivesufficient-contrast | issues | high | axe reported serious contrast failures on all three sampled templates, including primary buttons and consent text. F20 high: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | axe found content outside landmarks and duplicate/unnamed landmarks; the consent vendor markup injects several extra H1 headings into the document outline. F21 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | issues | high | The 1000px desktop layout is scaled to 360px, making body copy, navigation and form text visibly tiny in every mobile capture. F22 critical: Text is legible and inclusively rendered: comfortable line layout, precise alignment, stable rendering across mixed fonts, no clipping or cramped wrapping that harms comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Mobile uses a 1000px layout viewport and Lighthouse fails target-size; 127 controls are below 24px before considering 200% zoom. F23 critical: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. |
follow-best-practicesno-console-errors | issues | high | Lighthouse reports browser console errors on home, novel detail and registration. F24 medium: The page loads without console errors or uncaught exceptions. |
follow-best-practicessound-document-and-assets | issues | high | Although doctype/UTF-8 are valid, the image audit found 20 missing dimensions and Lighthouse found an incorrectly proportioned image on registration. F25 medium: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found deprecated APIs, missing large-script source maps and DevTools inspector issues on all sampled paths. F26 medium: The page uses the platform cleanly: no deprecated APIs, no avoidable BFCache blockers, no broken source maps or inspector issues, no stale vulnerable libraries, no paste-prevention on inputs, and no notification/geolocation prompts on load. |
be-discoverabletitle-and-description | issues | high | Home and content pages have descriptive metadata, but /register has an empty meta description and Lighthouse fails meta-description there. F27 medium: The page has a unique, descriptive <title> and a meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse fails crawlable-anchors and the DOM has javascript:void(0) links; the viewport declaration produces a 1000px scaled layout on 360px devices. F28 high: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive. |
be-discoverablecanonical-and-indexing-signals | pass | high | All sampled public pages returned content with self-referencing canonical URLs; robots.txt permits them and points to a current sitemap index. |
be-discoverablestructured-and-shareable-metadata | issues | high | The homepage has Open Graph tags but zero JSON-LD despite representing an organization and many works; sampled entity pages expose no recorded structured-data evidence. F29 medium: Where the page represents an article, product, organization, event, place or other rich entity, structured data and share-preview metadata accurately describe the visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP and HSTS are absent and all 19 observed cookies were flagged; 12 cookies lacked Secure and all used permissive SameSite=None except two. F30 critical: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Before consent, network capture reached 33 third-party origins and 11 known tracker domains; the consent text names 209 partners. F31 critical: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No permission prompt appeared on load, but the account flow offers password registration only; no passkey/WebAuthn capability was found. F32 high: Permission prompts are requested in context (not on load), and authentication uses modern, phishing-resistant methods (passkeys / WebAuthn) where relevant rather than passwords alone. |
be-private-and-securedefensive-browser-policies | issues | high | Headers inspection found no clickjacking protection, Referrer-Policy, Permissions-Policy, X-Content-Type-Options, CSP or HSTS. F33 critical: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | pass | high | Discoverability capture found 100% rendered-content word coverage in 422KB raw HTML, no empty SPA mount and preserved title/description without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Sampled MPA routes rendered complete server content; the tested unknown route provided a stable explanatory recovery page and home link. |
be-resilientoffline-and-installable | not-applicable | high | This is a server-rendered public publishing/content service rather than an install-oriented app; offline installability is not required for the sampled core journeys. |
be-resilientnetwork-and-http-failure-states | pass | high | The deliberate unknown route showed a clear “page not found” explanation and a top-page recovery link instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang=ja is correct, but the CSS probe found only six logical-property rules and the fixed physical desktop layout does not adapt even to a narrower same-language viewport. F34 medium: Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited surface is deliberately Japanese-only and sampled pages did not expose user-entered currency, locale selection or locale-sensitive data operations. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, cross-time-zone event or user-facing time-zone workflow appeared on the representative paths. |
be-trustworthyno-dark-patterns | issues | high | A blocking consent dialog offers prominent Consent and Manage options but no equally direct Reject action, while tracker requests are already active before a choice. F35 critical: No deceptive design: no confirmshaming, forced continuity, disguised ads, or nagging consent walls; honest defaults; clear pricing and consent; easy reversal/cancel; predictable, declaratively-wired actions; and no hidden-text tricks (hidden content stays deep-linkable and indexable rather than used to deceive). |
be-trustworthyhumane-error-handling | issues | high | Empty registration submission produced native invalid states but no page error summary, accessible announcement or focus movement. F36 high: Forms prevent and recover from mistakes humanely: validate after interaction (not prematurely), give clear required-field feedback, announce errors accessibly, and signal invalid fields visibly rather than blaming the user. |
be-trustworthytrustworthy-input-assistance | issues | high | Registration username, email, password and confirmation fields all expose empty autocomplete values; axe also finds confirmation/captcha unlabeled. F37 high: Input is assisted, not obstructed: correct autocomplete tokens so address, payment, sign-in and sign-up fields autofill, and inputs are highlighted/sized to help the user rather than trip them up. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The sampled account flow relies on password-only registration and is obscured by consent; no passkey capability or clear privacy-preserving default is present. F38 high: Checkout, subscription, consent, authentication and account-management flows are clear, reversible, and proportionate: pricing and commitments are visible, cancellation is findable, sensitive actions re-authenticate when appropriate, and users are not tricked into continuity. |
be-sustainableoptimised-assets | issues | high | The homepage transfers 11.86MB of images; 48 images use legacy formats, 10 are oversized, 22 lack srcset and 21 below-fold images are not lazy. F39 critical: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized. |
be-sustainableno-wasteful-work | issues | high | The homepage makes 201 requests, loads 39 scripts and sends traffic to 33 third-party origins, including multiple analytics systems before consent. F40 high: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 150 requests and 12.91MB; home imagery alone reaches 11.86MB and individual covers exceed 600KB. F41 critical: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing capabilities are emerging and optional; no declared agent surface or transaction API was in scope for this public content site. |
be-agent-readyon-device-inference | not-applicable | high | On-device inference is an optional emerging enhancement and is not necessary for the sampled browse/read/register tasks. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 novel/manga tab toggles, summarized heap grew from 33.85MB/608,281 nodes to 35.42MB/615,824 nodes (about 4.6%/1.2%); no constructor showed interaction-proportional growth. |
be-memory-efficientbounded-footprint | pass | medium | The content-heavy homepage retained about 35.4MB in the post-interaction summary; object/array populations remained nearly flat and proportionate to the loaded page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appeared in either top-constructor summary and repeated toggles did not materially grow Object/Array/closure populations. |
Provenance
Canonical report: results/atomic/reports/0857-www_alphapolis_co_jp.json
Report SHA-256: 2abadb9de056c733b014dfdd377d0e262e22062836fecdd80a15844e1abe4673
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_alphapolis_co_jp/2026-07-23T11-13-46-105Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_alphapolis_co_jp/2026-07-23T11-13-46-105Z
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.