Accessibility Quality Gate

Catch accessibility issues before you publish.

Automated checks, issue management, and publish safeguards — built directly into TYPO3 for editors, integrators, and agencies.

TYPO3 13 / 14 No card required Local checks free
Why AQG exists

From missed checks to controlled publishing.

Accessibility problems usually surface too late — during audits, client reviews, or after content is already live. AQG moves these checks into the TYPO3 editing workflow, so issues are found, reviewed, and resolved before they ever reach production.

Manual workflow

Checks happen too late

  • Reviews run after publish — during audits or client hand-off
  • Results are inconsistent between editors and projects
  • Fixing issues on live pages is slower and more expensive
  • Easy to skip entirely when deadlines are tight
AQG workflow

Issues caught while editing

  • Inline feedback in CKEditor as editors write
  • Page-level issue overview inside the TYPO3 backend
  • Remote crawler scans of rendered frontend pages
  • A publishing Quality Gate that blocks critical issues
Interactive walkthrough

See AQG in a real TYPO3 workflow

Watch how an editor finds issues, reviews page-level results, and uses the Quality Gate to improve accessibility before publishing — no setup required.

Review issues by severity Open page-level detail See editor-friendly fixes

Interactive demo powered by Supademo. Opens in-place and can be viewed fullscreen.

Core capabilities

One TYPO3-native workflow from editor feedback to frontend reports.

Editors

Inline editor feedback

Catch issues directly in CKEditor and on content element detail screens, so editors know what to fix immediately.

Overview

Page tree visibility

Review critical, warning, and info findings across page trees with team-friendly prioritisation.

Governance

Publishing Quality Gate

Warn editors in Free, or block publishing in Pro until critical issues are fixed.

Reporting

Remote crawler scans

Scan real frontend pages, capture screenshots, and generate PDF/CSV reports for stakeholder review.

Editor view

Make accessibility visible where content is edited.

Connect editor feedback, page-level review, and publish control in one TYPO3-native workflow.

TYPO3 editor view with Accessibility Quality Gate feedback
Workflow

Install, scan, fix — then protect publishing.

01

Install

Install the extension via Composer or TER and open the AQG module in TYPO3.

02

Scan

Run your first scan locally, through Scheduler, or via CLI and review issues by severity.

03

Fix

Fix flagged content elements, validate again, and enable the Quality Gate for your publishing workflow.

EAA readiness

The European Accessibility Act is now in force. Is your TYPO3 content ready?

AQG helps teams prepare TYPO3 workflows for WCAG-related checks in the editor and on the frontend before publish.

Read the guide
AQG PRO trial

Run the full AQG workflow on your own TYPO3 site.

Start a 5-day PRO trial and test it on real content — from inline editor checks to remote crawler reports, before you decide.

Remote frontend scanPDF + CSV reportsPublishing Quality Gate
Plans

Start free, upgrade when your workflow needs more control.

Every plan runs the same checks. Higher tiers add remote audits, reporting, and stronger publish safeguards.

Free

€0/forever

For individuals and teams getting started with local TYPO3 accessibility checks and no licence key.

  • No licence key required
  • Rendered page check
  • Scheduler + CLI
Get started free

For TYPO3 agencies & integrators

Agency

€99/mo

For agencies running accessibility across multiple TYPO3 client projects.

  • Unlimited domains, one key
  • One licence per installation
  • Dedicated email support
Go Agency
Compare all plans Full feature matrix, billing options and FAQ.
Get started

Start catching accessibility issues today.

Install AQG and run local checks for free. Upgrade to Pro when you need remote audits, screenshots, and PDF reporting.

Open source · No licence key required for local checks

Frequently Asked Questions

What accessibility standard does AQG check against?

AQG helps identify WCAG-related issues that matter for accessible commercial websites and digital products.

Which TYPO3 versions are supported?

Accessibility Quality Gate supports TYPO3 13.4 LTS and TYPO3 14 with PHP 8.2 or newer.

Does AQG work with multi-site TYPO3 installations?

Yes. The Pro licence covers one TYPO3 project with 1 domain. The Agency licence covers one TYPO3 installation with unlimited domains.

Do I need a licence key for the free version?

No. The free version requires no licence key and no account. Install via Composer or TER and start scanning immediately.

What is the Quality Gate?

The Quality Gate is a configurable rule that runs when an editor saves or publishes a page. In warn mode it allows publishing. In block mode (PRO) it prevents publishing until issues are resolved.

What is the remote crawler?

The PRO remote crawler scans your live frontend pages in a real browser, not just backend content. This catches issues that only appear after rendering.

How does AQG differ from axe DevTools or WAVE?

AQG is built specifically for TYPO3 editorial workflows. It integrates directly into the TYPO3 backend, provides per-content-element feedback, tracks issues over time, and can block publication of inaccessible content.

Will AQG slow down my TYPO3 installation?

No. Local scans run on demand or via Scheduler during low-traffic periods. The remote crawler runs on separate infrastructure and does not affect your TYPO3 server performance.

What happens when my PRO licence expires?

Your TYPO3 installation continues to work normally. PRO-only features such as the remote crawler, PDF export, and blocking mode become unavailable. Local scanning and all free features remain active.

Is my content data sent to your servers?

Local backend scanning runs entirely within your TYPO3 installation — no content leaves your server. The remote crawler fetches your public frontend URLs and processes accessibility results on our infrastructure.

Can I use AQG in a CI/CD pipeline?

The a11y:scan CLI command can be integrated into deployment pipelines. Full CI/CD exit code support is on the roadmap.