Manifest position 211 · CrUX rank bucket 1000
https://www.jra.go.jp
Coverage complete
Coverage-complete audit of six representative paths. Excluded: authenticated betting/account services on other origins, transaction completion, and every individual race/news detail page because one representative template per archetype was selected.
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 preference probe matched dark mode but reported color-scheme: normal and body text rgb(51,51,51); the emulated-dark screenshot retains white surfaces. F01 medium: No dark color-scheme adaptation |
respect-user-preferencesrespects-reduced-motion | issues | high | The CSS context shows the only reduced-motion rule comes from Font Awesome. The main carousel has no reduction rule, and the reduced-motion screenshot caught an in-progress dark cross-fade. F02 medium: Primary carousel does not fully respect reduced motion |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors CSS explicitly retints active carousel dots and scrollbars; axe found no definite contrast violation (14 items required manual review), and desktop screenshots remain legible. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS probes found no authored view-transition-name or transition API usage across the representative templates. F03 low: Page and state changes do not use transition continuity |
implement-natural-interactionsscroll-driven-animations | issues | high | The resource probe found jQuery, Slick and Swiper, while the authored CSS probe found no animation-timeline usage. F04 low: Carousel and scroll effects rely on legacy libraries rather than scroll timelines |
implement-natural-interactionsphysical-gestures | pass | high | Homepage carousel exposes swipe/pagination affordances and authored CSS includes overscroll behavior; no custom pointermove anti-pattern was observed in the resource/DOM probe. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Desktop and mobile screenshots show persistent global navigation, carousel position dots and horizontal scroll feedback for campaign/service shelves. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, callout or edge-sensitive anchored overlay was present on the representative paths; the only overlay is a centered full-page search modal. |
provide-guided-navigationdirects-attention | pass | high | News, calendar and beginner screenshots use breadcrumbs, highlighted current tabs/month and strong section headings to direct attention after navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial-load screenshots show core content immediately with no consent, signup or promotional interstitial covering the viewport. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | After opening search, the visible #modal is a DIV without role=dialog or aria-modal, and document.activeElement is BODY. No dialog or popover exists. F05 high: Search modal is a non-semantic fixed div and loses focus |
maximize-content-reduce-noisereduced-chrome | issues | high | The desktop screenshot shows four dense navigation/header rows before content; the 360px capture scales that entire desktop chrome and its small labels into the viewport. F06 medium: Navigation chrome overwhelms the first viewport |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The homepage declares meta viewport width=1200. At a 360x800 device viewport, layout reports a 1200 CSS-pixel viewport at scale 0.3, making the whole desktop page tiny rather than reflowing. F07 high: Homepage uses a fixed 1200px viewport on phones |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Across four templates the CSS probes found zero container rules; the homepage instead forces width=1200 and links to a separate smartphone site. F08 medium: Components do not adapt to their available container |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse found 15px-high news links with less than the required safe spacing; dense scaled homepage controls are also visibly small at 360px. F09 medium: Some mobile targets are too small or tightly spaced |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage first viewport identifies JRA and exposes race cards, odds, results, schedule, live coverage and betting login with explicit Japanese labels. |
support-core-task-successprimary-flow-completion | pass | high | The news search form has a labelled query control and navigates to a branded search-results page; race calendar and beginner content routes loaded without authentication barriers. |
support-core-task-successclear-system-state-and-recovery | pass | high | An unknown route rendered a branded Forbidden state explaining likely causes and providing FAQ/contact and homepage recovery links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured homepage LCP 23.3s and news LCP 6.9s; the raw trace corroborated homepage LCP 6.80s, FCP 3.87s and 84.5ms TBT under a separate run. F10 high: Cold-load LCP is far outside the good threshold |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0.035 on home, 0 on news/calendar and 0.063 on beginner, all below the 0.1 good threshold in these runs. |
be-fast-and-stableefficient-main-thread | pass | high | Trace total blocking time was 84.5ms with one 134.5ms long task; Lighthouse TBT was 170ms home and 120ms news, within the good threshold. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 159 requests and 4.84MB transferred, including 3.71MB images. DOM confirmation shows multiple synchronous head scripts; Lighthouse estimates 2.15s render-blocking savings and 3.8MB cache savings. F11 high: The homepage ships a large, blocking resource graph |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 301KiB unused JavaScript and 40KiB unused CSS on home, plus legacy JavaScript and unminified CSS. F12 medium: Large amounts of CSS and JavaScript are unused on initial load |
be-inclusivenames-roles-labels | issues | high | axe found critical missing alt text on two meaningful images and a focusable element inside aria-hidden. Lighthouse on news found prohibited ARIA and broken tab role parent/child relationships. F13 high: Interactive and image semantics are invalid or missing |
be-inclusivesufficient-contrast | pass | high | axe produced no confirmed color-contrast violation; desktop screenshots show readable text/control contrast and forced-colors overrides exist for key carousel controls. |
be-inclusivestructure-and-focus | issues | high | axe/Lighthouse report no main landmark; news uses tabindex=1 and malformed tab/list roles. The search modal opens with focus left on BODY. F14 high: Pages lack main landmarks and contain broken focus structure |
be-inclusivelegible-text | pass | high | News and calendar desktop screenshots show readable Japanese text, clear hierarchy and comfortable line lengths in the principal content column. |
be-inclusivezoom-reflow-targets-and-media | issues | high | meta viewport width=1200 shrinks content to 30% scale at 360px, and Lighthouse flags undersized news touch targets. F15 high: The homepage does not reflow at a phone-sized viewport |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console with one recorded browser error. F16 low: Homepage logs a browser console error |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found all 100 homepage images lacked width/height attributes; 45 were oversized and 69 had empty/missing alt (many decorative, but two were independently confirmed meaningful). F17 medium: Images omit intrinsic dimensions at scale |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports Inspector cookie issues, 33KiB legacy-JavaScript savings and third-party-cookie usage; the page loads jQuery 3.5.1 and compatibility shims synchronously. F18 medium: Legacy and cookie issues surface in DevTools |
be-discoverabletitle-and-description | issues | high | The metadata probes found no description on the race calendar or beginner guide, although titles were present. F19 medium: Important content templates omit meta descriptions |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The homepage viewport is width=1200 and is rendered at scale 0.3 on a 360px device; Lighthouse SEO is 0.85 despite crawlable raw HTML. F20 high: The canonical homepage is not mobile-friendly |
be-discoverablecanonical-and-indexing-signals | issues | high | The calendar has no canonical link, and a direct /sitemap.xml request returned HTTP 403 while robots.txt allows crawling. F21 medium: Indexing signals are incomplete across templates |
be-discoverablestructured-and-shareable-metadata | issues | high | All four page probes found zero JSON-LD; the calendar has no Open Graph metadata and the beginner OG description is empty. F22 low: Structured and social metadata coverage is inconsistent |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS, nosniff and SAMEORIGIN are present, but the header audit found no Content-Security-Policy, Referrer-Policy or Permissions-Policy. F23 high: Sensitive browser policy headers are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The page contacted 13 third-party origins and five known tracker domains. HAR attributes 26 requests and 776,864 bytes to third parties; no consent control was found. F24 high: Tracking starts with a broad third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | Audited JRA pages contain no authentication or permission flow; betting login is a separately hosted service outside this audit scope, and no permission prompt fired on load. |
be-private-and-securedefensive-browser-policies | issues | high | All five observed first-party analytics cookies lacked Secure; four used SameSite=None and two persisted for 400 days. CSP, Referrer-Policy and Permissions-Policy were absent. F25 high: Cookie and policy defenses are incomplete |
be-resilientprogressive-enhancement | pass | high | Discoverability fetch returned HTTP 200 with 96% rendered-word coverage in raw HTML; crawler screenshot retains the main content and the site is not a JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | The custom search overlay opens without a dialog role or aria-modal and focus falls to BODY, so keyboard and assistive-technology state is not preserved. F26 medium: Overlay runtime behavior is not robust for keyboard users |
be-resilientoffline-and-installable | not-applicable | high | The public information site does not declare installable/offline intent; its manifest explicitly uses display: browser and no service worker controlled the page. |
be-resilientnetwork-and-http-failure-states | pass | high | The unknown-route probe shows explicit Forbidden messaging plus FAQ/contact and homepage recovery links instead of a blank or raw server error. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The audited service is explicitly Japanese-language with a separate external English site; no same-document locale or RTL presentation is offered or declared. |
be-internationalisedlocale-aware-data | not-applicable | high | The selected pages target a Japanese locale and expose no locale selector or locale-varying input; evaluating alternate locale formatting is outside the site’s observed intent. |
be-internationalisedtime-zone-correctness | not-applicable | high | No user-scheduled cross-time-zone event or time-zone input exists on the representative pages; calendar data is Japan-specific. |
be-trustworthyno-dark-patterns | pass | high | Screenshots and inspected flows show no confirmshaming, forced continuity, disguised advertisements or obstructed cancellation on the audited public-content paths. |
be-trustworthyhumane-error-handling | pass | high | The required global-search field is labelled, uses native required validation, and the failure route explains the problem and provides recovery actions. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The audited same-origin forms are search-only and collect no identity, address, payment or sign-in data eligible for autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Commercial betting and account authentication are hosted on separate origins and were not entered; public JRA content itself contains no checkout/subscription/account flow. |
be-sustainableoptimised-assets | issues | high | The image audit found 45 oversized images, 38 legacy-format images, 34 without responsive sources and 51 below-fold images without lazy loading. Lighthouse estimates 2.36MB image savings. F27 high: Image delivery wastes substantial bandwidth |
be-sustainableno-wasteful-work | issues | high | The homepage initiates 26 third-party requests and loads multiple analytics/advertising stacks, including 776KB third-party transfer, without an observed consent gate. F28 medium: Optional tracking creates wasteful background work |
be-sustainablethird-party-and-media-budget | issues | high | HAR measured 4.84MB over 159 requests, with 3.71MB images and 776KB third-party bytes; the largest two hero images alone transfer 613KB and 541KB. F29 high: Page and third-party weight exceed a proportionate budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | No developer intent for agent-executable transactions is declared; this public information site remains crawler-readable, but WebMCP capability registration is contextual and not required here. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation or other user-facing inference use case is present on the selected paths, so built-in on-device AI is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten search-overlay open/close attempts, heap self-size increased 3.3% (22.87MB to 23.62MB), nodes 1.6% and closures 0.4%; no monotonic detached-node signal appeared in summary constructors. |
be-memory-efficientbounded-footprint | pass | medium | The loaded media-rich homepage heap summary was 22.87MB self-size with 405,045 nodes; code/objects were bounded and proportionate to the unusually dense page, though network/DOM reduction remains desirable. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Baseline/post summaries contain no Detached* constructor among leading retained populations; Array, Map, Set and closure counts remained nearly flat after repeated overlay interaction. |
Provenance
Canonical report: results/atomic/reports/0211-www_jra_go_jp.json
Report SHA-256: b7ebdb8850849ac3c4728719272330ae93647e9aec846f2194bbbdc0cdab4c58
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_jra_go_jp/2026-07-19T04-48-49-546Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_jra_go_jp/2026-07-19T04-48-49-546Z
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.