Manifest position 1000 · CrUX rank bucket 1000

https://forms.cloud.microsoft

Coverage complete

Coverage-complete audit of the credential-free public route. The supplied URL redirects to the localized Microsoft Forms product landing; authenticated form creation and account surfaces were explicitly outside this run.

Attempts

1 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	The dark-condition screenshot is visually identical to the light capture: white page, white navigation, and light hero remain unchanged. F001 medium: The page does not adapt its light surfaces to the user’s dark colour-scheme preference.
respect-user-preferences `respects-reduced-motion`	pass	high	Computed CSS inspection and reduced-motion emulation found extensive `prefers-reduced-motion` rules and zero active animations under reduce.
respect-user-preferences `respects-contrast`	issues	high	The high-contrast screenshot is entirely blank although the paired probe confirms 3,314+ characters remain in the DOM and `matchMedia("(prefers-contrast: more)")` is true. F002 high: The rendered page disappears under `prefers-contrast: more`.
implement-natural-interactions `view-transitions`	pass	high	CSS inspection found view-transition rules in the delivered styles, providing platform-level transition support where state changes use it.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	No scroll-linked animation is present on this content page, so there is no scroll-handler implementation to judge.
implement-natural-interactions `physical-gestures`	pass	high	CSS inspection found scroll-snap and overscroll-behavior rules for carousel/scroll interactions rather than evidence of custom pointer-loop physics.
provide-guided-navigation `scroll-state-aware-chrome`	pass	high	Desktop capture shows persistent in-page section navigation directly beneath the hero, with stable section anchors for the long page.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No tooltip, transient popover, or edge-positioned menu was exposed in the representative public state.
provide-guided-navigation `directs-attention`	pass	high	Descriptive Overview, Features, Pricing, Resources, Apps, and Next steps anchors map directly to named page sections and maintain orientation.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	At 360×800 the consent block consumes roughly the first 345 px before product navigation and content, delaying the “Microsoft Forms” purpose and primary actions. F003 medium: The optional-cookie banner dominates the initial mobile viewport.
maximize-content-reduce-noise `semantic-dismissible-primitives`	not-applicable	high	The visible consent surface is an inline banner rather than a modal, and no rich overlay requiring dialog/popover/details was present.
maximize-content-reduce-noise `reduced-chrome`	pass	high	After the consent banner, the desktop capture gives the hero and content sections dominant space with restrained navigation chrome.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	At 360×800, layout measured scrollWidth=clientWidth=360 and zero horizontal overflow; the hero stacks cleanly.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	The CSS feature probe found responsive and modern interaction rules but no `@container` token; this component-heavy landing page is therefore coupled to global viewport breakpoints. F004 low: The page adapts at the viewport level but exposes no container-query implementation.
adapt-to-the-form-factor `input-modality-aware`	issues	high	The target probe found dozens of visible links only 16 px high; these are below comfortable touch-target guidance even though keyboard outlines are generally present. F005 medium: Many visible footer links have undersized hit areas.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	The first viewport states “Microsoft Forms”, explains surveys/quizzes, and presents Sign in and Try for free actions prominently.
support-core-task-success `primary-flow-completion`	pass	high	Primary CTAs are crawlable anchors with concrete Microsoft sign-in, trial, and pricing destinations; no dead control was observed on the public path.
support-core-task-success `clear-system-state-and-recovery`	not-applicable	high	The public landing path contains no data-loading, empty, submission, or partial-completion state; authenticated product states were outside the credential-free scope.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured LCP 17.2 s and CLS 0.589 with performance score 27; the independent trace still measured LCP 3.46 s and 534 ms total blocking time. F006 critical: Cold-load Core Web Vitals are far outside the good range.
be-fast-and-stable `visual-stability`	issues	high	Lighthouse measured CLS 0.589, while the image audit found 36 of 41 images without explicit width/height attributes, a concrete source of unreserved layout space. F007 high: The page shifts substantially during the Lighthouse load.
be-fast-and-stable `efficient-main-thread`	issues	high	The trace recorded three long tasks, the longest 432.52 ms, with 534.24 ms total blocking time; Lighthouse reported 310 ms TBT. F008 high: Long main-thread tasks block responsiveness during load.
be-fast-and-stable `efficient-resource-delivery`	issues	high	The HAR recorded 119 requests and 4,406,313 transferred bytes, including 64 scripts (2.43 MB) and seven fonts (1.15 MB). F009 high: The landing page delivers a large, fragmented critical load.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimates 443 KiB unused JavaScript and 346 KiB unused CSS; one global stylesheet is 98% unused. F010 high: Large amounts of shipped JavaScript and CSS are unused on first load.
be-inclusive `names-roles-labels`	pass	high	Lighthouse accessibility scored 100 and link-name/label audits found no applicable failures; meaningful hero images have descriptive alt text.
be-inclusive `sufficient-contrast`	pass	high	Lighthouse/axe colour-contrast audit passed for the standard rendered state.
be-inclusive `structure-and-focus`	pass	high	The page has one H1 followed by logical H2/H3 sections, a skip link, semantic controls, and visible dotted/dashed focus indicators in the focus probe.
be-inclusive `legible-text`	pass	high	Desktop and mobile captures show readable line lengths, clear hierarchy, and no clipping or cramped hero text.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	The target probe found dozens of visible footer and utility links with only 16 px-high boxes; mobile reflow itself had no horizontal overflow and the viewport permits scaling. F023 medium: Many visible links do not provide a sufficiently large interaction target.
follow-best-practices `no-console-errors`	pass	high	Lighthouse `errors-in-console` passed with an empty error table.
follow-best-practices `sound-document-and-assets`	issues	high	The image audit found 36/41 images without dimensions, nine without responsive sources, two oversized assets, and one legacy-format asset. F011 medium: Image markup omits dimensions and responsive source selection.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse reported three deprecation warnings: two unload listeners and a synchronous main-thread XMLHttpRequest. F012 medium: Deprecated unload handlers and synchronous XHR remain in production bundles.
be-discoverable `title-and-description`	pass	high	DOM probe found descriptive title and meta description matching Microsoft Forms.
be-discoverable `crawlable-and-mobile-friendly`	pass	high	The page has a viewport meta tag, real hrefs, descriptive CTA text, robots index/follow, and a valid robots.txt according to Lighthouse.
be-discoverable `canonical-and-indexing-signals`	issues	high	Fetching `/sitemap.xml` returned status 200 but an HTML Microsoft content page rather than XML, weakening route discovery and robots/sitemap consistency. F013 medium: The advertised sitemap endpoint does not return a sitemap.
be-discoverable `structured-and-shareable-metadata`	issues	high	The DOM probe found Open Graph title/description/url but zero JSON-LD blocks for the Microsoft Forms software/product entity. F014 low: The product landing has social tags but no structured entity data.
be-private-and-secure `secure-transport-and-headers`	issues	high	HTTPS, HSTS, CSP, and Trusted Types are present, but CSP permits `unsafe-eval`/`unsafe-inline`; nosniff is absent. All three observed cookies use SameSite=None and MUID lasts 390 days. F015 high: Security headers and cookie posture are incomplete.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	The tracker probe observed 14 third-party origins, including Microsoft event endpoints, RUM, and Vidyard; the HAR transferred 4.4 MB before any audited consent action. F016 medium: The first load contacts a broad third-party and telemetry surface.
be-private-and-secure `in-context-permissions-and-modern-auth`	not-applicable	high	No permission request fired and authentication is delegated to Microsoft’s separate identity flow; the unauthenticated landing exposes no auth implementation to inspect.
be-private-and-secure `defensive-browser-policies`	issues	high	The header probe found no Referrer-Policy, Permissions-Policy, X-Content-Type-Options, or explicit X-Frame-Options/frame-ancestors directive. F017 high: Several browser-enforced defensive policies are absent.
be-resilient `progressive-enhancement`	issues	high	The discoverability primitive found only 4% rendered-word coverage in raw HTML, classified the response as a JS shell, and showed the crawler view without the product page. F018 high: Almost all meaningful product content depends on JavaScript.
be-resilient `resilient-runtime-behaviour`	pass	high	The responsive public state loaded without console errors; navigation and carousel controls remained within the viewport and CSS includes anchor/overscroll safeguards.
be-resilient `offline-and-installable`	not-applicable	high	This is a public product marketing page, not an installable app surface; no manifest/service-worker registration is expected for this route.
be-resilient `network-and-http-failure-states`	issues	high	The no-JavaScript crawler capture contains only a tiny shell and 4% of rendered content, so a blocked or failed script removes the page’s purpose and recovery path. F019 high: A script failure leaves the core public page effectively blank.
be-internationalised `lang-dir-and-logical-properties`	pass	high	The localized final URL uses en-GB content, `<html lang="en-GB">`, LTR direction, and a responsive layout that remained intact.
be-internationalised `locale-aware-data`	not-applicable	high	The representative page contains no user-facing dates, currency, measurements, or locale-sensitive numeric data.
be-internationalised `time-zone-correctness`	not-applicable	high	The representative page contains no event scheduling or time-zone-sensitive data.
be-trustworthy `no-dark-patterns`	pass	high	The consent banner offers Reject with equal visual prominence to Accept, and primary Sign in/Try for free actions use clear labels without disguised commitment.
be-trustworthy `humane-error-handling`	not-applicable	high	There is no user-data form on the public landing page; the only form control is site search in the global header.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	No address, payment, sign-in, sign-up, or other user-data input appears on the public landing route.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	Pricing and sign-in are outbound journeys; checkout/account management are separate authenticated or commerce surfaces not represented by this route.
be-sustainable `optimised-assets`	issues	high	The image audit found no modern-format images, nine missing responsive sources, two oversized images, and 36 missing intrinsic dimensions. F020 medium: Image delivery is not consistently resolution- or format-efficient.
be-sustainable `no-wasteful-work`	issues	high	The HAR contains 64 scripts and the trace records 534 ms blocking time; Lighthouse identifies 443 KiB unused JS and deprecated synchronous XHR. F021 high: The page performs disproportionate script and telemetry work for a marketing landing page.
be-sustainable `third-party-and-media-budget`	issues	high	The 4.4 MB load includes 2.43 MB of scripts, 1.15 MB of fonts, and 14 third-party origins for a text-and-image product landing. F022 high: Third-party, font, and script bytes dominate the page budget.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	This public marketing landing does not expose a task-completion tool surface; agent tooling is an emerging opportunity, not an applicable obligation here.
be-agent-ready `on-device-inference`	not-applicable	high	The page has no local inference task where a built-in language model or summarizer would improve its core marketing purpose.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After ten full-page scroll cycles, heap self-size was 36.94 MB versus a 37.02 MB baseline; no retained-size growth signal appeared.
be-memory-efficient `bounded-footprint`	pass	high	The baseline heap summary reported 37.02 MB self-size for the long, component-rich landing page; this is proportionate to the rendered surface despite network bloat.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Ten repeated scroll cycles produced no heap-size growth (37.02 MB to 36.94 MB) and only ~0.6% node-count variation across independent captures, with no unbounded trend.

Provenance

Canonical report: results/atomic/reports/1000-forms_cloud_microsoft.json
Report SHA-256: 91ca141737ea780f4989b36ebfbfed6b4871f98bae9a655ee3eae00ad9679e9c
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/forms_cloud_microsoft/2026-07-24T10-58-58-824Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/forms_cloud_microsoft/2026-07-24T10-58-58-824Z
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.