Enterprise-scale crawling
Vendor cites coverage across 25,000+ pages per portfolio with 90M+ findings uncovered across customer programs. Most accessibility scanners cap out well below that scale or perform poorly on large portfolios.
Deque • Enterprise software
axe Monitor
axe Monitor scans staged and production sites continuously and tracks accessibility regressions over time.
Continuous accessibility monitoring at enterprise scale. Scheduled WCAG scans across thousands of pages with regression detection, executive-tier dashboards, technical-tier issue queues, and Jira integration. Available through Merito with crawl scoping, dashboard configuration, and Jira workflow design.
- Best for
- Product leaders responsible for accessibility scoring across web portfolios, Accessibility program managers running enterprise compliance programs, Site reliability engineers integrating accessibility monitoring into production observability
- Hosting
- SaaS
- Time to value
- 2 to 4 weeks
- Security posture
- GDPR, SAML SSO, audit logging
- Last reviewed
- 2026-05-03
What it is
axe Monitor in the enterprise stack
Production accessibility drift is a real failure mode. Releases land that reintroduce violations the audit team thought were fixed. Content updates change page structure in ways that regress assistive-technology compatibility. Third-party scripts inject DOM elements that fail WCAG. axe Monitor is the production-side bookend that detects that drift continuously rather than at the next quarterly audit cycle.
Coverage scales to enterprise portfolios. The vendor cites scanning across 25,000+ pages with 90M+ findings uncovered across customer programs. Scheduled scans run against staged or production sites at configured intervals. Outcome reports track accessibility scoring over time, so program-level trend lines surface alongside per-page issue queues.
Differentiated views matter at scale. Leadership gets executive scoring and trends. Engineering and QA teams get prioritized issue queues, per-page details, and Jira ticket creation. Same data, different audiences, different surfaces. Without that separation, executive reports drown in technical detail and engineering teams drown in roll-up metrics.
Merito frames axe Monitor as the production-side bookend to the developer-side tooling. The full accessibility program runs axe Linter at pre-commit, axe DevTools at code time, axe Auditor at structured audit time, and axe Monitor at production time. Customers buying Monitor without the rest are watching for issues they could have prevented earlier in the SDLC.
Ideal use cases
- Continuous WCAG scanning across enterprise web portfolios at scale
- Regression detection for accessibility issues introduced by code releases or content updates
- Executive-tier accessibility scoring and trend reporting
- Per-page issue queues for engineering and QA teams
- Jira ticket creation for prioritized accessibility findings
- Pre-release scanning of staged sites before deploy
What it is best at
Where axe Monitor earns its seat
Executive plus technical view separation
Leadership dashboards show accessibility scoring trends and program-level metrics. Technical dashboards show per-page issue queues with prioritized findings. Same data, different surfaces. Avoids the failure mode of one dashboard everyone hates.
Continuous monitoring catches drift
Quarterly audit cycles miss the accessibility regressions that ship between audits. Continuous scanning is the only way to detect drift in production traffic before users hit it.
Jira integration for remediation handoff
Findings flow into Jira tickets automatically with severity, WCAG criterion, and reproduction steps. Engineering teams receive accessibility findings in the same queue they triage every other defect.
axe-core ruleset consistency from production back to development
Findings in Monitor match the ruleset that axe DevTools and axe Linter use during development. Production findings show up as issues developers recognize from their pre-commit and CI runs, not as a separate language.
Core capabilities
axe Monitor capabilities, grouped by outcome
Continuous scanning at scale
Scheduled WCAG scans across enterprise portfolios with crawl-scope configuration.
Scheduled scan cycles
Configurable scan intervals (daily, weekly, custom). Each cycle covers the full configured portfolio with consistent crawl scope.
Enterprise-scale crawling
Scales to 25,000+ pages per portfolio with stable crawl performance. Vendor cites 90M+ findings uncovered across customer programs.
Crawl scope configuration
URL include/exclude patterns, depth limits, and authenticated-flow handling. Crawl scoping is where most accessibility monitoring deployments succeed or fail.
Staged plus production scanning
Scan staged sites before release as a release gate, scan production after release as drift detection. Same scan engine, different cycle cadence.
Differentiated dashboards and reporting
Executive-tier scoring and technical-tier issue queues built for different audiences.
Executive accessibility scoring
Roll-up accessibility scoring across the portfolio. Trend lines over time. Suitable for board, leadership, and risk-committee reporting.
Per-page technical detail
Per-page issue queues with prioritized findings, WCAG criterion mapping, severity, and reproduction steps. Suitable for engineering and QA triage.
Custom report templates
Customer-branded report templates with standard sections (executive summary, methodology, findings, trend lines) plus customer-specific extensions.
Outcome reports tracking trend lines
Audit-over-audit and scan-over-scan trend reports. Useful for proving the accessibility program is reducing risk over time.
Remediation workflow integration
Finding-level handoff into the team's existing remediation queue.
Jira ticket creation
Findings flow into Jira tickets with severity, WCAG criterion, page URL, and reproduction steps. Engineering teams triage in the same queue as other defects.
Prioritized issue queues
Findings prioritize by severity, WCAG conformance level, and (where configured) page traffic weight. Critical-path violations surface above background noise.
Verified-fix tracking
Subsequent scans detect when a previously-flagged issue has been resolved. Verified-fixed status flows back into the trend lines without manual reconciliation.
Where it fits in the stack
How axe Monitor connects to the rest of your landscape
Issue tracker integration (native)
NativeFirst-party integration with the issue tracker the engineering team uses for triage and remediation.
- JiraFindings flow into Jira tickets with severity, WCAG criterion, page URL, and reproduction steps.
axe portfolio integration (certified)
CertifiedReporting and ruleset alignment with the rest of the Deque axe portfolio.
- axe-core rulesetProduction findings use the same axe-core ruleset that axe DevTools and axe Linter use during development. Developers recognize the issues from their pre-commit and CI runs.
- axe AuditorMonitor findings inform audit-cycle planning. Audit teams scope manual cycles around the surface where Monitor is detecting persistent drift.
Identity and access management (custom)
CustomAuthenticated-flow scanning configuration patterns.
- SAML SSO providersAuthenticated scanning for logged-in pages typically requires service-account credentials or SSO impersonation. Configuration patterns are customer-specific.
- Service accountsDedicated service-account credentials with scoped permissions for crawl access. Common pattern for customers whose accessibility scope includes authenticated areas.
Deployment and implementation
How it rolls out
- Hosting
- SaaS
- Implementation complexity
- Moderate
- Typical time to value
- 2 to 4 weeks
- Prerequisites
- Defined portfolio scope (URLs, sub-domains, page count)
- Crawl access to staged or production sites (allow-list of Deque IPs may be required)
- Authenticated-flow handling defined where applicable (logged-in pages, SPA route handling)
- Existing issue tracker (Jira) for findings handoff
- Defined accessibility standard (WCAG 2.1, 2.2)
- What Merito usually handles
- Monitor runs SaaS by default. Crawl runs from Deque-hosted infrastructure against the customer's staged or production sites. Self-hosted scanning is available for regulated customers whose accessibility scope cannot leave the customer network; verify during scoping.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- axe Monitor is a subscription typically scoped on portfolio scale (page count under monitoring) and scan frequency (daily, weekly, custom). Multiple environment scopes (staged plus production) sit under one license. Pricing is not published; Deque gates commercial pricing through demo conversations.
- Editions and modules
axe Monitor
Full subscription with continuous scanning, executive plus technical dashboards, and Jira integration.
Best for: Enterprise accessibility programs with web portfolios above a few hundred pages and a need for continuous regression detection.
- Common expansion areas
- Larger portfolio coverage (page count) as web scope grows
- Higher scan frequency for faster regression detection
- Bundle with axe DevTools for the developer-tier of the program
- Bundle with axe Auditor for structured audit cycles between continuous scans
- Bundle with Deque University for accessibility training across the program
Merito services
How Merito helps you win with axe Monitor
Pick the engagement that matches where you are in the lifecycle.
01
Accessibility Compliance Program
WCAG, ADA, and Section 508 program delivery built around continuous monitoring. Audit cadence design, governance, and ongoing run.
Explore service02axe Monitor Implementation
License setup, crawl scope configuration, dashboard customization, Jira workflow design, executive-report template authoring, and program-team handover.
Explore service03Managed Services
Merito-operated continuous monitoring with dashboard maintenance, regression triage, and Jira workflow management on the customer's behalf.
Explore service04DevOps Consulting
Monitor wired into release-pipeline gating so staging-environment scans block deploys with critical accessibility regressions.
Explore service05Premium Support
Named engineer, priority SLAs, and release-time coverage on the axe Monitor rollout.
Explore service06Staff Augmentation
Merito-placed accessibility engineers experienced with axe Monitor crawl configuration and Jira workflow design.
Explore serviceaxe Monitor licensing
Continuous WCAG scanning at enterprise scale.
axe Monitor across staged and production portfolios up to 25,000+ pages, available through Merito with crawl-scope configuration, dashboard customization, and Jira workflow design.
Merito point of view
Quarterly audit cycles miss the regressions that ship between audits. Monitor is the production-side bookend.
Merito's position. Production accessibility drift is the failure mode that costs programs their audit-cycle conformance scoring. A release lands that reintroduces a fixed violation. A content update changes page structure in ways that regress assistive-technology compatibility. A third-party script injects DOM elements that fail WCAG. Without continuous monitoring, none of that surfaces until the next scheduled audit, by which point the user impact has already accrued.
Crawl scoping is where Monitor deployments succeed or fail. Site-wide scanning produces a lot of duplicate noise without good crawl configuration. Twenty-five thousand pages with the same shared header component produce the same finding twenty-five thousand times. Merito's standard rollout includes a crawl-scoping sprint that defines URL include/exclude patterns, depth limits, authenticated-flow handling, and finding-deduplication rules.
Executive plus technical dashboard separation matters at scale. Leadership wants accessibility scoring trends. Engineering wants prioritized per-page issue queues. Most accessibility monitoring deployments fail because one dashboard tries to serve both audiences and serves neither well. Monitor's separation is the right architecture; Merito designs the customer-specific dashboard layouts during rollout.
Monitor pairs with the rest of the axe portfolio. Programs running Monitor without axe DevTools are watching for issues developers could have caught before code shipped. Programs running Monitor without axe Auditor are watching for issues a structured audit cycle would have surfaced and remediated more comprehensively. Monitor is the production-side bookend; the four-product stack is the program.
What buyers usually underestimate
- Skipping the crawl-scoping sprint. Site-wide scanning without configuration produces noise that drowns the real findings.
- One dashboard for executives and engineers. Both audiences end up dissatisfied; the program loses credibility with leadership and tactical traction with engineering.
- Running Monitor without axe DevTools. Production-side detection of issues developers could have caught at code time is the most expensive way to find them.
- No Jira workflow design for accessibility findings. Tickets pile up in an unmanaged queue and the program quietly stalls.
- Treating Monitor scoring as the only accessibility metric. Scoring rises when fewer issues are detected, which is also what happens when the crawl config narrows scope. Watch trend lines, not snapshots.
Related from Merito
Continue exploring axe Monitor on Merito
Related solutions
Related services
Related products
- axe DevToolsDeveloper-tier runtime accessibility testing. Catches issues at code time before they reach production.
- axe LinterPre-commit static accessibility analysis. The leftmost-shift counterpart to Monitor's production-side detection.
- axe AuditorStructured manual audit cycles. Pairs with Monitor for the manual-versus-continuous coverage split.
Frequently Asked Questions
axe Monitor FAQs
Consultation request
Talk to Merito about axe Monitor
Share your web portfolio scale (page count), release cadence, authenticated-flow surface, and Jira setup. A Merito accessibility specialist follows up within one business day.
Crawl scoping
Where Monitor deployments succeed or fail
Site-wide scanning without crawl-scope configuration produces noise. Merito designs URL include/exclude patterns and authenticated-flow handling before the first scheduled scan.
Production bookend
One quadrant of four
Monitor is the production-side bookend to axe Linter, axe DevTools, and axe Auditor. Merito scopes the full quadrant set, not just the production tier.
Next step
Pick the portfolio scope. Merito scopes the crawl around it.
A Merito axe Monitor conversation starts with the portfolio (page count, sub-domains, authenticated areas), the release cadence, and the program team that owns the accessibility scoring.