Guide · reviewed 2026-11-03
Why do I need ongoing accessibility monitoring?
Because a site that passed a check last month can fail this month: each deploy, theme update, plugin and new piece of content can bring accessibility problems back. Monitoring re-checks your important pages on a schedule and shows what is new and what is fixed, so problems are caught soon after they appear. Raasta’s monitoring is free for one site and five pages, checked monthly, and like any automated check it finds a large share of problems, not all.
How problems come back
- Deploys. A new component, a redesigned header or an updated library can remove a label or break keyboard access without anyone noticing.
- Content editors. New images go up without alt text, headings are chosen for their size, and a banner goes in with low-contrast text.
- Themes, plugins and apps. On Shopify, WordPress and similar platforms, an update to a theme or app changes your pages’ code for you.
- Third-party widgets. Chat, cookie and review widgets change on their supplier’s schedule, not yours.
How Raasta’s monitoring works
Sign in with a free DanixSoft account, add your site and verify that you own it with a meta tag, a file or a DNS TXT record. Then choose the pages to watch, by hand or by importing your sitemap. On a schedule, Raasta loads each page in headless Chrome, runs its JavaScript and checks it with axe-core, then shows the score over time and which issues are new and which are fixed since the last run. You can turn on an email report, with a one-click unsubscribe.
Free: 1 site, 5 pages, checked monthly. Site ($19 a month): 1 site, 100 pages, monthly. Pro ($49 a month): 3 sites, 250 pages each, weekly. Agency ($149 a month): 25 sites, 100 pages each, monthly, with printable client reports under your agency’s name. Your first site gets a 14-day Pro trial.
What monitoring cannot do
- It only checks what it can reach. Monitoring never signs in, so pages behind a login need the live-page check instead.
- It does not open menus or fill in forms. Pages are checked as they load. Test menus, dialogs and error states with the live-page check and by hand.
- It does not replace manual testing. Keyboard, screen reader and meaning checks still need a person, ideally when a new page type or component ships.
- It does not certify compliance. A good score is evidence of care, not a certificate.
Offering monitoring as an agency
For agencies, monitoring turns a one-off accessibility audit into a monthly service. Audit and fix each client site once, then add it to monitoring, review the new issues each month, fix them as part of a care plan, and send the client a printable report under your agency’s name. Be clear with clients that it covers automated checks, and price manual testing of new templates separately.
See the common failures and their fixes, the WCAG 2.2 guide or the accessibility statement generator.
Questions
How often should a site be checked?
At least monthly, and after every significant release. Sites that deploy often or have many editors benefit from weekly checks.
Why do I have to verify that I own the site?
So that scheduled checks only run on sites whose owners asked for them. Raasta’s one-off quick scan fetches only the single page a person requests.
Which pages should I monitor?
One or two of each page type (home, listing, product or article, contact form, checkout start) plus your most visited pages. Templates repeat, so a sample of each catches most problems.
How do I pay for a plan?
For now, payment is by bank transfer, JazzCash or Easypaisa, and the plan is switched on once payment is confirmed.