← Help

How do I scan a page or repository for free?

The free scanner checks any public web page or GitHub repository for accessibility issues. No account is needed, and every report gets a permanent link you can share with your team.

Run a scan

  1. Go to app.accesslint.com/scan.
  2. Enter a page URL (like example.com/pricing) or a repository (like github.com/owner/repo).
  3. Click Scan.

Page scans

For a URL, AccessLint loads the page in a real browser and runs its automated WCAG checks against the rendered result. Each issue in the report shows the rule, its impact (critical, serious, moderate, or minor), the WCAG level, the affected elements with an HTML snippet, and a link explaining the rule.

A few boundaries:

Repository scans

For a GitHub repository, AccessLint fetches the default branch and runs static checks on its UI source files, the same file types covered in pull request reviews. Static checks catch what’s visible in the markup: missing alt text, unlabeled controls, missing landmarks, and similar.

Public repositories work with no setup. For a private repository, install the AccessLint GitHub App. Installing is what grants AccessLint permission to read it.

What a clean scan means (and doesn’t)

Automated checks find the issues a machine can detect: roughly a third to half of WCAG success criteria. They can’t judge keyboard flows, focus order, the quality of alternate text, or whether content makes sense to a screen reader user. Likewise, static repo checks can’t see issues that only appear on a rendered page, like insufficient color contrast. A clean scan is a good start, not a compliance verdict.

For continuous coverage instead of one-off scans, AccessLint reviews every pull request and monitors live journeys on a schedule.