> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/how-to-guides/visual-coverage.md). # Visual coverage Techniques to capture more of your interface, from responsive viewports and injected CSS to non-image file diffs. Techniques to capture more of your interface and make every screenshot count. * [Responsive viewports](/docs/learn/how-to-guides/visual-coverage/responsive-viewports.md) – Capture the same screen at multiple viewport widths * [Storybook story modes](/docs/learn/how-to-guides/visual-coverage/storybook-story-modes.md) – Capture stories across multiple modes and themes * [Capture screenshots from URLs](/docs/learn/how-to-guides/visual-coverage/capture-screenshots-from-urls.md) – Screenshot a list of URLs without writing tests * [Injecting CSS](/docs/learn/how-to-guides/visual-coverage/injecting-css.md) – Apply custom CSS at capture time to hide or restyle elements * [Fallback baselines](/docs/learn/how-to-guides/visual-coverage/fallback-baselines.md) – Compare a variant against an existing screenshot instead of reporting it as added * [Adding ARIA snapshots manually](/docs/learn/how-to-guides/visual-coverage/adding-aria-snapshots-manually.md) – Attach accessibility snapshots alongside your screenshots * [Compare non-image files](/docs/learn/how-to-guides/visual-coverage/compare-non-image-files.md) – Diff text, JSON, and other non-image files in Argos --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://argos-ci.com/docs/learn/how-to-guides/visual-coverage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.