Manifest position 329 · CrUX rank bucket 1000
https://support.microsoft.com
Coverage complete
Atomic coverage complete across five representative paths. Excluded: authenticated account completion, purchase flows, and every locale/article instance; representative public templates were sampled instead.
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-mode screenshot remains white, and the computed probe reports color-scheme: normal with no dark surface retint. F1 medium: The site does not honor the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | medium | Under prefers-reduced-motion: reduce the animation probe found zero active animations. |
respect-user-preferencesrespects-contrast | pass | medium | Lighthouse color-contrast passed and essential controls remained legible in all captured templates. |
implement-natural-interactionsview-transitions | issues | medium | The CSS feature probe found no view-transition rules across the landing template, section, search, or article navigation surfaces. F2 low: Page and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | medium | No scroll-linked animation exists, so no main-thread scroll-handler anti-pattern was observed. |
implement-natural-interactionsphysical-gestures | pass | medium | No custom swipe, pull, parallax, or pointer-driven gesture was present on the audited templates. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | Landing and article captures show long documents while the feature probe found no scroll timeline/container behavior or progress affordance. F3 low: Long pages provide static rather than scroll-state-aware navigation chrome. |
provide-guided-navigationanchored-positioning | pass | medium | The only visible callout remained attached to the sign-in control within the desktop viewport; no clipped overlay was observed. |
provide-guided-navigationdirects-attention | pass | medium | Screenshots show clear heading hierarchy, product grouping, article sections, descriptive result links, and a visible not-found recovery search. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop landing and Windows section screenshots show a 260px sign-in callout covering the upper-right content before user interaction. F4 medium: A sign-in teaching callout opens on load and obscures page content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Recon found zero dialog, popover, or details elements while the visible teaching callout is represented by #smcTeachingCalloutPopover and a javascript:void(0) dismiss anchor. F5 low: The teaching callout is an ad-hoc div/link overlay rather than a semantic popover. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Mobile and article screenshots devote the viewport primarily to content with restrained borders and navigation. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | At 360x800 the layout primitive measured scrollWidth 360, clientWidth 360, and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The page adapts at 360px without overflow, but the CSS probe found zero @container rules across reused card/navigation components. F6 low: Responsive behavior is viewport-based, with no component container queries detected. |
adapt-to-the-form-factorinput-modality-aware | pass | medium | Focus probe showed visible outlines on sampled controls and primary product targets were 48px or larger. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Landing, section, article, search, and 404 screenshots clearly state purpose and expose the next action. |
support-core-task-successprimary-flow-completion | pass | medium | The support search flow completed via GET query=wifi and returned ten descriptive result links plus pagination. |
support-core-task-successclear-system-state-and-recovery | pass | medium | The unknown-route capture displays “Sorry, page not found” and an actionable support search field. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.2s and FCP 3.0s; the CDP trace corroborated LCP/FCP at 2.22s under a separate run. F7 medium: Cold-load LCP is outside the good Core Web Vitals range. |
be-fast-and-stablevisual-stability | pass | medium | Mobile layout observer measured CLS 0.0103 with no horizontal overflow, within the good range. |
be-fast-and-stableefficient-main-thread | pass | medium | Trace recorded one 69.68ms long task and only 19.68ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 2.24MB across 68 requests, including 1.59MB images and eight parser-inserted high-priority stylesheets; Lighthouse estimated 940ms render-blocking and 1,632KiB cache-lifetime savings. F8 high: Resource delivery is image-heavy and contains a long render-blocking chain. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse duplicated-javascript insight estimated 6KiB savings, alongside 14 scripts and 313KB transferred script bytes in the HAR. F9 low: The landing page ships avoidable duplicate JavaScript. |
be-inclusivenames-roles-labels | pass | medium | Lighthouse accessibility scored 0.96; image-alt passed and search/feedback controls exposed names or associated labels. |
be-inclusivesufficient-contrast | pass | medium | Lighthouse color-contrast audit passed. |
be-inclusivestructure-and-focus | issues | high | Lighthouse and the focus probe found five positive tabindex values (1,2,4,5,6); search recon found zero h1 elements despite a full results page. F10 high: Focus order is manually reordered, and the search results template has no h1. |
be-inclusivelegible-text | pass | medium | Mobile landing, search, and article captures show readable 16px body text, comfortable line lengths, and no clipping. |
be-inclusivezoom-reflow-targets-and-media | pass | medium | Viewport meta is present and 360px captures reflow without horizontal overflow; no required video/audio media appears on tested templates. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse errors-in-console audit passed with no logged browser errors. |
follow-best-practicessound-document-and-assets | issues | high | The image probe found all 46 images missing width/height, 12 missing srcset, eight oversized, and 46 legacy-format assets; Lighthouse also flagged 46 unsized and nine low-resolution images. F11 medium: Images omit intrinsic dimensions and are delivered with poor responsive sizing. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse traced an unload listener in the analytics bundle and reported BFCache failure UnloadHandlerExistsInMainFrame. F12 medium: A deprecated unload listener prevents back/forward cache restoration. |
be-discoverabletitle-and-description | pass | medium | Homepage and article expose descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse crawlable-anchors identified the skip-to-main and callout dismiss anchors; recon confirms the skip link href is javascript:void(0). F13 medium: Two controls are implemented as javascript:void(0) anchors, including the skip link. |
be-discoverablecanonical-and-indexing-signals | pass | medium | Homepage/article returned 200, expose canonical URLs, robots.txt is valid, and robots.txt advertises two sitemap indexes. |
be-discoverablestructured-and-shareable-metadata | issues | high | Article metadata probe found zero JSON-LD blocks and no hreflang links, although the content has a canonical URL and localized site architecture. F14 low: The representative article lacks structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show CSP 'frame-ancestors self' and HSTS, but no script/style/default-src policy, no X-Content-Type-Options, Referrer-Policy, or Permissions-Policy. F15 high: The CSP only restricts framing and omits core XSS defenses. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe found seven third-party origins; HAR recorded 16 third-party requests and 181,561 bytes; Lighthouse found nine third-party cookies and the cookie probe found five SameSite=None cookies. F16 medium: The anonymous landing load has a broad telemetry and cookie footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No permission prompt appeared on load; sign-in is delegated through Microsoft OIDC rather than a page-local password form. |
be-private-and-securedefensive-browser-policies | issues | high | Headers show CSP 'frame-ancestors self' and HSTS, but no script/style/default-src policy, no X-Content-Type-Options, Referrer-Policy, or Permissions-Policy. F15 high: The CSP only restricts framing and omits core XSS defenses. |
be-resilientprogressive-enhancement | pass | medium | Discoverability captures show 100% content visibility without JavaScript on landing and article templates. |
be-resilientresilient-runtime-behaviour | pass | medium | Landing, section, search, and article templates rendered stable content and the visible callout stayed within viewport bounds. |
be-resilientoffline-and-installable | not-applicable | high | This public support content site is primarily document/search delivery rather than an installable app; offline installability was judged out of scope. |
be-resilientnetwork-and-http-failure-states | pass | medium | The representative unknown URL displays a useful not-found state with recovery search instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | medium | The article correctly declares en-US/ltr, but the stylesheet probe counted 263 physical-direction rules versus seven logical-property rules and no hreflang metadata. F17 medium: Localized pages remain heavily dependent on physical-direction CSS and expose no hreflang links. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited support templates contain no user-facing dates, currencies, durations, or numeric data requiring locale formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited templates expose no scheduling or time-zone-sensitive data. |
be-trustworthyno-dark-patterns | pass | medium | No pricing, forced continuity, confirmshaming, or disguised advertising was observed; the sign-in callout is dismissible. |
be-trustworthyhumane-error-handling | pass | medium | Search accepts a non-destructive GET query and the 404 state gives neutral, actionable recovery language. |
be-trustworthytrustworthy-input-assistance | pass | medium | Search controls use native type=search with clear names; no address/payment/profile data is requested on audited paths. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | No checkout/subscription flow exists on tested support templates; account sign-in is clearly labeled and delegated to Microsoft identity. |
be-sustainableoptimised-assets | issues | high | Images account for 1.59MB; 35 below-fold images are not lazy-loaded, all 46 are legacy PNG/JPG, 12 lack srcset, and eight are oversized. F18 high: Below-fold imagery is not optimized for transfer or viewport need. |
be-sustainableno-wasteful-work | issues | high | HAR totals 68 requests and 2.24MB while the first viewport is mostly headings and product links; 35 below-fold images load eagerly and telemetry contacts browser.events.data.microsoft.com. F19 medium: The landing page eagerly fetches content and telemetry that is not needed in the first viewport. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties transfer 181,561 bytes and images transfer 1.59MB on a page whose core task is navigating text links or searching. F20 medium: Third-party and image transfer is disproportionate to a text-first support landing page. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No transactional agent-facing capability is needed for these public support-document templates; semantic crawlable content is the relevant surface. |
be-agent-readyon-device-inference | not-applicable | high | On-device inference is not necessary to complete the tested support search and article-reading tasks. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten full-page scroll cycles, heap self-size grew only 142,836 bytes (1.2%) and node count 823 (0.4%), with no unbounded-growth signal. |
be-memory-efficientbounded-footprint | pass | medium | Baseline heap was 11,996,995 self-size bytes for 198,515 nodes, proportionate to the content-rich landing page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Baseline/post summaries show stable native counts (97,978 to 97,986) and no Detached* constructor population among top retained constructors. |
Provenance
Canonical report: results/atomic/reports/0329-support_microsoft_com.json
Report SHA-256: a5221b92e71729601ce33cbbb77f483c3f06bba54afc013ac9e1c9599d574b35
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/support_microsoft_com/2026-07-19T23-48-01-244Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/support_microsoft_com/2026-07-19T23-48-01-244Z
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.