Getting the statement onto your website

Once published, your statement has a permanent public address. How it gets from there onto your website is up to you. One way is enough. What matters is that visitors can reach the statement from every page – usually through an “Accessibility” link in the footer.

The ways compared

Way	Requires	New version appears	Without JavaScript
Link to the public address	publication, from the Starter plan	immediately	yes
Embed snippet	from the Starter plan	within a few minutes	the link stays
Server-side embedding	from the Starter plan, your own server code	depends on your cache	yes
WordPress plugin	publication, from the Starter plan	after up to 60 minutes, plus page cache	yes
Use it yourself	none, in every plan	never on its own	yes

Link to the public address

After publishing, the address is shown in the website’s “Overview” tab, in the “Statement” section. The publishing page also offers a “Ready-made link for your footer”.

The public page is built to be accessible and contains the form visitors use to report barriers, the PDF and all earlier versions. It stays online even when your subscription ends – a linked statement must not lead nowhere.

Embed snippet or server-side embedding

For systems without a plugin: TYPO3, Drupal, Webflow, a custom frontend. The text then sits on your own domain and follows every new version. Setup, allowed domains and what happens after a subscription ends: Embedding the statement without a plugin.

WordPress plugin

The plugin places the text on a page with a shortcode or block and starts scans straight from WordPress. It verifies the domain without DNS access. Set up the plugin · Show the statement

Use it yourself

You download the draft as Markdown and copy it into your system – possible in every plan. The reporting channel for barriers, the date of the last review and the archive of earlier versions are then your responsibility, and a new scan does not change your text. Using the draft yourself

Which way fits?

Your website runs on WordPress: the plugin.
Another system, and you can add server code: server-side embedding – the text is then part of the page even without JavaScript.
You can only paste HTML: the snippet.
You don’t want to build anything in: a link in the footer.

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.

Using the draft yourself

How to download the draft statement as Markdown and put it into your own system – and what you are then responsible for yourself.

From scan to published statement

Which steps come before publishing an accessibility statement, what blocks publication and what happens afterwards.