Manifest position 529 · CrUX rank bucket 1000
https://sellercentral.amazon.com
Coverage complete
Atomic coverage complete across 58 checks and four representative public/auth/localized paths. Account creation beyond the credential boundary and authenticated Seller Central were not covered.
Attempts
2 / 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 pixel-identical to the light capture and the probe reports color-scheme: normal with no prefers-color-scheme or light-dark() CSS. F-001 medium: The public and sign-in surfaces ignore the user’s dark-mode preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation matched successfully and the page reported zero active animations; no auto-advance or nonessential motion was present. |
respect-user-preferencesrespects-contrast | pass | high | The forced-colors screenshot preserves readable text, visible primary controls, and focus/control outlines throughout the first two sections. |
implement-natural-interactionsview-transitions | issues | high | The live CSS probe found no view-transition declarations; the covered route changes and sign-in validation swap state without a View Transition. F-002 low: Navigation and state changes have no transition treatment. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation, parallax, scrollytelling, carousel, or reveal behavior exists on the covered paths. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull, drag, scroll-snap carousel, or other gesture-driven component exists on the covered paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The landing page is over 4,200 CSS px tall, but the CSS probe found no scroll-state query, scroll timeline, or progress treatment for navigation chrome. F-003 low: Long-page navigation does not respond to scroll state. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or viewport-edge floating menu was present in the covered public, sign-in, or onboarding states. |
provide-guided-navigationdirects-attention | pass | high | Desktop, mobile, and signup screenshots show a clear heading hierarchy, strongly differentiated primary action, and labeled navigation destinations. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Fresh-load screenshots on all four paths show no interstitial, consent wall, or overlay obscuring core content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No modal dialog, disclosure, picker, or transient popover was present in the covered states. |
maximize-content-reduce-noisereduced-chrome | pass | high | The public first viewport prioritizes the seller proposition, primary CTA, and supporting image with restrained navigation chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360x800 viewport, layout reports innerWidth 1000 on home and 980 on sign-in, hasViewportMeta false, and Chrome scales the desktop layout to about 0.36, shrinking text and controls. F-004 high: The pages omit the viewport meta tag and render a desktop-sized CSS viewport on phones. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | At a requested 360x800 viewport, layout reports innerWidth 1000 on home and 980 on sign-in, hasViewportMeta false, and Chrome scales the desktop layout to about 0.36, shrinking text and controls. F-004 high: The pages omit the viewport meta tag and render a desktop-sized CSS viewport on phones. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The live probe found visible links only 14–21 CSS px high, and Lighthouse sign-in reports seven target-size failures. F-005 medium: Several controls and links fall below comfortable touch-target dimensions. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The H1 states “Create an Amazon selling account” and prominent Sign up and Log in actions are visible without scrolling. |
support-core-task-successprimary-flow-completion | pass | high | The audited public entry routes predictably to distinct sign-in and start-selling destinations; the credential boundary is expected and no dead end appeared before it. |
support-core-task-successclear-system-state-and-recovery | pass | high | Empty sign-in submission produces explicit alert text, returns focus to ap_email, and offers password/passkey recovery alternatives. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 9.2 s, FCP 4.3 s, Speed Index 7.4 s, and TTI 14.5 s; the independent trace measured LCP 3.27 s and FCP 3.25 s with low TBT, confirming network/LCP rather than sustained main-thread blocking as the main problem. F-006 high: The public landing page loads too slowly for the primary path. |
be-fast-and-stablevisual-stability | pass | high | The mobile layout observer measured CLS 0.022 and Lighthouse measured CLS 0.011, both in the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Trace evidence measured one 74.7 ms long task and 24.7 ms TBT; Lighthouse measured 90 ms TBT, within a good interaction budget. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR records 123 requests and 3.36 MB transferred, including five parser-inserted stylesheets and 1.37 MB across 15 fonts; DOM confirmation shows all five active stylesheets, while most scripts are async but three body scripts are synchronous. F-007 high: Critical delivery is delayed by a large render-blocking and font/image waterfall. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 279 KiB unused JavaScript and 136 KiB unused CSS, while the DOM loads duplicate aos.js and assets-Sell.js URLs in both async head and synchronous body contexts. F-008 medium: The landing page ships substantial unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse reports 43 homepage images without alt text and seven role/ARIA mismatches; the sign-in audit adds an unnamed link and invalid ARIA value. The image primitive counted 93 img elements without alt, including many decorative icons. F-009 high: Image and ARIA semantics are incomplete on primary surfaces. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast passed and forced-colors evidence keeps foreground and controls distinguishable. |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports no main landmark on sign-in. On the landing page the hamburger is a span inside a focusable header rather than a named button, even though visible focus itself is present. F-010 medium: The sign-in template lacks a main landmark and the mobile menu trigger is not a semantic control. |
be-inclusivelegible-text | pass | high | Desktop and localized screenshots show strong typographic hierarchy, readable line lengths, and no clipping in the sampled content. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Both representative sellercentral.com templates omit a viewport declaration, causing 980–1000 CSS px layouts to be downscaled into a 360 px device viewport; Lighthouse also reports seven sign-in touch-target failures. F-011 high: Mobile reflow and zoom start from the wrong viewport. |
follow-best-practicesno-console-errors | pass | high | Lighthouse reported no browser console errors on the public landing page. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive reports 99 of 100 images without width/height attributes and 46 oversized images. Lighthouse reports one deprecated API warning. F-012 medium: Asset sizing and platform hygiene have avoidable defects. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports four BFCache failure reasons on the landing page and two on sign-in, increasing repeat-navigation cost. F-013 medium: Both primary templates are ineligible for the back/forward cache. |
be-discoverabletitle-and-description | issues | high | Lighthouse SEO passes the public homepage title/description but reports that the sign-in document has no meta description. F-014 low: The sign-in archetype has no meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | At a requested 360x800 viewport, layout reports innerWidth 1000 on home and 980 on sign-in, hasViewportMeta false, and Chrome scales the desktop layout to about 0.36, shrinking text and controls. F-004 high: The pages omit the viewport meta tag and render a desktop-sized CSS viewport on phones. |
be-discoverablecanonical-and-indexing-signals | pass | high | The public page returns 200, declares canonical https://sellercentral.amazon.com/, robots allows indexing, and robots.txt/sitemap.xml were successfully retrieved. |
be-discoverablestructured-and-shareable-metadata | issues | high | The metadata probe found Open Graph and Twitter tags but zero JSON-LD or microdata blocks on a public Amazon Seller Central organization/service page. F-015 low: The public organization/commerce landing page has share tags but no structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and HSTS are present, but the header probe found no CSP, Referrer-Policy, or Permissions-Policy. Cookie evidence reports 14 cookies without Secure and auth-like session-id/session-token cookies readable by script and using SameSite=None. F-016 high: Security headers and cookie attributes are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe records 15 third-party origins; the HAR attributes 118 of 123 requests and 3.21 of 3.36 MB to non-sellercentral origins, including Adobe/Demdex and Everest redirects. F-017 high: The public landing page has a large analytics and third-party footprint before user action. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; the sign-in validation exposes passkey handling and alternative password recovery, showing modern authentication support. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS and X-Frame-Options are present, but no CSP/frame-ancestors, Referrer-Policy, or Permissions-Policy was observed; the cookies evidence also shows broad SameSite=None use. F-018 high: Browser-enforced defenses are only partially configured. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 5% raw-to-rendered word coverage and classified the marketing page as a JavaScript shell; the raw HTML has title/description but no H1, while the rendered page has 284 content tokens. F-019 high: The public landing page exposes little meaningful content to non-JavaScript clients. |
be-resilientresilient-runtime-behaviour | pass | high | Repeated full-page scrolling kept DOM nodes stable at 1,410, screenshots showed no clipped initial controls, and form validation retained focus/context. |
be-resilientoffline-and-installable | not-applicable | high | Seller authentication and account creation are intrinsically online, and the public marketing entry is not presented as an installable app. |
be-resilientnetwork-and-http-failure-states | pass | high | The exercised authentication failure state provides explicit, actionable messages, retries/alternatives, and focus recovery rather than a blank or stuck state. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The Spanish variant correctly sets lang=es-ES and renders translated content, but the CSS probe found no logical inline/block properties, reducing resilience for RTL/writing-mode expansion. F-020 low: Locale metadata is correct, but the stylesheet does not use logical properties. |
be-internationalisedlocale-aware-data | pass | high | The Spanish locale renders translated navigation/content and locale-appropriate “50 000 $” formatting with lang=es-ES. |
be-internationalisedtime-zone-correctness | not-applicable | high | The covered public, sign-in, and onboarding surfaces expose no dates, events, schedules, or time-zone-sensitive data. |
be-trustworthyno-dark-patterns | pass | high | Covered screenshots show clearly labeled sign-up/login actions, linked conditions/privacy, visible incentive qualifiers, and no confirmshaming or consent wall. |
be-trustworthyhumane-error-handling | pass | high | Empty sign-in submission announces clear errors and restores focus to the email field; the message asks for correction without blame. |
be-trustworthytrustworthy-input-assistance | issues | high | Lighthouse reports an autocomplete-valid failure on the authentication form, despite this being a high-value sign-in surface. F-021 medium: The sign-in template contains an invalid autocomplete configuration. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The covered onboarding landing clearly distinguishes sign up/log in, shows the incentive qualifier, and provides Pricing navigation before the credential boundary. |
be-sustainableoptimised-assets | issues | high | The image audit reports 46 oversized images, seven legacy-format images, five without responsive sources, and 99 without dimensions; images transfer 1.07 MB on the initial load. F-022 high: The page transfers oversized and weakly constrained media. |
be-sustainableno-wasteful-work | issues | high | The initial load sends analytics requests to Adobe/Demdex, Everest and Amazon telemetry endpoints, while the DOM includes duplicate aos.js and assets-Sell.js loads; this work occurs before a seller chooses an action. F-024 medium: Nonessential background analytics and duplicate resources create avoidable work. |
be-sustainablethird-party-and-media-budget | issues | high | The 3.36 MB load includes 1.37 MB of fonts, 1.07 MB of images, and 3.21 MB attributed to third-party origins; 15 separate fonts and 118 third-party requests dominate the budget. F-023 high: Third-party, font, and media cost is disproportionate for a marketing entry page. |
be-agent-readystructured-agent-capabilities | issues | high | The live probe found no WebMCP or agentic tool registration, and the public content is only 5% present in raw HTML, leaving agents to infer actions from a JS-heavy visual surface. F-025 low: The agent-relevant seller onboarding surface exposes no structured capability contract. |
be-agent-readyon-device-inference | not-applicable | high | The covered marketing and authentication tasks do not contain a summarisation or generative task for which on-device inference would improve the experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten representative full-page scroll cycles, DOM nodes remained exactly 1,410; used JS heap rose only about 0.93 MB during the active sample and a post-interaction heap was within 0.7% of baseline size. |
be-memory-efficientbounded-footprint | pass | high | Heap summaries measured about 23.8–24.0 MB self size and roughly 358k heap nodes, proportionate to the rendered marketing page despite its network weight. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Ten scroll cycles left DOM node count unchanged; closure count changed only 48 and no Detached* constructor appeared among retained top constructors. |
Provenance
Canonical report: results/atomic/reports/0529-sellercentral_amazon_com.json
Report SHA-256: 003d5237977ffaf075456d6e1c2d1a01a18a6a6e81dcb899f3a83c879191e033
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/sellercentral_amazon_com/2026-07-26T14-26-17-298Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/sellercentral_amazon_com/2026-07-26T14-26-17-298Z
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.