Manifest position 242 · CrUX rank bucket 1000
https://apps.apple.com
Coverage complete
Coverage complete: all 58 catalog checks received conclusive outcomes.
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 | pass | high | The light screenshot uses light system surfaces while the default dark capture uses dark surfaces; rendered CSS declares color-scheme: light dark and system color tokens. |
respect-user-preferencesrespects-reduced-motion | pass | high | The emulated preference matched, no active animations remained, and five reduced-motion media rules were present. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse color-contrast passed and the prefers-contrast: more screenshot retained legible text, icons and controls. |
implement-natural-interactionsview-transitions | issues | medium | Representative route loads changed immediately and authored CSS exposed only short opacity transitions; no View Transition API or ::view-transition integration was found for route continuity. F-012 low: Route changes lack continuity cues |
implement-natural-interactionsscroll-driven-animations | pass | medium | Long content shelves use native overflow/scroll presentation; inspection found no continuous script-driven scroll animation and the trace showed only three bounded long tasks. |
implement-natural-interactionsphysical-gestures | pass | medium | Horizontal shelves and mobile navigation use native scrolling/touch surfaces with no evidence of pointermove-based gesture reimplementation. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | Desktop keeps a stable side rail while mobile collapses it to a compact header, preserving content space and orientation without intrusive floating chrome. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, context-menu, or edge-sensitive anchored overlay was required in the exercised catalog, detail, editorial, or discovery flow. |
provide-guided-navigationdirects-attention | pass | high | Each template uses a single H1, prominent hero or app identity, selected navigation state, and clear View links to direct attention. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No consent wall, modal, newsletter prompt, or full-viewport interruption obscured content on load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | medium | The rendered DOM exposed dialog/role-dialog surfaces rather than an unlabelled full-screen interruption; no forced overlay appeared during the exercised flow. |
maximize-content-reduce-noisereduced-chrome | pass | high | The compact side rail becomes a 44px mobile header; the rest of the viewport is devoted to catalog content and primary details. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Home and story reported zero overflow; listing and detail reported only a 2px viewport-rounding delta, with no visible clipped content in mobile captures. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | The live stylesheet contained 30 @container rules and cards/navigation visibly reflowed between 780px and 360px. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The first 20 focusable controls reported outline-style none, including search and primary navigation links, so keyboard focus lacks a dependable visible indicator. F-005 high: Keyboard focus is not visibly indicated |
support-core-task-successclear-purpose-and-primary-action | pass | high | Today, Apps, story and app-detail templates state their purpose immediately and expose direct View/detail links with clear hierarchy. |
support-core-task-successprimary-flow-completion | pass | high | Prominent href-backed cards and navigation reached rendered listing, story and Roblox detail templates without authentication or dead ends. |
support-core-task-successclear-system-state-and-recovery | issues | high | The 404 state says only “The page you’re looking for can’t be found” and offers no contextual recovery action in the content pane. F-011 low: The not-found state has no recovery action |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 12.5s, FCP 5.8s and TBT 262ms (performance 0.52); the trace still measured LCP 2.71s and 137ms TBT under a lighter run, so load performance is condition-sensitive and fails the lab mobile bar. F-001 high: Slow mobile rendering delays the catalog |
be-fast-and-stablevisual-stability | pass | high | All representative layout captures and Lighthouse reported CLS 0 with dimensions reserved. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 4.4s main-thread work, 2.1s JavaScript execution and 262ms TBT; the trace recorded three long tasks and 137ms TBT. F-002 high: Main-thread and unused-code costs are substantial |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded a redirect, parser-inserted high-priority stylesheets and 1.66MB initial transfer; Lighthouse found 30,047KiB total payload, 750ms render-blocking savings and 480ms document-latency savings. The parser script is type=module and was not treated as blocking. F-003 high: Trailer delivery creates an excessive mobile payload |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 642KiB unused JavaScript (including 75.8% of the 622KiB main bundle) and 37KiB unused CSS (78.1% of the stylesheet). F-002 high: Main-thread and unused-code costs are substantial |
be-inclusivenames-roles-labels | issues | high | Lighthouse found focusable descendants inside aria-hidden navigation and multiple cards whose visible label text did not match the accessible name. F-004 high: Hidden mobile navigation remains keyboard-focusable F-014 medium: Card accessible names do not include visible labels |
be-inclusivesufficient-contrast | pass | high | Lighthouse reported no color-contrast failures on the audited mobile surface. |
be-inclusivestructure-and-focus | issues | high | Lighthouse found H1-to-H3 heading skips, and the focus probe found outline-style none on search and navigation controls. F-005 high: Keyboard focus is not visibly indicated |
be-inclusivelegible-text | pass | high | Body, heading, rating and metadata text remained readable with clear hierarchy and sensible line lengths across representative templates. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Mobile layouts reflowed without meaningful overflow, but Lighthouse found footer language links only 10px high with insufficient spacing. F-006 medium: Footer locale links have undersized touch targets |
follow-best-practicesno-console-errors | pass | high | Lighthouse reported no browser console errors during page load. |
follow-best-practicessound-document-and-assets | pass | high | The document has an HTML doctype, UTF-8 charset and viewport; Lighthouse passed responsive image sizing/aspect ratio and the layout observer reported CLS 0. |
follow-best-practicesbrowser-platform-hygiene | issues | medium | The best-practices category scored 1.0, but Lighthouse separately reported missing source maps for large first-party JavaScript, limiting production diagnostics. F-013 low: Production JavaScript lacks source maps |
be-discoverabletitle-and-description | issues | high | The homepage has a descriptive title but no meta description; Lighthouse failed the meta-description audit. F-007 medium: Homepage search and share metadata is incomplete |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Raw HTML retained 98% of rendered content, anchors have real hrefs, the viewport meta is present, and robots.txt permits public catalog paths. |
be-discoverablecanonical-and-indexing-signals | issues | high | The homepage returned 200 and robots.txt points to six sitemap indexes, but the page has no canonical link or hreflang signals despite locale/storefront variants. F-008 medium: Canonical and locale indexing signals are absent |
be-discoverablestructured-and-shareable-metadata | issues | high | The homepage exposed no JSON-LD and no Open Graph metadata, leaving catalog/editorial content without machine-readable or social-preview context. F-007 medium: Homepage search and share metadata is incomplete |
be-private-and-securesecure-transport-and-headers | pass | high | HTTPS, HSTS, CSP, nosniff and frame denial are present; the secrets scan found no exposed sensitive credentials. |
be-private-and-securedata-minimisation-and-third-parties | pass | medium | No known tracker domains were detected; cross-origin requests were confined to Apple/mzstatic delivery, media and telemetry origins, with no third-party cookies. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No permission request, sign-in, registration, or authentication surface appeared in the public browse/detail journeys tested. |
be-private-and-securedefensive-browser-policies | issues | high | Referrer-Policy and Permissions-Policy headers were absent, CSP permits unsafe-inline styles, and the geo cookie was set without Secure and with SameSite=None. F-009 medium: Defensive policies and the geo cookie need tightening |
be-resilientprogressive-enhancement | pass | high | Raw server HTML returned 200 and retained 98% of rendered content, including title and H1; the crawler screenshot remained useful. |
be-resilientresilient-runtime-behaviour | pass | medium | Listing, detail, editorial and invalid routes all rendered stable states without uncaught console errors or broken navigation chrome. |
be-resilientoffline-and-installable | issues | high | A standalone manifest exists, but it has no start_url and the live page had zero service-worker registrations, so offline/installable behavior is incomplete. F-010 medium: The PWA manifest does not provide offline behavior |
be-resilientnetwork-and-http-failure-states | issues | high | The not-found route presents a clear message but no retry, home link, search prompt, or other recovery control in the main state. F-011 low: The not-found state has no recovery action |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=en-US and dir=ltr; CSS uses start-aligned declarations and the footer exposes multiple locale links. |
be-internationalisedlocale-aware-data | pass | medium | The storefront identifies en-US and provides explicit localized page links including Arabic, Korean, French, Portuguese and Chinese variants. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative catalog, app-detail and editorial surfaces contained no user-entered or scheduled date/time workflow requiring time-zone conversion. |
be-trustworthyno-dark-patterns | pass | high | No consent manipulation, forced signup, disguised advertisement, confirmshaming, or obstructed cancellation appeared in the public flows. |
be-trustworthyhumane-error-handling | not-applicable | high | The only form is catalog search; there is no required multi-field data-entry submission for which validation timing or aria-invalid behavior applies. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No sign-in, address, payment, or account fields appeared; search intentionally uses autocomplete=off and does not collect identity data. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Web browsing exposes product information and external View actions, but no checkout, subscription, account, or reauthentication flow was available on the audited site. |
be-sustainableoptimised-assets | pass | medium | Rendered delivery used appropriately sized WebP artwork in the HAR; Lighthouse passed image sizing/aspect ratio and estimated a comparatively small 157KiB image opportunity. |
be-sustainableno-wasteful-work | issues | high | The mobile load fetched or discovered many high-resolution trailer variants; Lighthouse attributed roughly 30MB largely to 1.3–4.8MB video files despite a browse-first task. F-003 high: Trailer delivery creates an excessive mobile payload |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 47 cross-origin requests and 723KB initial cross-origin transfer; Lighthouse’s fuller run reached 30,047KiB, dominated by Apple trailer media variants. F-003 high: Trailer delivery creates an excessive mobile payload |
be-agent-readystructured-agent-capabilities | not-applicable | high | This is a public browse/catalog surface with no declared agent action workflow; lack of WebMCP tools is not treated as a defect for the audited intent. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or other inference feature is part of the public App Store web journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten repeated country-control open/dismiss attempts, heap self size decreased from 36,274,590 to 36,266,169 bytes; node count rose only 1,023 (0.17%), with no retained-size growth signal. |
be-memory-efficientbounded-footprint | pass | medium | The loaded content-rich catalog retained a 36.3MB self-size heap; this is bounded and proportionate to the large rendered catalog, though network/code costs remain separate findings. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The repeated interaction produced no material total retained-size growth; constructor summaries showed no growing Detached* population among dominant constructors. |
Provenance
Canonical report: results/atomic/reports/0242-apps_apple_com.json
Report SHA-256: a5076447283a752d0d4ddb30cdc180088325873e7728d1f4805cf6ccb31bf55e
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/apps_apple_com/2026-07-19T09-41-32-902Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/apps_apple_com/2026-07-19T09-41-32-902Z
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.