These Scan Settings give you greater control over the state of a web page before your accessibility audit begins, ensuring the scan is comprehensive and accurate, especially for complex or dynamic sites.
Scan Delay
Scan Delay sets a waiting period or condition that must be met after the page initially loads but before the scanner starts checking for accessibility issues.
Its main purpose is to account for dynamic content (like pop-ups, data loaded from an API, or animations) that appears a few moments after the page renders. Without a delay, the scanner might miss checking this critical, late-loading content.
Option | Description | Rationale |
None (Default) | The scan initiates immediately once the page's base document is loaded. | Fastest option; best for static pages or if you're sure all content loads instantly. |
Element is present | The scan waits until a specified HTML element (identified by a CSS selector, like \#main-content or .product-list) appears on the page. | Ideal for pages where you know a crucial piece of content takes a variable amount of time to load. The scan only starts when the content is guaranteed to be there. |
Time delay | The scan waits for a fixed number of milliseconds (e.g., 5000ms = 5 seconds) before proceeding. | Useful when you know the approximate time all dynamic content takes to load, providing a simple, reliable buffer. |
Page Scroll
Page Scroll controls the scanner's view of a page, ensuring that all relevant content is loaded and available in the viewport (the visible area of the browser window) before the scan starts.
This is important because some content on modern websites is lazy-loaded, which means it only appears or fully renders once the user scrolls it into view.
Option | Description | Rationale |
No scroll (Default) | The scanner only checks the content visible in the initial viewport. | Fastest option; only recommended if the page content is minimal or guaranteed to not use lazy loading. |
Scroll to page end | The scanner automatically scrolls down, until it reaches the very bottom of the page. | Guarantees that all lazy-loaded images, components, or entire sections are triggered and rendered for a complete scan. |
Scroll to a specific element | The scanner scrolls just enough to bring a specified element (via its selector) into the viewport. | Useful for targeting a specific, late-loading component (like a footer, a comment section, or a "Load More" button) without needing to load the entire page. |
Query Parameters
Query Parameters allows you to add key-value pairs to the URL (e.g., ?mode=dark&test=true) that the scanner uses to load the page.
This is vital for testing the accessibility of a page under specific, non-default configurations that are controlled by the URL, such as different user roles, themes, or page states.
1. Key-Value Query Parameter
This is the actual parameter you want to add to the URL.
Example: If the base URL is example.com/products, adding the parameter page\_number=1 results in the scanner loading the URL: example.com/products?page_number=1.
Purpose: This allows you to test different conditional content (e.g., the second page of a search result, a dark mode setting, or a different layout for a signed-in user) to ensure accessibility issues aren't introduced in these states.
2. Scope
Scope determines which pages the specified query parameter will be applied to during a multi-page scan.
Page: The query parameter is only added to the single, initial URL you provide to the scanner. Any subsequent linked pages found during the scan will be visited without the parameter.
Pages: The query parameter is added to every URL that the scanner visits within the defined scan scope (e.g., all pages on a certain domain). This is necessary if you are scanning an entire site that requires a specific parameter (like a login session or a theme setting) to maintain a consistent state across all pages.