Manifest position 680 · CrUX rank bucket 1000
https://search.yahoo.com
Coverage complete
Atomic coverage complete. The external web and image result backends returned failure/empty states during the run; those observed states are reported as findings rather than blockers because the templates remained inspectable.
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 | Dark emulation leaves all principal surfaces white and no preference-aware theme CSS is present F001 medium: The search experience ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | prefers-reduced-motion: reduce matched and zero active animations were present on the inspected landing state |
respect-user-preferencesrespects-contrast | pass | high | Controls, text, focus, and search affordances remained visible under forced colors; Lighthouse contrast audit passed |
implement-natural-interactionsview-transitions | issues | high | Search submission performs an abrupt document swap and no view-transition CSS was found F002 low: Search navigation swaps abruptly instead of preserving spatial continuity. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, carousel, or scroll-linked motion exists on the representative surfaces, so there is no scroll animation to implement or evaluate. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The inspected search, retry, tab, and sign-in surfaces expose no swipe, pull, snap, or gesture-driven interaction requiring physical gesture treatment. |
provide-guided-navigationscroll-state-aware-chrome | not-applicable | high | The representative search utility states do not use persistent scroll chrome or a long-form reading journey where scroll-state feedback would add orientation. |
provide-guided-navigationanchored-positioning | issues | high | The apps overlay is a plain div with no popover or CSS anchor positioning F003 low: The apps menu is not implemented as an anchored, self-repositioning overlay. |
provide-guided-navigationdirects-attention | pass | high | The active Images tab is clearly highlighted and both failure states place retry/suggestion actions next to the status message |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No load-time popup, interstitial, or content-obscuring banner appeared on landing, results, image results, or sign-in |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The transient apps overlay uses a role-less div and no popover/dialog/details primitives were present F004 low: Transient menu UI uses an ad-hoc div instead of the platform popover primitive. |
maximize-content-reduce-noisereduced-chrome | pass | high | The landing prioritises the search field and results states contain little non-content chrome |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Landing lacks viewport meta; web results overflow 920px and image results 441px F005 high: The primary search and result templates do not reflow for a 360px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No container queries were found and shared result/navigation shells stay desktop-wide on mobile F006 medium: Shared result components do not adapt to their available container. |
adapt-to-the-form-factorinput-modality-aware | pass | high | Touch target audit passed and keyboard focus on the first control has a visible 1px auto outline |
support-core-task-successclear-purpose-and-primary-action | pass | high | Yahoo branding, “Search the web” input, and Search action make the primary purpose immediately clear |
support-core-task-successprimary-flow-completion | issues | high | The submitted broad query did not return web results and the image archetype also returned no results F007 critical: The core search task could not return web or image results. |
support-core-task-successclear-system-state-and-recovery | pass | high | Both failures state what happened and offer retry/new-query guidance; image results add concrete search suggestions |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse LCP is 9.8s although the unthrottled trace LCP is 1.28s; constrained mobile load misses the good range F008 high: Throttled mobile loading misses the LCP good range. |
be-fast-and-stablevisual-stability | pass | high | Landing CLS was approximately 0.000002 and Lighthouse CLS was 0; result templates also reported CLS 0 |
be-fast-and-stableefficient-main-thread | pass | high | Raw trace recorded no long tasks and TBT 0ms; Lighthouse TBT was 59ms, within the good range |
be-fast-and-stableefficient-resource-delivery | issues | high | Initial delivery is 1.36MB, including four eager voice WAV files totalling about 505KB F009 medium: The sparse landing page transfers 1.36MB, including 505KB of voice audio before the feature is used. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Estimated savings are 409KiB unused JavaScript and 39KiB unused CSS F010 medium: Large portions of consent, analytics, and mobile CSS are unused at load. |
be-inclusivenames-roles-labels | issues | high | Two mobile icon links lack discernible names and the web-results query input has no label F011 medium: Some primary controls lack accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color contrast passed and essential UI remained visible in forced-colors mode |
be-inclusivestructure-and-focus | issues | high | No main landmark exists and heading order starts at h3 then h4; focus itself remains visible F012 medium: The landing page lacks a main landmark and starts its visible heading hierarchy at h3. |
be-inclusivelegible-text | issues | high | Text becomes tiny on the scaled landing and clipped on both result templates at mobile width F013 medium: Mobile scaling and clipping make text difficult to read. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Touch targets pass and no captioned media is needed, but landing omits viewport meta and result templates fail reflow F005 high: The primary search and result templates do not reflow for a 360px viewport. |
follow-best-practicesno-console-errors | issues | high | A client request to acapi.yahoo.com/v1/sync returns 404 and is logged as a browser error F014 low: The page logs a failed network resource to the browser console. |
follow-best-practicessound-document-and-assets | pass | high | HTML doctype and UTF-8 are valid; all six landing images have alt and dimensions and aspect/resolution audits passed |
follow-best-practicesbrowser-platform-hygiene | pass | high | BFCache passes, paste is allowed, no geolocation/notification prompt occurs on load, and no deprecated API failure was reported |
be-discoverabletitle-and-description | issues | high | Result templates have descriptive titles but no meta description; Lighthouse also saw no description in its mobile landing variant F015 medium: Result templates omit a meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Links and robots syntax pass, but all inspected templates fail mobile friendliness through scaling or horizontal overflow F005 high: The primary search and result templates do not reflow for a 360px viewport. |
be-discoverablecanonical-and-indexing-signals | pass | high | Landing returns 200 to the discoverability fetch, is indexable, and robots.txt deliberately excludes query-result routes; no accidental noindex was observed |
be-discoverablestructured-and-shareable-metadata | not-applicable | high | The audited surfaces are a generic search utility and transient query/error states, not an article, product, organization, event, place, or other rich entity requiring entity structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS are present, but CSP permits unsafe-inline/unsafe-eval and two cookies lack Secure F016 high: Cookie and CSP settings weaken an otherwise HTTPS-protected page. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | 22/27 requests and 1.316MB/1.363MB transferred bytes are third-party; Google Tag Manager is active F017 medium: Third-party delivery and tracking dominate the landing load. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No permission prompt fires on load, but the relevant sign-in surface exposes no passkey/WebAuthn option F018 medium: The linked sign-in flow does not expose phishing-resistant passkey authentication. |
be-private-and-securedefensive-browser-policies | issues | high | Permissions-Policy is missing; CSP contains unsafe directives and broad object/connect/media sources F019 medium: Defensive browser policy coverage is incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability reports 100% rendered-word coverage from raw HTML, not a JS shell; crawler view retains the core search content |
be-resilientresilient-runtime-behaviour | pass | high | Simple search and recovery controls render without clipped overlays at desktop; no fragile async shell or initial visibility flicker was observed |
be-resilientoffline-and-installable | not-applicable | high | Search results inherently require a live index/network. No installable intent is declared, so an offline/PWA experience is not expected for this public search utility. |
be-resilientnetwork-and-http-failure-states | pass | high | Backend/result failures produce explicit messages, retry/new-query actions, and suggestions rather than blank shells or infinite spinners |
be-internationalisedlang-dir-and-logical-properties | issues | high | lang=en-US is correct, but no logical properties were detected and physical left/right positioning dominates F020 medium: The CSS is built around physical left/right positioning rather than writing-mode-safe logical properties. |
be-internationalisedlocale-aware-data | not-applicable | high | Representative surfaces display no dates, numbers, currencies, durations, or calendar values whose locale formatting can be judged. |
be-internationalisedtime-zone-correctness | not-applicable | high | Representative search, error, and sign-in states contain no event times, recurring intervals, or stored temporal concepts. |
be-trustworthyno-dark-patterns | pass | high | No confirmshaming, disguised ads, consent wall, hidden price, or forced continuity was observed; “Stay signed in” is visible and reversible |
be-trustworthyhumane-error-handling | not-applicable | high | The primary search accepts free text and has no invalid-input state; the linked username step was not submitted with personal data, so no representative validation-error state was available to exercise. |
be-trustworthytrustworthy-input-assistance | issues | high | The username/email/phone field has a visible label but an empty autocomplete attribute F021 medium: The username field does not advertise the autocomplete token browsers need. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Sign-in is clear and reversible but does not offer a phishing-resistant passkey route on the inspected entry screen F018 medium: The linked sign-in flow does not expose phishing-resistant passkey authentication. |
be-sustainableoptimised-assets | pass | high | All six landing images have dimensions and alt; none are oversized, and Lighthouse aspect/resolution audits pass |
be-sustainableno-wasteful-work | issues | high | Voice media is fetched before intent and hundreds of KiB of shipped JS are unused at load F022 medium: Nonessential scripts and audio are fetched before user intent. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 96.6% of transferred bytes and nonessential media/scripts dominate a sparse search landing page F017 medium: Third-party delivery and tracking dominate the landing load. F022 medium: Nonessential scripts and audio are fetched before user intent. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The site exposes no declared agent-facing task surface and robots.txt explicitly disallows major AI agents; this is an intentional crawler posture, not a missing WebMCP obligation. |
be-agent-readyon-device-inference | not-applicable | high | No declared summarisation or local-inference feature exists on the inspected search utility, so built-in on-device AI is an opportunity rather than a requirement. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 representative query interactions, nodes rose 0.38% (234,395 to 235,293) and self size 0.59% (14,649,660 to 14,735,491 bytes), with no unbounded pattern in this bounded run |
be-memory-efficientbounded-footprint | pass | high | The landing uses about 14.6MB V8 snapshot self size, 12.5MB live JS heap in the probe, and 302 live DOM elements, proportionate to the page |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appears among top retained constructors and repeated interaction produced only modest bounded node growth; confidence is medium because listener enumeration was unavailable |
Provenance
Canonical report: results/atomic/reports/0680-search_yahoo_com.json
Report SHA-256: 363d2acbe4063096fdd5f93bb2f1ad77037a80baf0c847312f7e3654227f5baa
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/search_yahoo_com/2026-07-22T09-01-15-877Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/search_yahoo_com/2026-07-22T09-01-15-877Z
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.