Compliance Monitoring
Catch regressions before your customers do
Scheduled baseline scans, on-demand rescans after deploys, diff reports that separate theme bugs from content edits, and alerts you control.
$1,200/quarter
Includes 4 hours of remediation work per quarter. Additional hours billed at the retainer rate.
Timeline: Ongoing, monthly baseline scans
How monitoring runs
Scheduled scans dispatch every 15 minutes. When your next run comes due, a baseline scan of your pinned page set executes automatically and diffs against your last run.
Step 1
Schedule
We configure a scan schedule on your storefront (daily, weekly, monthly, or quarterly) with the notification mode you pick. Nothing is installed on your store.
Step 2
Scan
Our worker scans on the schedule, or on demand after a theme deploy. Each run reopens home, cart, search, contact, one collection, and one product page and the pinned template sample from your baseline so counts stay comparable.
Step 3
Diff
New and resolved violations are separated into template regressions (your theme or an app) and page-specific content changes from merchandising.
Step 4
Alert
Email and optional Slack alerts fire based on your notify settings: every scan, regressions only, monthly summary, or regressions plus monthly.
What the retainer actually buys
Every panel below is the live product or a live render of the real notification, using six months of scan history from Tosche Station Outfitters.
Is the storefront getting safer, or drifting?
One chart answers the question a quarterly invoice has to justify. Six scheduled scans show violations falling through remediation, then an uptick when a newly installed app shipped fresh violations into the collection template.
Try this
- Hover a point to read the critical, serious, moderate, and minor split.
- Look at the final point: that is the regression detailed below.
Violations Over Time
Hover a severity to highlight its line. Click to keep it highlighted and read it alone in the tooltip.
A regression, caught without anyone looking
When a scan finds new violations, the diff separates template regressions (your theme or an app) from page-specific content changes, so you know whether it is a developer ticket or a merchandising fix. The likely cause is named, not left for you to work out.
Try this
- Note the template vs page-specific split: that decides who owns the fix.
- Compare the new and resolved counts against the prior baseline.
Likely cause: Theme app embed installed on the collection template
- Template regressiontemplate: collectionserious
A newly installed upsell app injects two unlabeled buttons and one untitled iframe into every collection page.
- Page-specific changetemplate: pagecritical
A merchandiser published a new landing page with three images missing alt text.
The alert that lands in your inbox
Email is the default and Slack is available for teams that would rather keep it in a channel. Both name the rule, the impact, the template, and the likely cause, then link to the full diff. Alert volume is a per-schedule setting, so this does not become another ignored inbox rule.
- From
- Cascadia Marquee monitoring
- To
- web@toschestation.example
- Subject
- 6 new accessibility violations on toschestation.example
Your monthly scan found new issues
Total violations moved from 8 to 13 since the February baseline. Two of the new findings are critical.
What changed
- Buttons must have discernible text (serious, 2 elements) on the collection template. New since last scan.
- Images must have alternate text (critical, 3 elements) on a newly published landing page.
- Frames must have a title (moderate, 1 element) from an app embed.
- Form elements must have labels resolved on the cart template.
Likely cause: a theme app embed was installed on the collection template between scans. Full diff and the failing selectors are in your report.
View the full report
Cascadia MonitoringApp9:02 AM
Accessibility regression on toschestation.example
- Total: 8 to 13 (+5)
- Critical: 0 to 2
- Template: collection
- Scan: monthly scheduled
Open report
Your schedule and how loud it is
The plan badge in your dashboard carries the host, the cadence, and the next scheduled run. You choose the cadence and the notification mode when the plan starts, and you can change either one.
Try this
- Hover or focus the plan badge to open the schedule detail.
- Pick the notify mode that matches how your team works.
- Cadence
- monthly
- Last run
- August 23, 2026
- Next run
- September 22, 2026
Every scan
An email after each scheduled scan, whether anything changed or not.
Regressions only
Email only when a scan finds new violations since the last baseline.
Monthly summary
One roll-up email per month, regardless of scan frequency.
Regressions plus monthly
Immediate regression alerts plus a monthly summary. Most common choice.
How monitoring is set up
A recurring plan should be specific about what runs, how often, and who hears about it.
- Cadence
- Daily, weekly, monthly, or quarterly, your choice
- On demand
- Unlimited rescans from your dashboard, so you can check a theme deploy or an app install the day it ships.
- Page set
- Each scheduled run rediscovers your sitemap and runs a fresh template-aware sample up to your plan cap, so new pages and templates are included. Results are diffed against the prior scan for regressions.
- Automated
- axe-core 4.11 (WCAG 2.0 A/AA, 2.1 AA, and selected 2.2 AA rules) plus IBM Equal Access checker
- Browser
- Headless Chromium via Playwright (1280 by 800 viewport). Automated scans do not run in Chrome, Safari, or Firefox.
- Diffing
- Each run is compared against the previous scan to separate genuinely new violations from ones already on your plan.
- Notifications
- Email by default, Slack optional. Four volume modes, changeable at any time.
- Included hours
- 4 remediation hours per quarter for regressions, plus an annual full manual re-audit.
What this tier does not include
- Monitoring does not fix issues on its own. Included remediation hours cover regressions introduced during the quarter; larger work is quoted.
- Scans reuse the must-pass URLs and template sample from your baseline audit. Adding templates or subdomains changes the scope.
- Violations inside third-party app iframes are reported but owned by that vendor.
- Alerts are technical findings, not legal notices or a compliance guarantee.
What you receive
- Scheduled baseline scans on your chosen cadence
- Unlimited on-demand rescans after deploys and app installs
- Diff reports with template vs page-specific classification
- Severity-ranked new violations with the likely cause named
- Violations-over-time trend chart and full scan history
- Email and optional Slack alerts with four volume modes
- 4 remediation hours per quarter
- Annual full-stack manual re-audit
- Slack channel for accessibility questions
Common questions
You choose the notify mode: every completed scan, regressions only, a monthly summary, or regressions plus monthly. Most clients pick regressions only or regressions plus monthly.
Stop guessing whether your storefront is still accessible
Monitoring turns compliance into a measurable baseline with alerts you control.