---
title: "Automation"
manual: "Accessibility Quality Gate"
version: "2.1"
permalink: "https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:automation@2.1"
source: "Automation/Index.rst"
rendered: "2026-10-27T10:03:44+00:00"
---

# Automation {#automation}

Content scans can be automated with the TYPO3 command line interface and with
the TYPO3 Scheduler. Both are available in all editions.

> [!NOTE]
> Subtree runs (`--root-pid`, or a Scheduler task with a root page) apply the
> local rules (`rte.*` and `structured.*`) only. Single-page runs
> (`--page-uid`, or a Scheduler task with a page UID) additionally run the
> rendered page check, see [Rendered page checks](https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:usage-rendered-checks@2.1). Changed-only runs never
> include it. Interactive frontend crawler scans are started from the backend
> module, see [Frontend scans (remote crawler)](https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:usage-remote-scans@2.1); scheduled frontend monitoring uses
> `a11y:monitor`, see [Scheduled frontend monitoring (PRO, Agency)](https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:automation-monitoring@2.1).

-   [Command line](https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:command-line-usage@2.1)
-   [Scheduler](https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:scheduler-task@2.1)
-   [Monitoring](https://docs.typo3.org/permalink/priebera/typo3-a11y-quality-gate:scheduled-frontend-monitoring-pro-agency@2.1)