---
title: "Enabling rules"
manual: "Accessibility Quality Gate"
version: "main"
permalink: "https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:configuration-rules@main"
source: "Configuration/Rules.rst"
rendered: "2026-09-17T16:05:02+00:00"
---

# Enabling rules {#enabling-rules}

The **Rules** tab lists all built-in rules with their category,
severity and WCAG reference, and lets you enable or disable each rule
individually. The enabled state is stored as JSON in the `rules_json` column
of the active ruleset.

Disabled rules are skipped during content scans, rendered page checks, CLI runs
and Scheduler runs. Findings that were produced by a rule before it was disabled
are removed on the next scan of the affected pages.

For the full list of rule identifiers see [Rule reference](https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:rule-reference@main).

## When to disable a rule {#when-to-disable-a-rule}

Typical reasons to disable a rule:

-   The rule targets a markup pattern that your site templates never produce.
-   A rule reports a best practice that conflicts with an agreed editorial
    convention, for example `rte.link_to_document_missing_notice`.
-   A rule produces findings that are handled by another tool in your workflow.

If a rule is generally useful but wrong on a single page or for a single site,
prefer the ignore workflow instead of disabling the rule globally; see
[Ignoring findings](https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:usage-page-detail-ignore@main).