Manifest position 301 · CrUX rank bucket 1000
https://steamcommunity.com
Coverage complete
Coverage-complete representative audit of eight public/unauthenticated paths. Authenticated posting, purchasing, cancellation, account settings, and destructive actions were not covered because no test account or transaction authority was provided.
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 | DOM computed styles report color-scheme: normal and the dark-emulated screenshot is materially identical to the default dark surface. F01 medium: The theme is hard-coded dark rather than adapting to the user color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | medium | evaluate under prefers-reduced-motion: reduce found zero active animations; no auto-advance was observed. |
respect-user-preferencesrespects-contrast | pass | medium | forced-colors screenshot retained visible text, controls, borders and links across the first viewport. |
implement-natural-interactionsview-transitions | issues | medium | The reduced-motion/modern-CSS probe found no view-transition CSS, and the sampled feed/filter navigation uses abrupt page/state replacement. F02 low: Browse/filter and route changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | medium | CSS/animation probe found no scroll-linked animation and the layout observer showed only two bounded long tasks, so no main-thread scroll-animation anti-pattern was observed. |
implement-natural-interactionsphysical-gestures | pass | medium | Mobile browsing uses native page scrolling with no observed custom pointer interaction fighting scrolling; layout has no horizontal overflow. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | Desktop and mobile screenshots show static chrome on a very long 15,707px feed; CSS inspection found no scroll-state or animation-timeline rules. F03 low: Navigation chrome does not respond to scroll state or expose reading/feed position. |
provide-guided-navigationanchored-positioning | pass | medium | Sampled menus, search controls and fixed consent surface remained aligned within the viewport on desktop and mobile; no drifting edge overlay was observed. |
provide-guided-navigationdirects-attention | issues | medium | Feed category/filter controls swap content without transition/highlight continuity; no View Transition or scroll-marker rules were found. F04 medium: State changes provide weak continuity cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | On the 360x800 capture the fixed cookie panel covers roughly the lower third of the first viewport and overlaps feed cards; it also overlays every desktop archetype. F05 medium: The cookie prompt obscures a large share of core content on every sampled template. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM/CSS evidence identifies .cookiepreferences_popup and .cookiepreferences_popup_content custom containers; no dialog/popover primitive is present. F06 low: The consent overlay is custom div-based chrome rather than a semantic dialog/popover primitive. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Across home, discussions, Workshop, Market and app hub, most of the viewport is allocated to the requested community content rather than decorative application framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | Mobile layout primitive measured scrollWidth=clientWidth=360 with zero horizontal overflow and a valid viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The CSS probe found no @container/container-type usage; reused cards, search panels, and navigation are adapted only by global responsive CSS. F07 low: Responsive behavior is viewport-wide rather than component-aware. |
adapt-to-the-form-factorinput-modality-aware | issues | high | At 360px, the active probe measured 95 of 100 visible links/controls below 44px in at least one dimension, including 15px-tall hub links and 18px search buttons. Keyboard focus was visible, but touch sizing was not adequate. F08 high: Most sampled interactive targets are smaller than the recommended touch target. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Screenshots show explicit page purposes and relevant actions: Find Hubs/People, search discussions, Browse Workshops, Market search, and sign in. |
support-core-task-successprimary-flow-completion | pass | medium | Unauthenticated browse flows completed through homepage, discussions, Workshop, Market, app hub and login using crawlable navigation; account-required actions are clearly labeled. |
support-core-task-successclear-system-state-and-recovery | issues | high | Navigating to a deliberately invalid path ended at https://steamcommunity.com/ with no 404 explanation, preserved path, or recovery message. F09 medium: Invalid routes fail silently by redirecting to the homepage. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 13.6s, FCP 8.3s, CLS 0.391, Speed Index 11.5s, and performance 0.33; the CDP trace corroborated LCP 12.7s. F10 high: Load performance is far outside good Core Web Vitals ranges. |
be-fast-and-stablevisual-stability | issues | high | The layout observer recorded CLS 0.421, including a 0.403 shift, while 84 of 99 images lacked explicit dimensions. F11 high: The mobile feed has severe cumulative layout shift. |
be-fast-and-stableefficient-main-thread | pass | medium | Trace found one 105ms long task and 55ms total blocking time; scripting is not the dominant observed bottleneck compared with network/LCP. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 115 requests and 5.88MB transferred, with 15 parser-inserted high-priority stylesheets; images contributed 4.57MB. Confirmed stylesheets are linked from the document head. F12 high: The critical delivery path is heavy and highly render-blocking. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,111KiB unused JavaScript and 105KiB unused CSS; the HAR includes 28 scripts totaling about 996KB transferred. F13 medium: The page ships substantial unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed image-alt (92 nodes), label (2 controls), link-name (24 links), and select-name; the image probe found 95 of 99 images without alt. F14 high: Core images, search fields, and links lack accessible names or labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reported 3.36:1 search-field text and 3.1:1 card link text against dark backgrounds, below WCAG AA for normal text. F15 medium: Important text and search controls have insufficient contrast. |
be-inclusivestructure-and-focus | issues | high | The homepage has no headings, Workshop has no h1-h3, and the app hub starts at h3; landmarks exist and sampled keyboard focus is visible. F16 medium: Heading structure is missing or inconsistent on major templates. |
be-inclusivelegible-text | pass | medium | Desktop/mobile screenshots show readable line lengths and no clipping or horizontal overflow; contrast exceptions are recorded separately. |
be-inclusivezoom-reflow-targets-and-media | pass | medium | Viewport permits normal scaling and 360px reflow has no horizontal overflow; no autoplay video/audio was present on the sampled first viewport. Touch-size failures are recorded under input modality. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured repeated console.error messages: “Missing config element # application_config” from community/main.js. F17 low: Production JavaScript logs repeated console errors. |
follow-best-practicessound-document-and-assets | issues | high | Although doctype/UTF-8 are valid, 84 of 99 images lacked width/height and 14 were oversized; this aligns with observed layout shift. F18 medium: Image sizing and asset markup are not robust. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports a deprecated unload listener in prototype-1.7.js, a known BFCache blocker pattern. F19 medium: Legacy runtime behavior blocks modern browser lifecycle features. |
be-discoverabletitle-and-description | issues | high | Direct DOM probes found no meta description on the homepage, discussions, workshop, market, app hub, or login; titles are present and unique on interior templates. F20 medium: Representative pages lack descriptive meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Discoverability measured only 10% rendered-word coverage in raw HTML; Lighthouse failed crawlable-anchors with 30 nodes and link-name with 24. F21 high: Most dynamic community content is unavailable to non-JavaScript crawlers, and many links are not crawlable/named cleanly. |
be-discoverablecanonical-and-indexing-signals | issues | high | The homepage and representative templates expose no canonical link; /sitemap.xml redirects to the homepage rather than returning a sitemap, while robots.txt otherwise allows public sections. F22 medium: Canonical and sitemap signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | medium | The homepage has Open Graph metadata but zero JSON-LD blocks; game/app and market templates expose rich entities that could be described without changing visible content. F23 low: Rich community entities lack structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | The page is HTTPS, but the headers probe found no CSP, HSTS, nosniff, frame protection, Referrer-Policy, or Permissions-Policy. The timezoneOffset cookie is not Secure, and sessionid is not HttpOnly; all three cookies report SameSite=None. F24 high: Security headers and cookie attributes are below a safe baseline. |
be-private-and-securedata-minimisation-and-third-parties | pass | medium | Tracker probe found no known analytics/tracker domains and secrets scan found no exposed credential; third-party origins are Steam CDNs/user media rather than observed behavioral trackers. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login probe found no WebAuthn/passkey usage. Username/password fields have labels but empty autocomplete attributes. No permission prompt fired on load. F25 medium: Authentication is password/QR-only and omits passkeys and autofill tokens. |
be-private-and-securedefensive-browser-policies | issues | high | The main response lacks HSTS, clickjacking protection, Referrer-Policy, Permissions-Policy, and CSP; no frame-ancestors policy is available as a fallback. F26 high: Browser-enforced defenses are absent. |
be-resilientprogressive-enhancement | issues | high | Raw HTML includes only 10% of rendered content words. The crawler screenshot contains far less community content than the browser view, though the page is not an empty shell. F27 high: Primary feed content depends heavily on JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | Representative menus, listings and app/detail templates rendered without clipped overlays or blank runtime states; all sampled requests returned 200 in HAR. |
be-resilientoffline-and-installable | issues | medium | The homepage probe found no web app manifest, and recon exposed no service-worker-backed offline fallback. F28 medium: The app-like community surface has no install/offline foundation. |
be-resilientnetwork-and-http-failure-states | issues | high | A nonexistent route silently redirected to the normal homepage with no error, retry, explanation, or correct visible state. F29 medium: HTTP failure handling is misleading. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | Document declares lang=en, exposes an extensive locale selector, and the Japanese mobile route reflowed without clipping. |
be-internationalisedlocale-aware-data | pass | medium | The locale parameter rendered a translated Japanese interface and dynamic counts/timestamps remained integrated in the localized layout. |
be-internationalisedtime-zone-correctness | pass | medium | The site sets a timezoneOffset cookie and presents relative activity times, avoiding ambiguous wall-clock timestamps on the sampled public surfaces. |
be-trustworthyno-dark-patterns | pass | medium | Consent presents equally available Accept All and Reject All actions and persistent cookie/privacy links; sampled browse and market pages show commitments and account gates plainly. |
be-trustworthyhumane-error-handling | issues | high | After submitting the empty login form, focus moved to the username input but no role=alert or visible error message was present. F30 medium: Empty sign-in submission gives no visible or announced error. |
be-trustworthytrustworthy-input-assistance | issues | high | The username and password inputs have empty autocomplete values despite representing established sign-in concepts. F31 medium: Sign-in fields do not advertise browser autofill semantics. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | Market prices and the login requirement are visible before gated actions; sign-in offers recovery and QR sign-in. Passkey/autofill shortcomings are recorded in dedicated checks. |
be-sustainableoptimised-assets | issues | high | HAR attributes 4.57MB of 5.88MB to 66 images; the image probe found 84 non-lazy below-fold images, 35 legacy-format images, 21 missing responsive sources, and a 1.07MB top image. F32 high: The feed transfers an excessive and poorly optimized image payload. |
be-sustainableno-wasteful-work | pass | medium | HAR observed only two XHR/fetch requests and trace TBT was 55ms; no continuous autoplay/background processing was observed. |
be-sustainablethird-party-and-media-budget | issues | high | 111 of 115 requests and 5.81MB are classified as third-party origins (mostly Steam CDNs/user content), with user images dominating bytes; these are operational CDNs rather than known trackers but still consume the initial budget. F33 medium: Media/CDN delivery dominates initial resource use. |
be-agent-readystructured-agent-capabilities | not-applicable | medium | No WebMCP, agentic workflow, or on-device-inference intent is declared or visible for this public community browsing audit. |
be-agent-readyon-device-inference | not-applicable | medium | No WebMCP, agentic workflow, or on-device-inference intent is declared or visible for this public community browsing audit. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten repeated feed scroll cycles, heap self size was 30.16MB versus 30.11MB baseline (+0.17%) and node count +0.26%, consistent with bounded noise rather than unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | medium | Heap summary measured about 30.1MB self size for a media-rich feed; the footprint remained proportionate and stable across the repeated-interaction sample. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Before/after heap summaries contain no Detached* constructor signature and show negligible aggregate growth after repeated scrolling. |
Provenance
Canonical report: results/atomic/reports/0301-steamcommunity_com.json
Report SHA-256: 18f3e5df63c7e1622c3bc10426aac61c2483e2e28f1be9762a2de60ea3cfb2b4
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/steamcommunity_com/2026-07-19T19-40-57-048Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/steamcommunity_com/2026-07-19T19-40-57-048Z
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.