> For the complete documentation index, see [llms.txt](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/images-and-media.md).

# Auditing

DevAlly provides two types of accessibility audits to test your products: **site audits** and **workflow audits**. Both audit types help you identify and fix accessibility issues to ensure your products are inclusive and compliant.

***

### What is auditing?

Auditing is the process of automatically scanning your product to detect accessibility violations against WCAG (Web Content Accessibility Guidelines) standards. Each audit generates a detailed report with:

* **Accessibility score**: overall accessibility score as a percentage (higher is better)
* **Issue count**: total number of accessibility violations detected
* **Detailed violations**: specific accessibility issues with code snippets, WCAG references, and fix recommendations

### Pick your audit type

{% tabs %}
{% tab title="Site audit" %}
**Best for:** public-facing pages that don't require authentication.

Site audits scan multiple URLs from your product to identify accessibility issues. They're ideal for testing:

* Marketing pages
* Public landing pages
* Documentation sites
* Blog posts
* Any pages accessible without signing in

**What gets audited:**

* Root URL (always included by default)
* Additional URLs you select
* Each page is analyzed independently

→ [Run a site audit](/EfyQpV4281edZ3h0g8tY/core-concepts/images-and-media/site-audits.md)
{% endtab %}

{% tab title="Workflow audit" %}
**Best for:** user journeys that require authentication.

Workflow audits run your pre-configured workflows to identify accessibility issues within multi-step user journeys. They're ideal for testing:

* Sign-in and sign-up flows
* Account settings and dashboards
* E-commerce checkout processes
* Multi-page forms
* Any authenticated user experience

**What gets audited:**

* Each workflow you select
* All blocks (steps) within the workflow
* Interactive elements and dynamic content
* State changes throughout the user journey

→ [Run a workflow audit](/EfyQpV4281edZ3h0g8tY/core-concepts/images-and-media/workflow-audits.md)
{% endtab %}
{% endtabs %}

{% hint style="info" %}
Site audits work on **Website** products only. Workflow audits work on both Website and Web app products. See [Products](/EfyQpV4281edZ3h0g8tY/core-concepts/markdown.md) for the difference between the two product types.
{% endhint %}


---

# 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://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/images-and-media.md?ask=<question>&goal=<user_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.