Managing websites for clients

An agency manages many websites but declares for none of them itself. That is why the service separates who owns the account from who declares for a website.

One organization, many websites

Add all client websites to your organization. How many depends on the plan – up to 25 in the Agency plan. Each website has its own domain verification, its own scans and its own statement.

Who declares: the client

The statement names who is responsible for a website’s accessibility. That is the client, not the agency.

So for each website, enter the client’s “Name of the responsible body” and “Type of body” under “Who is declaring” in “Settings”. If the field stays empty, the website takes your organization’s name – and the statement would carry your name. The publishing page shows who declares at the top, so it is noticed before approval.

The type of body decides which document is generated: Which accessibility statement do I need?.

The WordPress plugin at the client’s

The client does not need an account:

Create a token in their website’s “Embedding” tab – with a “Label” that tells you later where it is used.
Enter the token, site ID and service address in their WordPress – or pass the three values on securely.

The token is valid for this one website only. It can start scans and read results and the statement – no other website in your organization. When the collaboration ends, revoke the token. Instructions: Setting up and connecting the WordPress plugin.

Under “Organization” → webhooks there is also an overview of all tokens in your organization.

Webhooks for your own system

A webhook applies to all websites of the organization – suitable for your ticket system, not for the client: Setting up webhooks and verifying signatures.

Without a note on the tool

Below every statement there is a note on which tool created it. In the Agency plan you can switch it off under “Organization” – for all websites of the organization.

Team

All members of your organization see all websites. So a client’s staff do not belong in your organization: Team and roles.

Team and roles

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

Which accessibility statement do I need?

Statement under BITV 2.0, information under § 14 BFSG or a voluntary statement – what the type depends on and what the applicability check decides.

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.

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.