---
title: "Upgrade"
manual: "Accessibility Quality Gate"
version: "2.0"
permalink: "https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:upgrade@2.0"
source: "Upgrade/Index.rst"
rendered: "2026-10-13T16:37:33+00:00"
---

# Upgrade {#upgrade}

## Versioning {#upgrade-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 {#upgrade-procedure}

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

Administrators learn about a new stable release from the update notice in the
AQG modules, see [Update notice](https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:usage-overview-update-notice@2.0). The notice only links to
the release notes and these instructions; updating stays a deliberate step in
Composer or the Extension Manager. A development checkout without a release
version, such as `dev-main`, shows no notice.

## Upgrading to AQG 2.0 {#upgrade-2-0}

AQG 2.0 redesigns the backend views, the rich-text feedback and the PDF reports.
It needs no configuration change:

-   The requirements are the same as for 1.9: TYPO3 13.4 LTS or 14.3 and later,
    PHP 8.2 and later.
-   The update adds database columns only. Run
    `vendor/bin/typo3 extension:setup` (or the database analyser in Classic
    installations) and flush the caches.
-   Rulesets, findings, ignore states, field configuration, the licence, the
    Scanner Token and the AI settings are kept.
-   The next content scan updates findings whose stored snippet format changed
    without reporting them as resolved and new; ignored findings stay ignored.
-   Some frontend scan features, such as the Highlighted / Original screenshot
    switch, need the matching AQG service release. AQG 1.9 installations keep
    working with that service release, so a service update does not require an
    extension update.

The changelog lists every change of the release.

## After an update {#upgrade-after}

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 {#upgrade-typo3}

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