# Web inspection

Use the available built-in browser first. Choose coverage by the intended surface and design differences, rather than URL count. For an application capture, prioritize accessible product views or readable product screenshots. For a public-site capture, inspect representative landing, reading, feature, and form treatments where they differ. Record missing product access without substituting website styling for product evidence.

A marketing page may contain several visual layers: page chrome, a demonstration frame, and the depicted product. Identify which layer supports each observation. Save enough context to distinguish them. When both website and product are in scope, record their coverage separately.

Capture desktop and narrow layouts where available. Exercise representative navigation, hover, keyboard focus, menus, dialogs, and forms within the user's scope. Inspect loading, error, disabled, and empty states when reachable without external side effects. Record unavailable states as gaps.

Measure representative elements through computed styles when accessible: type metrics, color roles, spacing, container and pane widths, row and header heights, radii, boundaries, and transitions. Inspect alignment and scrolling behavior alongside individual values. Match measurements to elements, surfaces, states, themes, and viewports in the manifest. Distinguish recurring rules from isolated decoration.

Save screenshots as you inspect. Try the browser's save option once; if unavailable, use a supported alternative or record the missing file. Verify saved files open correctly. An image visible in a tool result may not exist on disk.

Observe responsive transformations before describing them. One narrow screenshot establishes an arrangement, not an exact breakpoint. A CSS declaration establishes a value, not proof of an exercised interaction. Treat blocked pages, inaccessible styles, authentication, and unsupported browser capabilities as capture limits.

Record verified source fonts, component libraries, and icon packages in the manifest, with their evidence. Describe visible font and icon traits when implementation identity is unknown. Apply the entrypoint's neutrality contract when translating observations into the guide.
