Automated vs manual testing
AQG performs automated accessibility checks. Automated scanning is a powerful first step — it consistently catches a broad range of technical issues across your entire site, including missing alt texts, empty headings, broken link labels, and many others.
However, some accessibility requirements can only be verified by a human.
- Does the page make sense when navigated by keyboard only?
- Is the reading order logical for screen reader users?
- Are form error messages clear and helpful?
- Is the content easy to understand for users with cognitive disabilities?
For a complete accessibility assessment, automated scanning should be combined with manual expert review, documentation and project-specific legal review where required.
Rendered page check
AQG also includes a rendered page check for the current page. This scan is HTML-only and is designed for fast page-level reviews directly from the TYPO3 backend.
- Rendered page check is HTML-only.
- JavaScript is not executed during this free page scan.
- Dynamic content rendered client-side is not scanned.
- Only the current page is scanned, not the full site.
Does a clean scan mean my site is EAA compliant?
No. A clean AQG scan means no automated accessibility issues were detected. It does not mean your site is legally compliant with the European Accessibility Act or any other accessibility regulation.
Legal compliance requires a complete assessment that includes both automated and manual testing, proper documentation, and — depending on your jurisdiction — a published accessibility statement.
Local vs remote scan — what is the difference?
AQG offers two types of scans that complement each other.
| Scan type | How it works | Best used for |
|---|---|---|
| Local backend scan | Analyzes content records directly from the TYPO3 database. Covers all pages including hidden and draft pages, plus RTE fields, image alt texts, and structured data. | Editorial QA, unpublished content, fast checks inside TYPO3. |
| Remote scan | Loads your published frontend pages in a real browser and checks the fully rendered output as a real visitor would see it. Covers dynamic content, embeds, and frontend-only rendering issues. | Production monitoring, rendered frontend output, public site validation. |
We recommend running both regularly: local scans to catch issues before publish, and remote scans to validate what real visitors actually receive. Trial, PRO and Agency scans may have page limits. Remote scans only cover publicly reachable pages unless scanner access or protection settings are configured. Screenshots and reports are PRO/Agency/Trial features.