Skip to main content

Accessibility Monitor Site Settings Reference Guide

Learn how each Accessibility Monitor setting affects scanning behavior, monitoring frequency, crawl performance, and WCAG compliance testing.

Accessibility Monitor provides multiple settings that control how your website is scanned, monitored, and evaluated for accessibility issues.

  1. Sign in to your Accessibility Monitor account at https://scan.userway.org/login.

  2. In the left navigation menu, click Site Settings.

Expected Result

You can view and configure the Accessibility Monitor settings for your website.

Monitoring Frequency:

Controls how often automatic accessibility scans run against your website.

Option

Recommended Use

None

Disable automatic monitoring.

Daily

Websites with frequent content or code changes.

Every 3 Days

Active websites with regular updates.

Weekly

Standard business websites with moderate update schedules.

Bi-weekly

Websites with occasional updates.

Monthly

Mostly static websites.

Quarterly

Rarely updated websites.

Rate Limiting:

Regulates crawler speed to prevent excessive requests to your server.

Option

Recommended Use

None

Crawl at full speed.

Low

Light traffic environments.

Medium

Shared hosting or moderate server limitations.

High

Strict server limits, firewalls, or sensitive environments.

⚠️ Important: Enabling Static IP Scanning automatically applies rate limiting during scans.

Wait for Load: (Seconds Delay)

Specifies how long the scanner's headless browser waits after the initial page load before capturing the DOM snapshot and evaluating accessibility rules.

⚠️ Important: Setting an unnecessarily long delay will increase scan duration without improving results. Use the shortest delay that consistently captures the full page content.

Modern websites often continue loading content after the page initially appears. This includes:

  • Single Page Applications (SPA) built with React, Vue, or Angular

  • Client-side rendered content

  • AJAX-loaded components

  • Dynamic menus and navigation

  • Third-party widgets and plugins

  • Tracking scripts and analytics

  • Accessibility widgets and overlays

Adding a delay helps ensure these elements are fully rendered before the accessibility scan begins.

Duration

Recommended Use

3 Seconds (Default)

Standard websites, static pages, or server-side rendered (SSR) websites that load quickly and do not rely heavily on delayed scripts.

5-10 Seconds

E-commerce websites, moderately complex applications, or Single Page Applications where dynamic content, product grids, filters, or popups require additional time to load.

15+ Seconds

Large, resource-intensive websites with multiple third-party integrations, complex widgets, or pages that perform several API requests before displaying content.

💡 Tip: If accessibility scans appear to miss dynamically loaded content, increase the wait time to allow all page elements to finish rendering before evaluation.

Scan From: (Geolocation / Static IP)

Controls the geographic location and IP address used when Accessibility Monitor scans your website. The scanner can run from either:

  • Regional Locations such as the United States, Canada, or the United Kingdom.

  • Static IP Locations, which use dedicated IP addresses that can be allowlisted by firewalls, VPNs, or security systems.

Option Type

Purpose

United States

Standard scan originating from the United States.

Canada

Standard scan originating from Canada.

United Kingdom

Standard scan originating from the United Kingdom.

United States Static IP

Uses dedicated, allowlistable IP addresses in the United States.

Canada Static IP

Uses dedicated, allowlistable IP addresses in Canada.

United Kingdom Static IP

Uses dedicated, allowlistable IP addresses in the United Kingdom.

Static IP Addresses

Organizations that restrict access through firewalls, VPNs, security gateways, or IP allowlists can use a Static IP location and add the corresponding IP addresses to their approved list.

Region

Static IP Addresses

United States Static IP

35.85.205.119, 52.38.192.218

Canada Static IP

3.98.5.100, 35.182.102.242

United Kingdom Static IP

18.134.223.209, 18.169.120.50

When to Use Standard Locations

Use a standard location when you want to:

  • Scan the website from a specific geographic region.

  • Verify region-specific content, languages, or currencies.

  • Test how the website appears to visitors in a particular market.

  • No firewall or IP allowlisting is required.

When to Use Static IP Locations

Use a Static IP location when:

  • The website is protected by a firewall.

  • The website is accessible only through a VPN or network allowlist.

  • Security policies require known source IP addresses.

  • The scanner is being blocked by Cloudflare, WAF rules, or network security controls.

Scroll:

Simulates scrolling down the page before accessibility evaluation begins.

Setting

Recommended Use

ON

Websites using lazy loading, deferred content, or infinite scrolling.

OFF

Websites where all content loads immediately.

💡 Tip: Turn this setting on for websites that load content as users scroll.

URL Params:

Controls whether the crawler evaluates URLs containing query parameters.

Examples:

  • ?id=123

  • ?category=blue

  • ?page=2

Setting

Recommended Use

ON

Query parameters generate unique content and pages that should be scanned independently.

OFF

Query parameters generate duplicate or highly similar pages that do not need separate evaluation.

Visible:

Controls whether the website appears in Accessibility Monitor reports and dashboards.

Setting

Result

ON

Website appears in reports, dashboards, and metrics.

OFF

Website is hidden from reporting views while retaining its configuration.

Common use cases include staging environments, internal testing websites, or temporarily inactive projects.

Scan AAA:

Enables testing against WCAG Level AAA success criteria in addition to Level A and Level AA rules.

Setting

Recommended Use

ON

Organizations that specifically require WCAG AAA evaluation.

OFF

Organizations targeting WCAG 2.1 or WCAG 2.2 Level AA compliance.

⚠️ Important: Most accessibility regulations and standards, including ADA, Section 508, and EAA-related compliance requirements, are based on WCAG Level AA rather than Level AAA.

Need more help?

Contact the UserWay Support Team — we're here to assist you.

Get in touch with UserWay Support.

Did this answer your question?