> 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/interactive-blocks/working-with-cases.md).

# Working with Cases

#### What is a case? <a href="#what-is-a-case" id="what-is-a-case"></a>

A case is the pattern an issue takes in your product. It groups every occurrence of the issue that shares the same CSS selector, so you can fix the pattern once instead of fixing each instance.

For example, if the issue "Color contrast insufficient" has cases like:

* `.header-text` pattern affecting 8 pages
* `.footer-link` pattern affecting 5 pages
* `.button-primary` pattern affecting 12 pages

each case represents one selector pattern where the issue appears across your application.

#### Case properties <a href="#case-properties" id="case-properties"></a>

When you open a case you'll see:

* **Case key**: a workspace-friendly identifier, e.g. `DEB-265`
* **Title**: a short description of the case
* **Element type**: the type of element this case applies to (e.g. button, link, image)
* **Status**: Active, Resolved, or Regressed
* **Status counts**: how many of the case's occurrences are Active, Resolved, or Regressed
* **Pattern details**: the CSS selector shared by every occurrence in this case
* **Impact & scope**: total occurrences, number of affected URLs, and a short scope description
* **Case summary**: detection method, first detected date, and any common pattern metadata
* **Code example**: a representative before/after fix for the case
* **Occurrences**: tabs for Active, Resolved, and Regression occurrences belonging to this case

The case page also displays the parent issue's severity and WCAG reference for context.

#### Finding high-leverage fixes <a href="#finding-high-leverage-fixes" id="finding-high-leverage-fixes"></a>

When a case has more than one occurrence, the case page surfaces a **High-leverage fix opportunity** alert. The same selector is appearing in multiple places, which means a single change to the shared component or CSS class can resolve every occurrence at once.

For example, if `.product-price` is failing contrast on 20 different product pages, you can fix the CSS once and resolve all 20 occurrences.

#### Case statistics <a href="#case-statistics" id="case-statistics"></a>

Cases track their progress through three counts:

* **Active**: currently detected occurrences
* **Resolved**: previously detected, not detected now
* **Regressed**: was resolved, but reappeared in a later audit

These stats help you understand the scope of each case and track your progress as you implement fixes.

#### Next steps <a href="#next-steps" id="next-steps"></a>

Now that you understand cases, you need to decide whether to work at the case level or drill deeper into specific occurrences. The following sections will guide you towards the right approach.

* Debugging with occurrences: drill into specific instances
* When to use cases vs occurrences: choose the right level for your fix


---

# 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/interactive-blocks/working-with-cases.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.