Help

How to check a website, review the results and publish an accessibility statement – on our site, embedded in your own, or with the WordPress plugin.

What can we help you with?

What the service checks – and what it doesn’t

Which requirements the automated scan measures, where it is uncertain, what only you can judge and why the service never changes your website.
The free scan without an account

What the free scan covers, how long the result is kept, which limits apply and what else you need for a published accessibility statement.
Adding a website and verifying the domain

How to add a website to your account and verify the domain by DNS record, meta element, file or WordPress plugin – and why verification is needed.

Reading the scan report

What the figures, findings, occurrences, severity levels and evidence images in the scan report mean – and how to tell how reliable a result is.
Assessing uncertain results

What the occurrences listed for review mean, how to classify them as a defect or not, and why they count neither as passed nor as failed.
Answering the manual checks

How the manual checks let you assess what cannot be measured, which questions block publication and what open questions mean.
Reviewing findings

How to classify a finding as no defect, won’t be fixed or disproportionate burden – and what each assessment does in the accessibility statement.
Scheduled scans, login areas and click paths

How to set up a recurring scan, have areas behind a login scanned and reach states through click paths.
Describing sign-in and click paths

How to define sign-in and click paths as steps, approve drafts and work with an AI assistant; selectors, keys, failure reasons.
Editing click paths through the API

The REST endpoints for click paths, sign-in flows and test runs, with examples, rights and error codes – for your own scripts without an AI assistant.

Which accessibility statement do I need?

Statement for public bodies, information under § 14 BFSG or a voluntary statement – what the type depends on and what the applicability check decides.
From scan to published statement

Which steps come before publishing an accessibility statement, what blocks publication and what happens afterwards.
Filling in the statement’s mandatory details

Which details no scan can generate – contact for reports, accessible alternatives, the responsible body – and what to keep in mind for each.
The conformance status – and when you may deviate

How the service suggests fully, partially or not conformant, when you may choose a different status and why that requires a justification.
Versions, “outdated” and PDF

Why every publication is an unchangeable version, what it means when a statement is marked as outdated, and how to publish a new version.
Using the draft yourself

When the draft statement is finished, how to copy or download it and put it into your own system – and what you are then responsible for.

Getting the statement onto your website

Link, embed snippet, server-side retrieval or WordPress plugin – which way fits and how quickly a new version appears with each of them.
Embedding the statement without a plugin

How to embed the statement with a snippet or server-side in TYPO3, Drupal or your own website – with allowed domains and never an empty spot.
Setting up and connecting the WordPress plugin

Step by step – install the plugin, create a token, enter the connection, verify the domain and start the first scan from WordPress.
Publishing the statement from WordPress

The whole way to your statement in the WordPress admin – manual checks, mandatory details, release – and who is responsible for it.
Showing the statement in WordPress: shortcode and block

How to place the statement on a WordPress page with a shortcode or block, cut out single sections and fit the headings into your page.
WordPress doesn’t show the statement, or shows an old one

Why the shortcode shows nothing, a notice or an old version – and what the plugin cache, cache plugins and your hosting provider’s cache have to do with it.
Working through findings in WordPress

How to read the findings list in the WordPress plugin, expand occurrences, scan again after a fix and keep an eye on your page quota.

Team and roles

Who may do what in an organization – owner, administration, editing, read only – and how to invite more people.
Managing websites for clients

How agencies run many client websites in one organization, who declares for them and how clients use the WordPress plugin without an account of their own.
Closing your account

When you can close an account, what happens immediately, how the deletion deadline starts, and how to request a return or withdraw the closure.
Setting up webhooks and verifying signatures

How your system learns when a scan has finished or a statement is outdated – with events, payload, signature verification and retries.
Plans, subscription and cancellation

What the plans include, what happens to websites and statements when you move to a smaller plan, and where to cancel or withdraw.

Reporting a barrier

Came across a barrier on a website? How to use the form below the accessibility statement – and what happens to your report.

Glossary

The key terms around accessibility scans and statements – from finding and success criterion to shortcode and conciliation procedure.

Tell us which question is still open. Questions we hear more than once become new help articles.