GatekeeperQA

GatekeeperQA / Testing resources

FREE AVAILABLE NOW

Free accessibility scanner: find issues and verify your fixes.

Finding an issue is only the start. GatekeeperQA helps testers inspect the evidence, explain a fix, and record what happened after a retest.

Scan a page for free

How to run your first accessibility scan

  1. Open the scanner and enter a public page you own or have permission to test.
  2. Confirm permission and start the scan. Wait for the report to finish; check for incomplete pages before interpreting results.
  3. Inspect a finding's element and HTML evidence. For an unlabeled field, follow the missing form labels guide.
  4. Fix the issue, repeat the scan on the same URL and page state, and record keyboard and screen-reader checks separately.

What the online scanner checks

GatekeeperQA uses Playwright and axe-core to inspect the initially loaded state of a public webpage for automatically detectable WCAG 2.1 and 2.2 A/AA issues. Findings can include missing accessible names, missing form labels, and text contrast problems where the tool can determine the rendered colors.

Use it on a website you own or have permission to test. Enter one public URL as a guest. A free account can submit up to five URLs from the same website in one run. The scanner checks those URLs; it does not crawl every linked page or sign into private application journeys.

What you get in the report

Explore a labeled example report before spending a scan allowance. The sample PDF (opens in a new tab) shows the downloadable layout. PDF downloads are not currently validated as fully accessible documents; use the on-screen findings or HTML report as another reading format.

Save the testing work, too

Sign in with an email code to keep your latest 10 reports for up to 30 days. Record reviewer notes and evidence, use Open, Needs review, Fixed, or Retest needed statuses, and filter the review by page, severity, rule, and status. Download your reviewed copy before retention expires.

Copy a finding into a bug ticket, or export all or filtered items as CSV. Compare completed scans of exactly the same page URLs and attach retest evidence. A finding that disappears is not automatically considered fixed: the page state or element location may have changed.

Free scanning limits

Guests receive 2 page scans per browser per UTC day. Free accounts receive 5 page scans per UTC day. A two-page scan uses two page scans. Shared limits are 50 page attempts per day, 500 per calendar month, and 8 per network per day. Scans may queue or become unavailable when capacity is used. Failed or incomplete pages restore personal allowance; shared safety limits still count attempts.

Pro is available at $19.99/month or $191/year; sign in to choose a plan and continue to Stripe checkout. Shared team workspaces are not available. Email-code sign-in supports work email addresses, but Outlook delivery is under investigation; check Junk if a code is missing.

Example: from a failed scan to a useful fix

Our owned demonstration page contained an empty Checkout button. The saved CLI baseline recorded one critical button-name finding. After adding visible button text, the same fixture returned zero confirmed findings. This is a narrow, reproducible example, not evidence that an entire site is accessible.

Read the case study and download both reports. For form fields, use the missing-label guide with HTML examples and a retest record.

Choose the right starting point

What automation cannot conclude

A passing scan does not establish full WCAG or Section 508 conformance. Keyboard operation, focus order, screen-reader behavior, content meaning, and changing page states need human evaluation. The product is not a DHS-approved or certified assessment service.

Follow the tester workflow from scan to verified fix, or send us a question.