# Getting started with Accessibility

**Category:** [Accessibility](https://help.totalctrl.app/hc/totalctrl/totalctrl-help-center/en-US/categories/accessibility-1)
**Updated:** 2026-10-04

## Scan a site in three steps

- Open **Accessibility** and click **New Project**. Choose **Website**, then give it a name and the site's base URL (e.g. `https://example.com`). You can also create a **PDF** project to check documents instead — see the PDF/UA article.
- Open the project and click **Run scan**. The scan launches a real headless Chromium browser, renders each page, and runs the industry-standard **axe-core** rules engine against it.
- When the scan finishes you'll see a **score out of 100**, the number of issues by severity (critical / serious / moderate / minor), and every failing rule with the exact elements and WCAG success criteria involved.

## See exactly what failed

Under **Issues by rule**, select any rule to expand the concrete offending elements — the CSS selector, the exact HTML, and (for colour-contrast) the text/background colours with the measured ratio versus the required threshold. Most elements also include a **screenshot with the failing element highlighted**, so you can see where it is on the page.
## Export or turn issues into tickets

**Export** a scan to a Microsoft Excel workbook with three tabs — Summary, Issues by rule (one row per element), and Pages scanned — and either download it or save it straight to a connected cloud drive (e.g. Google Drive). Or click **Create tickets** to file one bug per failing rule into an **Issue Tracking** project, complete with the affected elements, colours, and screenshots; priority is set from each issue's impact.
## One scan, every framework

You don't run a separate scan per standard. A single scan is reported against **WCAG 2.2 AA**, U.S. **Section 508**, and EU **EN 301 549** at once — switch the profile on the report to see each view of the same results.
## Scans run in the background

Scanning is heavy, so it never runs on the web app itself — each scan is queued and executed by a dedicated worker. Large scans just take a little longer; you can leave the page and come back. The status updates live from *queued* → *running* → *completed*.

---

## Related Articles

- [Checking PDF documents (PDF/UA)](https://help.totalctrl.app/en-US/articles/accessibility-pdf-ua-1)
- [CLI & browser extension (developer tools)](https://help.totalctrl.app/en-US/articles/accessibility-cli-and-extension-1)
- [Scheduling, alerts & automation](https://help.totalctrl.app/en-US/articles/accessibility-automation)
- [Scan limits & fair use](https://help.totalctrl.app/en-US/articles/accessibility-limits)
- [VPAT / ACR reports & Accessibility Statements](https://help.totalctrl.app/en-US/articles/accessibility-reports-2)

---
[← Back to TotalCtrl Help Center](https://help.totalctrl.app/en-US/)