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

# Upgrade {#upgrade-1}

## Versioning {#versioning}

AQG follows semantic versioning (`MAJOR.MINOR.PATCH`):

-   **MAJOR**

    Incompatible or breaking changes.

-   **MINOR**

    Backwards-compatible new functionality.

-   **PATCH**

    Backwards-compatible bug fixes.

The changelog of every release is maintained in `CHANGELOG.md` in the
repository.

## Updating the extension {#updating-the-extension}

```bash
composer update priebera/typo3-a11y-quality-gate
vendor/bin/typo3 extension:setup
vendor/bin/typo3 cache:flush
```

In Classic installations, update the extension in the Extension Manager and run
the database analyser.

## After an update {#after-an-update}

1.  Run **Re-scan TCA** in the Settings view if the release adds rules
    or supports new field types.
1.  Check the **Rules** tab. New rules are available for the first time
    and may need to be reviewed for your project.
1.  Run a full scan so that existing pages are re-evaluated with the new rules.
    Expect additional findings after a release that adds rules; this does not
    mean the site got worse.
1.  If the quality gate runs in blocking mode, run the full scan before the next
    editorial cycle, so that editors are not blocked by findings they have not
    seen yet.

## TYPO3 version upgrades {#typo3-version-upgrades}

AQG supports TYPO3 13.4 LTS and TYPO3 14.3 or later. TYPO3 14.0 to 14.2 are
declared as conflicting.

When upgrading TYPO3 13 to 14:

-   The backend module moves from **Web** to **Content**. The
    route identifier stays `web_a11y`, so backend user group permissions,
    bookmarks and AJAX routes keep working.
-   Scheduler task parameters are unchanged. On TYPO3 14 the fields are
    registered through TCA on `tx_scheduler_task`, on TYPO3 13 through the
    additional field provider of the task.
-   Rulesets, findings, ignore states and field configuration are kept.

## Findings and fingerprints {#findings-and-fingerprints}

Findings are matched across scans by a stable fingerprint. Ignore states survive
rescans as long as the underlying content is unchanged. Editing the content that
produced a finding creates a new finding, which is open again — this is
intentional, because the changed content has to be re-evaluated.