> 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.md).

# Issues, Cases and Occurrences

#### What are accessibility issues? <a href="#what-are-accessibility-issues" id="what-are-accessibility-issues"></a>

Accessibility issues are problems that prevent people with disabilities from using your website or app. DevAlly automatically detects these issues and helps you fix them efficiently.

{% hint style="info" %}
DevAlly groups issues into a three-level pyramid: **issues** (root problems) → **cases** (patterns of where they appear) → **occurrences** (specific instances). Pick the level that fits the question you're trying to answer.
{% endhint %}

#### The three-level system <a href="#the-three-level-system" id="the-three-level-system"></a>

Our accessibility system organizes problems into a clear hierarchy that helps you understand and fix issues efficiently. Think of it as a pyramid where each level provides different information for different purposes.

**Issues: the root problems**

**What**: the underlying accessibility problem in your product **Example**: "Color contrast insufficient" or "Images missing alt text" **Purpose**: understand what's wrong and prioritize your fixes

**Cases: the patterns**

**What**: how an issue appears across your site (selector-based grouping)\
**Example**: `.header-text` pattern affecting 8 pages, `.footer-link` pattern affecting 5 pages\
**Purpose**: find high-leverage fixes that resolve multiple instances at once

**Occurrences: the specific instances**

**What**: exact instances captured during audits with full context **Example**: specific product page with exact DOM context and screenshots **Purpose**: debug edge cases and verify fixes

#### How they work together <a href="#how-they-work-together" id="how-they-work-together"></a>

Issues give you the big picture: what problems exist and how serious they are. **Cases show you patterns**: which elements have issues and how fixing them can resolve multiple instances across your site. Occurrences provide the detailed context you need for debugging specific issues.

#### High-leverage fix opportunities <a href="#high-leverage-fix-opportunities" id="high-leverage-fix-opportunities"></a>

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

#### Quick start <a href="#quick-start" id="quick-start"></a>

{% stepper %}
{% step %}
**Review your issues**

See what problems exist across your product.
{% endstep %}

{% step %}
**Look for high-leverage fixes**

Open cases with multiple occurrences. Fixing the shared selector once can resolve every occurrence.
{% endstep %}

{% step %}
**Fix systematically**

Start with high severity, then work through cases with the most occurrences.
{% endstep %}

{% step %}
**Validate results**

Re-audit to confirm fixes worked across all pages.
{% endstep %}
{% endstepper %}

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

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-circle-exclamation">:circle-exclamation:</i> <strong>Understanding issues</strong></td><td>Learn about the root problems.</td><td><a href="/EfyQpV4281edZ3h0g8tY/core-concepts/interactive-blocks/understanding-issues.md">Understanding Issues</a></td></tr><tr><td><i class="fa-layer-group">:layer-group:</i> <strong>Working with cases</strong></td><td>Plan your fixes around patterns.</td><td><a href="/EfyQpV4281edZ3h0g8tY/core-concepts/interactive-blocks/working-with-cases.md">Working with Cases</a></td></tr><tr><td><i class="fa-magnifying-glass">:magnifying-glass:</i> <strong>Debugging with occurrences</strong></td><td>Handle specific instances and edge cases.</td><td><a href="/EfyQpV4281edZ3h0g8tY/core-concepts/interactive-blocks/debugging-with-occurrences.md">Debugging with Occurrences</a></td></tr></tbody></table>


---

# 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.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.