Parameters

Field	What It Does	UI Default
URL	Start URL to scan. If you enter without scheme, app uses HTTPS. Not shown in URL List mode — the first URL from the uploaded file is used automatically.	(empty)
Mode	single scans one page, crawl follows same-site links, sitemap reads sitemap URLs, URL List scans a curated set of URLs from an uploaded file.	crawl
Scan Title	Optional label shown in the report header. Only available in URL List mode. If left blank, the first URL from the list is used as the title.	(empty)
URL List File	Upload a .txt, .csv, or .xlsx/.xls file containing the URLs to scan. Text/CSV: one URL per line, lines starting with # are ignored. Excel: each row is scanned across its first 10 columns for the first valid URL. Only the exact URLs provided are scanned — no link following or depth crawling. Capped by Max pages.	—
Audit Profile	WCAG uses WCAG tag set only. Extended runs wider axe rule set.	WCAG
Report Audience	Developer shows full technical detail. Client shows simplified executive-friendly report.	Developer
WCAG	Target version for tags.	2.2
Level	Conformance level tag filter.	AA
Strict	N score uses critical+serious only. Y uses all confirmed violations. NN uses critical only. YM uses confirmed violations plus manual-review (incomplete).	N
Scoring weights	Severity weights used in scoring: critical=10, serious=6, moderate=3, minor=1. In YM mode, these same weights are also applied to manual-review (incomplete) items.	—
Platform	Viewport/device profile used for scan rendering.	desktop
Settle ms	Extra wait after page load before audit starts.	2000
Max pages	Maximum pages collected in crawl/sitemap mode, or maximum URLs scanned in URL List mode.	50
Max depth	Maximum crawl depth from the start URL. Not used in URL List mode.	3
Sitemap URL	Optional explicit sitemap URL when mode is sitemap.	(empty)
Exclude Rules	Comma-separated axe rule IDs to disable, e.g. color-contrast,target-size.	(empty)
Skip linked PDFs	Skips PDF links encountered during crawling.	Checked

Typical Runs

• Single page: Set Mode to single and enter page URL.
• Site crawl: Keep Mode as crawl; adjust Max pages and Max depth.
• Sitemap scan: Set Mode to sitemap and provide sitemap URL if needed.
• Curated URL list: Set Mode to URL List, optionally enter a Scan Title, then upload a .txt or .xlsx file. Each URL in the file is scanned individually — no crawling or link following occurs.

Scheduling Jobs

Click Schedule Job (below the Run Scan button) to expand the scheduling panel. Configure the scan parameters as usual, then set schedule options and click Confirm Schedule.

Field	What It Does
Frequency	Once fires on a specific date. Weekly repeats on selected day(s). Monthly repeats on a chosen day of each month. Quarterly repeats on a chosen day every quarter.
Date	For Once: the calendar date on which to run the scan.
Day(s) of week	For Weekly: one or more days (Sun–Sat) on which to run.
Day of month	For Monthly / Quarterly: which day of the month to run (1–28; capped at 28 to avoid month-end gaps).
Starting month	For Quarterly: selects which set of months in the year — e.g. Jan/Apr/Jul/Oct, Feb/May/Aug/Nov, or Mar/Jun/Sep/Dec.
Time	Wall-clock time in the selected timezone when the scan fires.
Timezone	The timezone used to interpret the scheduled time. Defaults to Eastern (ET).
Notification Email(s)	Comma-separated email addresses that receive a confirmation on creation and a result notification after each run.

• Active schedules appear pinned at the top of the Jobs list with a SCHEDULED badge. Use the Scheduled filter to see only schedule entries.
• Click the ✕ button on a schedule card to cancel it (it stays visible with a CANCELED badge). Click the trash icon to remove a canceled/done schedule permanently.
• Result notification emails include a link to the report and a note that reports are deleted after 30 days.
• Email delivery requires the SENDGRID_API_KEY environment variable to be set on the server. If not set, schedules still run but no emails are sent.
• Set PUBLIC_URL (e.g. https://dex.sprucetech.com) on the server so report links in emails are absolute.
• Schedule definitions are stored in data/schedules/ and are not subject to the job retention sweep.

Compliance History

The Compliance History page tracks accessibility scores over time for URLs you designate. Use it to demonstrate improvement trends or catch regressions.

Feature	How It Works
Tracking a scan	Expand a completed job card in the Jobs list and check Include in compliance history. The scan is then included in the trend chart for that URL and scan settings combination.
Scheduled runs	Scheduled jobs default to Include all runs in compliance history (checked). Uncheck it in the Schedule Options panel before confirming if you do not want scheduled runs counted.
URL identity	Each URL is tracked per unique combination of: URL, WCAG version, Level, Mode, and Audience. The same URL scanned at WCAG 2.1 AA and WCAG 2.2 AA will appear as two separate tracked entries.
Drop threshold	A data point is flagged in red when the score drops by at least this many points compared to the previous run. Default is 5. You can change it per URL from the Compliance History page — it is saved on the server.
Chart	Blue line = score over time. Red dot = drop ≥ threshold. Purple dot = scheduled run. Gray dot = manual run. Click any data point to open its report (if not yet expired).
Time range	Use All / 90d / 30d buttons to filter the chart to a window.
Duplicate schedules	Creating a second active schedule for the same URL+WCAG+Level+Mode+Audience combination is blocked. Cancel the existing schedule first, or change one of the scan settings.
Editing a schedule	Click the pencil icon on an active schedule card to edit its frequency, time, timezone, notification emails, and compliance history setting. The URL and scan parameters cannot be changed — create a new schedule for that.

Notes

• Automated scans detect many issues, but not all accessibility requirements; manual review is still required.
• If crawl only finds one page on protected sites, bot/challenge protection (for example Cloudflare) may be blocking traversal.
• Run history is available from Reports Dashboard.
• Powered by axe-core.