Add your sites for accessibility checks
Add your organisation's sites, prove they are yours, set up sign-in with a test account, and add flows.
Where the portal runs accessibility checks itself, it can check your organisation's own sites, with no CI. Admins add and set up sites, in person, never with an access token; designers and above then check them.
Add a site
- Open Accessibility checks (/accessibility-checks) and the Sites tab.
- Choose Add site and enter:
- Name: such as "Acme staging".
- Address: its scheme, host and port with no path, such as
https://staging.example.com. - Start page (optional): a path where checks that follow links start.
- Choose Add site.
Prove it's yours
On a hosted portal a site is checked only once it's proved yours. The site's Ownership tab gives its token. Use one of these:
- A DNS record: add a TXT record at
_pfdl-a11y.<host>holding the token, then choose Check ownership by DNS. - A file: serve the token alone at
https://<host>/.well-known/pfdl-a11y.txtastext/plain, with no redirect, then choose Check ownership by file. - Ask the operator to approve it, if you can't change either.
A proof covers that one address, is checked again every day, and ends if the record or file goes. Changing the address starts again. A portal of your own may not ask for proof.
Sign in for checks
To check pages behind sign-in, give the site a test account, never a real person's: its pages appear in reports. Give it no admin rights, no real customer data, and a password used nowhere else.
- Open the site's Sign-in tab.
- Choose Add a sign-in flow: the steps that type
${secret:username}and${secret:password}. - Under Sign-in details, choose Add › A value for the flow for each name it types. Add also offers a TOTP seed, HTTP basic credentials, a request header, or a saved session for single sign-on.
- Choose Test sign-in to see whether it works.
Values are encrypted and never shown again. A sign-in through your identity provider needs its address under Settings › Sign-in addresses.
Add flows
Flows take a check through your app's tasks. On the Flows tab, choose New flow (or Import JSON), then Save flow. Publishers and admins save flows; designers run them with Check this flow.
What checks may load
On a hosted portal, checks load only the site and the origins under Settings › Also loads from. List every CDN, font service and API the pages use.
If something goes wrong
| What you see | What to do |
|---|---|
| No Sites tab | The portal doesn't run checks itself. Use CI instead. |
| "The last check didn't find it" | Wait for the DNS record to spread, or check the file's address and type. |
| "The proof that this site is yours has ended" | Put the record or file back, then check ownership again. |
| "The sign-in flow types values this site doesn't have" | Add a value for each missing name on Sign-in. |