Frequently Asked Questions 

Why does the scan take a few seconds? 

The extension uses the "View Module" technique to render the page exactly as it would appear to a visitor. This involves a full rendering of the page by TYPO3, which can take some time depending on the complexity of your page and server performance.

Can I scan protected pages or pages with access restrictions? 

Yes. Since the scan runs in your browser using your current backend session, the "View Module" can render any page you have permissions to view in the backend.

Can I scan my entire website at once? 

No. The Accessibility Checker is designed for a page-by-page audit while you are working on a specific page. For full-site audits, we recommend using external tools or CI/CD integrations.

Why do different engines show different results? 

Different engines (axe-core and HTML CodeSniffer) use different rule sets and algorithms to detect accessibility issues. It is common for them to highlight different aspects or have varying severity levels for the same issue. We recommend reviewing results from both engines for a comprehensive audit.

Why don't I see a "For developers" tab? 

The developer-facing findings are only shown to backend users who have been explicitly granted Developer Corner access, either directly or through one of their backend groups. Administrators and system maintainers always have this access. See Developer Corner access for how to grant it to other users.

Can a green result be used as proof my site is accessible? 

No. The module provides automated assistance only, and automated tools can only detect a subset of WCAG success criteria. A page without findings may still have accessibility problems that require human judgement to catch. If you need your site officially certified as accessible, that certification has to come from a qualified accessibility audit. See What it is not.