Manifest position 19 · CrUX rank bucket 1000
https://cardgames.io
Coverage complete
Atomic coverage complete: 58/58 checks judged across five representative 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 | The dark-emulated screenshot is visually unchanged from the normal capture; the computed root color-scheme is normal and the CSS probe found no prefers-color-scheme rule. F01 medium: The site does not follow the system dark-color preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce the stylesheet probe found no reduced-motion rule, while the page loads fireworks effects and exposes confetti/holiday-effect settings. F02 medium: Motion preferences are not wired to the game’s effects. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast screenshot remains visually unchanged; Lighthouse reports contrast failures including 2.19:1 themed links and 4.42:1 consent action text. F03 medium: High-contrast preferences do not change the interface, and controls retain contrast failures. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no view-transition usage, while primary actions and full-page game links replace state without directional continuity. F04 low: Game and route state changes are abrupt. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface was present on the representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull, carousel, or gesture-driven primary interaction was present; card moves are click/tap game actions. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Desktop/mobile screenshots and DOM inspection show persistent, compact navigation without a scroll-dependent orientation failure; the long page remains navigable. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored popover, or edge-positioned menu requiring anchor positioning was found. |
provide-guided-navigationdirects-attention | pass | high | Game titles, board framing, persistent top links, and the tested 404 page provide visible orientation and next destinations. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and 360 px screenshots show an opaque modal over the primary content before interaction; on mobile it consumes nearly the full viewport. F05 high: A first-visit consent wall obscures the entire catalog and every game. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection found zero dialog, popover, or details elements but two role=dialog custom divs, including the blocking consent UI. F06 medium: Overlays are custom ARIA divs rather than native dialog/popover primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | After accounting for the separately reported consent wall, screenshots show the board/catalog as the dominant surface with compact persistent navigation. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout at 360x800 reports scrollWidth=clientWidth=360 and zero overflow on home and Solitaire, with viewport meta present. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Desktop/mobile screenshots show catalog, board, navigation, and consent components reflow to their available width without clipping. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse identifies the 40x32 mobile-menu button with no accessible name and multiple social links only 17 px high; keyboard focus itself is visible when present. F08 medium: Some controls are inaccessible or too small for non-pointer users. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Titles, game catalog labels, visible boards, and game controls clearly communicate the purpose and next action on all representative paths. |
support-core-task-successprimary-flow-completion | issues | high | Every representative game screenshot shows the consent wall covering the board and controls on first visit, adding a required detour before play. F07 high: The primary play journey is interrupted before users can interact. |
support-core-task-successclear-system-state-and-recovery | pass | high | The invalid-route probe renders a descriptive PAGE NOT FOUND state, apology, and extensive recovery links; game pages expose pause/restart/status controls. |
be-fast-and-stablegood-core-web-vitals | pass | high | Trace gives LCP 1.06 s and TBT 18.79 ms; Lighthouse gives LCP 1.7-1.9 s, CLS 0, TBT 120-140 ms and performance 0.96. |
be-fast-and-stablevisual-stability | pass | high | Mobile layouts report CLS 0.00032 on home and 0 on Solitaire with no horizontal overflow; Lighthouse CLS is 0. |
be-fast-and-stableefficient-main-thread | pass | high | Trace records one 68.79 ms long task and 18.79 ms TBT; Lighthouse TBT remains 120-140 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR: 89 requests and 1,854,791 transferred bytes; 19 third-party requests transfer 701,861 bytes, including 403 KB from the CMP and 299 KB from Google tags. F09 medium: Non-critical consent and analytics dependencies dominate the initial network. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The two Google tag scripts alone transfer about 299 KB, the CMP SDK about 127 KB, and Lighthouse interactive time is 9.2-10.0 s despite good paint metrics. F10 medium: Third-party JavaScript adds substantial startup cost without core game value. |
be-inclusivenames-roles-labels | issues | high | Lighthouse button-name fails on button#mobile-menu on both homepage and Solitaire; it has no text, aria-label, aria-labelledby, or title. F11 high: The mobile menu has no accessible name. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports themed links at 2.19:1, board text at 3.77:1, and the accept button at 4.42:1 against a 4.5:1 requirement. F12 high: Game-theme and consent text do not meet minimum contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports New Game, Restart, Pause, and Options hash links as skip links without valid targets; the document also contains two H1 elements in game state. F13 medium: In-page game action links point to missing focus targets. |
be-inclusivelegible-text | pass | high | Representative screenshots show readable body/rules text with stable wrapping; specific measured contrast defects are recorded separately. |
be-inclusivezoom-reflow-targets-and-media | pass | high | The viewport permits scaling and both 360 px layouts reflow without overflow; target-size defects are recorded under input modality. |
follow-best-practicesno-console-errors | pass | high | Lighthouse reports no console-error or uncaught-exception audit failure on either homepage or Solitaire. |
follow-best-practicessound-document-and-assets | pass | high | DOM evidence confirms HTML doctype, UTF-8 charset and viewport metadata; Lighthouse homepage best-practices score is 1.0. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse best-practices is 0.77 on Solitaire and reports an Issues-panel third-party-cookie problem from a.pub.network. F14 low: The game template logs a browser inspector cookie issue. |
be-discoverabletitle-and-description | pass | high | DOM probes show descriptive titles and a non-empty description meta value on the public templates. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Rendered links use real hrefs, viewport meta is present, robots.txt does not block crawling, and Lighthouse SEO is 1.0. |
be-discoverablecanonical-and-indexing-signals | issues | high | A request to /sitemap.xml returns the site’s Page Not Found HTML; robots.txt is empty. Canonical and hreflang signals otherwise exist. F15 medium: The site does not publish a working sitemap. |
be-discoverablestructured-and-shareable-metadata | issues | high | Open Graph metadata exists, but DOM inspection found no JSON-LD on the homepage despite the site representing a collection of playable games. F16 low: Game pages lack structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS, nosniff and X-Frame-Options are present, but CSP is absent; both observed first-party cookies lack Secure and country uses SameSite=None. F17 high: Security headers and cookie flags are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The banner names 1,017 partners; the load contacts four third-party origins and known Google trackers, transferring 701,861 third-party bytes. No sensitive secret was exposed. F18 high: The initial privacy footprint is disproportionate to a simple card-game visit. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | The audited public games require neither browser permissions nor authentication. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence shows no Content-Security-Policy or Permissions-Policy; HSTS, framing, referrer and nosniff protections are present. F19 medium: Browser-enforced policy coverage is incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability shows 85-86% rendered-word coverage in raw HTML, with title and H1 present and no empty JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Representative mobile/desktop captures show board and consent overlays contained by the viewport; focus and navigation remain available. |
be-resilientoffline-and-installable | issues | high | A valid standalone manifest exists, but navigator.serviceWorker.getRegistrations() returned no registrations on Solitaire. F20 medium: The app-like game site is installable in metadata only and has no offline fallback. |
be-resilientnetwork-and-http-failure-states | pass | high | The invalid route renders a useful 404 page with clear recovery links rather than a blank shell or infinite spinner. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The page publishes six hreflang locales and correct lang=en, but stylesheet inspection found no logical-property signal in the inspected rules and no dir declaration. F21 medium: The localized site is not demonstrably writing-mode resilient. |
be-internationalisedlocale-aware-data | not-applicable | high | Representative pages expose no dates, currencies, or locale-sensitive numeric data requiring Intl formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | No events, schedules, recurring times, or time-zone-sensitive data are part of the audited journeys. |
be-trustworthyno-dark-patterns | pass | high | Consent presents Reject All and Accept with equal prominence, games require no signup/payment, and no forced continuity was observed. |
be-trustworthyhumane-error-handling | pass | high | The available report form has explicit labels and the invalid-route state uses neutral language plus recovery links; no blaming or premature error state was observed. |
be-trustworthytrustworthy-input-assistance | issues | high | DOM inspection found labelled name, email, description, device, and location fields, but every field has an empty autocomplete attribute value. F22 low: The user-report form omits autocomplete hints. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication, or account-management flow exists in the audited scope. |
be-sustainableoptimised-assets | pass | high | The image audit found no oversized rendered images and no missing srcset on the inspected image elements; the material page-weight issue is recorded under media budget. |
be-sustainableno-wasteful-work | pass | high | Trace shows only one short long task and low TBT over 6.5 seconds, with no evidence of continuous background CPU work. |
be-sustainablethird-party-and-media-budget | issues | high | HAR transfers 1.85 MB on the homepage: 702 KB third party and 1.05 MB images, including a 156 KB decorative stadium image and multiple tag/CMP bundles. F23 medium: Third-party and decorative media cost is high relative to the core interaction. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent readiness is emerging and contextual; this free card-game site exposes no transactional agent-facing workflow, so absence is not penalized. |
be-agent-readyon-device-inference | not-applicable | high | No summarization, language-model, or other inference task is part of the card-game experience; absence is not penalized. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | Heap summaries rise from 17,365,169 bytes/364,950 nodes to 24,988,197 bytes/530,849 nodes after ten menu open/close cycles. The separate-session comparison makes confidence medium and does not isolate a constructor leak. F24 medium: Repeated menu exercise shows substantial retained-heap growth that needs investigation. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap is 17.37 MB for an interactive game plus consent UI, proportionate to this surface; no single constructor dominates unexpectedly. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary lists a Detached* constructor among the largest populations; repeated-growth uncertainty is recorded separately. |
Provenance
Canonical report: results/atomic/reports/0019-cardgames_io.json
Report SHA-256: 76fc5bda5a95b1640b10c4151a7550417e440aae8dd371020f08e661ff0ed8ad
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/cardgames_io/2026-07-17T21-36-22-272Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/cardgames_io/2026-07-17T21-36-22-272Z
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.