Manifest position 26 · CrUX rank bucket 1000
https://boardgamearena.com
Coverage complete
Complete atomic coverage of all 58 catalog checks across six representative public paths. Authenticated gameplay, payment, account management, and destructive account actions were intentionally not covered because they require credentials or side effects.
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 | Screenshot comparison under emulated dark preference shows the same light #f7f7f7 landing surface; CSS only switches when an html.dark class is set, so the system preference does not select dark mode. 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 | The reduced-motion probe matched prefers-reduced-motion: reduce but still found infinite 1.75s fa-blink animations and many non-zero transitions. F02 medium: 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 | pass | high | Forced-colors plus prefers-contrast screenshot preserves visible text, links, primary action, and focusable chrome. |
implement-natural-interactionsview-transitions | issues | medium | CSS/DOM probe found no view-transition rules and route changes use full, abrupt document swaps across the representative navigation. F03 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 | None of the representative public templates uses parallax, scrollytelling, or scroll-linked reveal motion, so there is no scroll-driven effect to implement. |
implement-natural-interactionsphysical-gestures | issues | medium | The game listing exposes horizontally paged carousels, but CSS inspection found no scroll-snap or overscroll declarations; movement is handled by custom arrow controls. F04 low: Gesture-driven interactions and entry/exit motion feel native (declarative overscroll/scroll-snap, physics-based easing, animating to intrinsic sizes, pull/swipe gestures) rather than fighting the platform with custom pointer handlers. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | Screenshots and CSS show static fixed navigation without a scroll-progress or scroll-state response despite long pages of 5,877 to 9,259 CSS px. 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 | issues | medium | Menus and panels are implemented with fixed/absolute positioning in the captured CSS; no anchor-name, position-anchor, or position-try declarations were found. F06 low: Tooltips, popovers and menus use CSS anchor positioning (with fallback positions) so they stay attached and reposition correctly rather than being manually positioned. |
provide-guided-navigationdirects-attention | pass | high | Active top-level sections are highlighted, listing headings are prominent, and game-detail Learn/Play actions provide clear directional cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No load-time interstitial or consent wall obscured content on any of the five representative public templates. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM probe found zero dialog, popover, or details elements while signup and menu overlays are custom containers, so modal/disclosure semantics and platform light-dismiss are absent. 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 | pass | medium | The landing, news, listing, and game-detail templates devote their main regions to games and editorial content with compact global navigation. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, both landing and listing layout metrics report scrollWidth=clientWidth=360 with viewport meta present and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The layout adapts at viewport breakpoints, but live CSS inspection found no @container/container-type rules for reused game cards and controls. F08 low: 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 | Focus probes retain a native outline, but Lighthouse target-size audits fail and the live probe found many links only 14 to 15px tall. F09 medium: 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 | The first viewport states the offer, its free/browser-based nature, and a single prominent Start playing now action. |
support-core-task-successprimary-flow-completion | pass | medium | The public primary journey from landing to game discovery, a specific game, and account creation is reachable through real links with clear Learn, Play, and Create an account actions; account submission itself was not performed to avoid creating test data. |
support-core-task-successclear-system-state-and-recovery | pass | high | An invalid URL renders a clear not-found state with a homepage recovery link, and the signup surface includes support and login alternatives. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured homepage LCP 28.5s/TBT 600ms, gamelist LCP 28.4s/CLS 0.159, and signup LCP 23.2s/CLS 0.158. F10 high: 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 | Mobile layout observers measured CLS 0.287 on home and 0.299 on gamelist; all 17 inspected images lacked width/height attributes. F11 medium: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | issues | high | Trace recorded three long tasks and 59.66ms TBT under a fast local run; throttled Lighthouse measured 600 to 710ms TBT. F12 medium: 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 recorded 4.99MB transferred, including three parser-blocking stylesheets and three classic parser-inserted scripts without async/defer/module confirmed by DOM. F13 medium: 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 | The landing page ships 3.88MB of JavaScript; sveltec alone is 2.12MB and legacy Dojo plus analytics bundles load before interaction. F14 medium: 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 | Lighthouse fails image-alt, link-name, label-content-name-mismatch, and signup form-label audits; the listing probe shows numerous image-only game links with no accessible name. F15 high: 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 | Lighthouse color-contrast audit fails on all three tested templates. F16 medium: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | All tested templates have zero main/navigation landmarks and no h1; Lighthouse fails landmark-one-main. Keyboard focus remains visible, but page structure is not logical for assistive technology. F17 medium: 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 | pass | medium | Desktop and mobile screenshots show readable line lengths, unclipped primary copy, and responsive wrapping across the representative templates. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Narrow screenshots reflow without horizontal overflow, but Lighthouse target-size fails and many interactive links measure only 14 to 15px high. No essential media requiring captions appears in the audited paths. F18 medium: 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 | pass | medium | Lighthouse did not report a console-errors or runtime exception failure on the three tested templates. |
follow-best-practicessound-document-and-assets | issues | high | Direct probes confirm standards mode and an HTML doctype, but image audit reports 17/17 missing dimensions, 16 legacy formats, and one oversized asset. F19 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 reports five BFCache failure reasons and missing source maps for large first-party JavaScript on all tested templates. F20 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 | Homepage and game detail have descriptive metadata, but /gamelist has an empty meta description. F21 medium: The page has a unique, descriptive <title> and a meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Viewport meta and robots.txt are present, but Lighthouse finds non-crawlable anchors on /gamelist and the DOM contains many href="#" pseudo-links with generic or empty text. F22 medium: 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 | issues | high | The public /gamelist page canonically points to the homepage and /sitemap.xml returns a 404, weakening indexing consistency. F23 medium: Public pages expose the indexing signals search engines need: successful HTTP status, canonical URL when appropriate, hreflang for localized variants, robots/sitemap consistency, and no accidental noindex/noarchive policy. |
be-discoverablestructured-and-shareable-metadata | issues | medium | Game detail has accurate Open Graph metadata but no JSON-LD for the visible game entity; homepage also has no structured data. F24 low: 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, HSTS and nosniff are present, but CSP permits unsafe-inline and unsafe-eval; analytics cookies use SameSite=None and two are not Secure. F25 high: 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 | Tracker capture found nine third-party origins and active Google Tag Manager/DoubleClick; HAR records analytics and consent SDK traffic on first load. F26 medium: 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 | medium | No permission prompt fired on load, but the public signup offers email/social identity only and no passkey/WebAuthn path was exposed. The scanned Google API key is treated as a likely public client key, not a secret. F27 low: 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 | HSTS, X-Frame-Options and frame-ancestors are set, but Referrer-Policy and Permissions-Policy are missing and CSP retains unsafe-inline/unsafe-eval. F28 medium: 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 comparison reports 94% rendered-word coverage in raw server HTML, isJsShell=false, and visible crawler rendering. |
be-resilientresilient-runtime-behaviour | pass | medium | Five public templates loaded to coherent states at desktop/mobile widths; menus and content were not visibly clipped, and no runtime exceptions were reported. |
be-resilientoffline-and-installable | pass | medium | A manifest with standalone display, start_url and complete icon set is linked, and navigator.serviceWorker is available on the loaded page. Offline gameplay is intrinsically networked and was not treated as required. |
be-resilientnetwork-and-http-failure-states | pass | high | A representative unknown route renders a clear, branded error state and a direct homepage recovery action rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The page has lang=en, dir=ltr and hreflang links for many locales, but loaded CSS inspection found 22 physical left/right rules and zero logical-property rules. F29 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 | pass | medium | The site exposes many locale-specific hosts via hreflang and a language switcher; representative English content and locale metadata agree. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative unauthenticated landing, listing, game detail, signup, and news first-view states expose no user-scheduled or timezone-sensitive event data to judge. |
be-trustworthyno-dark-patterns | pass | high | Signup plainly states that it is free, presents equivalent identity choices without preselection, links the privacy policy, and provides a visible existing-account route. |
be-trustworthyhumane-error-handling | issues | high | Signup email fields have no associated labels or required semantics; clicking Create an account with an empty field produced no visible, accessible inline recovery message in the captured state. F30 medium: 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 | pass | high | Public account inputs expose autocomplete=email and autocomplete=username tokens. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | The public account entry clearly identifies free registration, privacy handling, social alternatives, and the route back to login; no subscription continuity or hidden pricing appeared. |
be-sustainableoptimised-assets | issues | high | Image audit reports 16 legacy-format images, 8 without responsive sources, 16 below-fold images without lazy loading, and one oversized logo. F31 medium: 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 landing page transfers 4.99MB and opens analytics, consent, Sentry and realtime/legacy runtime scripts before the user interacts; script transfer alone is 3.88MB. F32 medium: 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 | HAR attributes nearly all 4.99MB to non-main origins and tracker evidence finds nine third-party origins; Google tag scripts alone transfer about 324KB. F33 medium: 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 | No declared agent-facing surface or WebMCP intent exists for the public entertainment pages; absence is treated as an emerging opportunity, not a failure. |
be-agent-readyon-device-inference | not-applicable | high | The audited public discovery and signup tasks do not require summarisation or language-model inference, so built-in AI is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten filter open/Escape cycles, heap self-size fell from 64.0MB to 58.5MB; node count rose only 0.56%, which is within cross-navigation snapshot variance and does not show unbounded retained growth. |
be-memory-efficientbounded-footprint | issues | medium | The gamelist baseline heap contains about 950,016 nodes and 64.0MB self-size before interaction, disproportionate for a public catalogue view and consistent with its multi-megabyte runtime. F34 low: Heap size and DOM node count are reasonable for what the page is; the footprint is proportionate rather than bloated. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appears among leading heap constructors; after repetition closures changed by only 7 (37,472 to 37,479) and arrays by 84, with no monotonic leak signal. |
Provenance
Canonical report: results/atomic/reports/0026-boardgamearena_com.json
Report SHA-256: 93bc2aac9bb62ad1bfd6e776067c1fd590bbcf477f0191c8b8c3af857f6309cc
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/boardgamearena_com/2026-07-17T22-21-08-514Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/boardgamearena_com/2026-07-17T22-21-08-514Z
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.