Getting started
This guide takes you from a new account to a first useful result: a scanned site, a list of issues to fix, and a review your team can start on. Setting up is free; running scans needs a plan. Plans start at $49 a month.
1. Create your account
Section titled “1. Create your account”Go to app.theaccessibility.company/sign-up and enter your name, email and a password of at least 8 characters, accept the Terms of Service and choose Create account. You can use Continue with Google instead.
With an email and password, we send a link to confirm your address. Open it: it confirms the address, signs you in and takes you on to set up your workspace. You cannot sign in until the address is confirmed. If the email has not arrived after a few minutes, check your spam folder; if the link no longer works, contact us.
If a teammate invited you, open the link in their invitation and sign up (or sign in) with the address it was sent to; it brings you back to join their workspace. See Team and roles.
2. Set up your workspace and first site
Section titled “2. Set up your workspace and first site”After you confirm your email, the welcome page walks you through three steps. Only the workspace owner sees it.
- Workspace. Name the workspace (the home for your sites, scans and team) and its handle. We guess both; you can change them later in Settings → Account. A new workspace may also ask Where should your data be stored? That choice is made once, when the workspace is created.
- First site. Enter the Website URL and a Site name.
- Pages and scan. Choose which pages the scan visits:
- A sitemap. We look for one ourselves. If we find it, the pages in it are scanned, up to your plan’s limit, and new pages are picked up as your site grows.
- Your sitemap’s address. If we cannot find one, paste its URL and choose Check this URL.
- A list of pages. Otherwise list the pages to scan, one URL per line.
A new site is checked against WCAG 2.2 AA unless you chose another standard in your preferences. You can change a site’s standard, and how it finds pages, in the site’s Settings later: discovery can be Sitemap, Manual or Hybrid (both), and Follow links on scanned pages finds pages a sitemap misses by following links on the same site, up to a crawl depth you set.
If you already have a plan, the last step’s button is Start first scan. If not, it is Save setup and choose a plan: your setup is kept and you go to Billing. Set up later skips the scan and opens the site.
3. Choose a plan
Section titled “3. Choose a plan”Plans live in Settings → Billing, which owners and admins can open. Pick monthly or annual billing (annual is two months free), then Subscribe to a plan. Payment is handled by Polar, our merchant of record; tax is added at checkout, and invoices are under Manage billing.
| Plan | Sites | Pages monitored | Seats |
|---|---|---|---|
| Starter | 3 | 750 | 5 |
| Growth | 10 | 3,000 | 20 |
| Pro | 20 | 10,000 | Unlimited |
| Enterprise | Custom | Custom | Unlimited |
Pages are pooled across your sites. Some features start on higher plans, and each guide says which: the pricing page compares them all.
4. Run the first scan
Section titled “4. Run the first scan”If you started the scan from the welcome page, you are already on the site. Otherwise open Sites, choose your site and press Run First Scan (or Scan full site once it has been scanned before). The arrow beside Scan full site also offers Scan a single page….
Each page is loaded in a real browser and checked with axe-core and our own checks. While it runs, the Overview shows Scan in progress and the results arrive when it finishes. To scan on a schedule, see Scan schedules. Pages behind a sign-in need signed-in scanning.
5. Read the results
Section titled “5. Read the results”Inside a site, the sidebar is the site’s. It lists the site’s sections in the order of the work: Overview, Find (scans, journeys and screen readers), Review, Fix (issues, visitor reports, ignored and the trend), Report and Settings. The site’s name at the top switches to another site, and All sites goes back to the list.
Overview
Section titled “Overview”A site’s Overview opens with Where it stands:
- how many issues there are to fix, and how many are unconfirmed (the scan could not decide them, so a person does), with a count for each impact: critical, serious, moderate and minor;
- what changed since the last scan (new and resolved);
- a ring for the criteria of your standard: how many are settled, failing and waiting for a person;
- when the site was last scanned, and when it is next.
Below it:
- Most serious right now names the issues at the top of the list.
- Next up lists what to do next, in order: start or continue the review (with the next page to check and about how long it takes), decide unconfirmed issues, and verify fixes.
- So far on this site counts what has been found, fixed and tested since you added the site.
- Published for visitors says whether your accessibility statement and status page are published, and whether the statement is out of date.
Issues
Section titled “Issues”Fix in the site’s sidebar opens on Issues, which lists what the scan found. The same problem on many pages is one issue, with every page it was found on. Open one to see what is broken, the failing element and its selector, why it matters, and the affected pages.
- Unconfirmed issues ask the same question as the Review, in the rule’s own words (for low contrast: Readable or Too faint). The first answer records a false positive and dismisses the issue; the second confirms it. More options dismisses it another way: for one page, for a while, or for another reason.
- Assign an issue, change its status, and comment, so the team knows who is on it.
- When a fix ships, set the status to Pending verify and choose Verify now: scans of the affected pages mark the issue Verified if two in a row do not find the problem (the second runs straight after the first), or reopen it if one does.
Outside a site, Issues in the sidebar shows the same list across every site.
6. Start a review
Section titled “6. Start a review”A scan settles what a machine can. Most WCAG criteria also need a person: whether alt text describes its image, whether the page works with a keyboard and a screen reader. Review turns those into plain questions, with the steps to test beside each one.
Start it once the first scan has finished: choose Review in the site’s sidebar (or Start the first review session in Next up). Read Review for how it works, and the live review panel to answer checks beside the page in your own browser.
Your review’s answers, with the scan, are what the reports are built from: the UK, US and EU readiness reports, your accessibility statement, and the VPAT on Pro and Enterprise.
7. Invite your team
Section titled “7. Invite your team”As the owner, open Settings → Members and choose Invite member to invite teammates by email, choosing each person’s role: Admin, Member or Viewer. Members and above can run scans, triage issues and answer review checks; viewers can read everything but change nothing. See Team and roles for the details, and for how seats are counted on each plan.
Where to go next
Section titled “Where to go next”- Review: how a review samples your pages and asks what the scan cannot settle.
- Reports: the readiness reports, statement and VPAT, and how each is built.
- GitHub, Jira and Linear: take issues to where your developers work.
- Webhooks and alerts: scan from your deploy pipeline, and send scan alerts to Slack, Google Chat or email.
- MCP server: let your coding agent read an issue, fix it and check the page.
- How we test: what the scan settles, what it flags and what a person checks, criterion by criterion.
- How to test each criterion: step-by-step guides on the main site.