The service, part two
Monthly Website Accessibility Monitoring
A scheduled WCAG 2.1 AA scan of your web properties every month, regression checks on everything that changed, a report your administrators can file, and a timestamped record of when each issue was found and when the next scan verified it fixed.
Sources
Key takeaways
- Why monitor at all? Because websites change. A site that meets the standard at its baseline can drift out of it with one redesign, plugin update or batch of new PDFs.
- What runs every month: a full WCAG 2.1 AA scan, a comparison against your baseline, and human verification of anything new before it reaches the report.
- Who fixes things: your IT staff or web vendor. We find, they fix, we verify. The separation is the point.
- What the record shows: when each issue was found and when a later scan verified it fixed, kept as a running, dated history.
What does monthly website accessibility monitoring cover?
Everything in your property inventory, against the same 50 WCAG 2.1 Level A and AA checkpoints as the baseline. New pages, new documents and new third-party embeds enter the next scan automatically, because the content that creates new gaps is almost always content added after the audit.
In detail
Each month's results are compared against the baseline and the prior month. The comparison is what makes monitoring different from running a free scanner once a year: it tells you exactly what changed, which fixes held, and which update quietly reopened an issue that was closed in March. The checkpoints themselves are listed on the WCAG 2.1 AA checklist.
How does the found-and-verified record work?
Every finding carries the date it was found. When your team fixes it, the next scan re-tests it, and the record shows the date the fix was verified. We document that a fix happened by verifying it; we do not guess at fix dates, because we do not do the fixing and will not present a date we did not observe.
In detail
That dated history is the quiet value of the service. If a question ever comes, from a complainant, a regulator or your own board, the record shows a serious, continuing accessibility effort: what was found, when, what was fixed, and when the fix was confirmed. It is not, by itself, a legal determination of compliance, and we will never present it as one. What it is: evidence of the work, kept by an organization with no stake in the scores.
What lands in the monthly report?
Scan summary
Open issues by severity, what is new, what was fixed and verified, and the trend since your baseline.
Regression alerts
Issues that were closed and have come back, usually after a redesign, a theme update or a new form.
New-content findings
Pages, PDFs and embeds added since last month, tested and verified before they reach the report.
Assignments carried forward
Findings assigned to your IT staff or vendor stay on the report month to month until a scan verifies the fix.
Reports are written for two readers at once: the administrator who owns the obligation and the technical person who will act on it. No raw scanner exports, ever; a person reviews every report before it goes out.
Why should the monitor be independent?
Because when the company that built or hosts your website also grades it, every defect it misses saves it a repair. ADA Site Monitor sells no hosting, design or content services to the entities it monitors. We test, your vendor fixes, we verify, and neither of us answers to the other. The responsibility question, including the DOJ's own vendor example, is covered in our guide to vendor-run websites and in the DOJ's fact sheet.
What does monitoring cost?
It is quoted together with the initial assessment, priced from your inventory: the number of websites, page templates, portals and documents you actually have. The pricing page explains how the quote is built. Write to Monitor@ADAsiteMonitor.com to set up the scoping call.