Scanning

Single page and site crawl

A single-page scan analyzes one URL. A crawl discovers same-origin pages subject to depth, requested page count, plan limits, and execution time. The current crawl request accepts at most 500 pages; a requested maximum does not guarantee all pages will be reached.

Large or slow sites can produce partial coverage. Review pages scanned, errors, and the outcome before using the result. An interrupted browser crawl is not currently guaranteed to resume automatically. Reduce the requested scope and retry when appropriate.

• Single-page testing
• Site crawl

Interpret the findings

Critical, serious, moderate, and minor describe the impact reported by the scanning engine. Prioritize findings in the context of essential user journeys, not severity alone.

Open affected elements for selectors, HTML evidence, and failure details. AI explanations and fixes depend on enabled features, provider availability, and credits. Review generated code before applying it; RegLayer does not automatically deploy a suggested fix to your website.

The score summarizes the automated checks that ran. It is not a percentage of legal compliance or a certification. Automated checks cannot cover every WCAG requirement, assistive technology, or interaction.

Policy rules without detected findings counts rules with no matched automated finding; it is not WCAG coverage. Rules may still need manual assessment. A single scan has a measured score but no change to compare until another scan completes.

From scan results, Manual-test the rest carries the scan ID into the manual-testing form. Review it and start the audit explicitly; opening the form does not create an audit.

New scans require scanning permission in the selected workspace. A read-only role sees the restriction before entering a URL. If access cannot be checked, retry after the connection recovers or choose an available workspace; the server still checks permission on every scan request.

• Review violations
• Manual testing

Authenticated pages and sensitive data

Where enabled, saved authentication settings support scanning signed-in pages. Use a dedicated, least-privileged test account and confirm that scanning is authorized. Findings, screenshots, and captured HTML may contain sensitive page content.

Keep credentials out of URLs, screenshots shared publicly, issue descriptions, and source control. A login failure or redirect can prevent meaningful coverage even when the site itself is reachable.

• Configure a crawl

Configured base limits

Base quotas come from the same configuration used by the application. Unlimited plan quota does not remove request, resource, or timeout limits. Owners and admins may have different monthly scan allowances.

• Check current allowance
• Reports and comparison