Accesserty Pulse
Website accessibility maintenance
Know which live pages to review next.Pulse records interaction clues such as repeated keyboard focus loops or an overlay staying open after repeated Esc presses, so you have a place to start checking.
Free: basic events. Pro: a page-review list, scan details and a weekly report.
Start with one page to check
Data comes from pages where Pulse is installed and active, when visits meet event or scan conditions. Pulse does not crawl the whole site; an unlisted page is not a checked page.
Repeated clicks or Tab cycling through a small set of controls can give you a reason to try that page yourself. Check responses, focus movement and ways to close an overlay. These are review clues, not confirmed failures or root causes.
Pro orders its page-review list using collected interaction events and bounded scan summaries. Signal reports are reviewed separately and do not affect that order; a specific report of a blocked essential task can still deserve attention first.
When Pulse can help
More pages than you can check at once
Use the clues you have to choose one page and try a real task, rather than starting with an arbitrary page.
A site that keeps changing
Compare event periods and scan dates with release dates. The latest saved scan may not reflect a page you have just changed.
Review and follow-up with colleagues
Use page URLs, interaction clues and Pro scan details as a starting point, then record what you confirm in your existing issue tracker.
What to do with the clues
Setup is below. Once data arrives, start with one page in Console, your maintenance workspace.
Step 1. Look at events and scan dates
Free provides basic events; Pro adds a page-review list, scan details and weekly reports. Compare event periods and scan dates. Review Signal reports separately; the order is not a confirmed defect list.
Step 2. Try the task on the page
Try the flow with the keyboard and record expected and actual behavior. Selector examples in scan details help a developer find elements; they do not highlight elements on the website.
Step 3. Record the fix and arrange a re-test
Use your existing issue tracker to record reproduction steps, an owner and re-test results. Repeat the same task after the fix; fewer events or no new scan next week do not establish that the issue is resolved.
Basic events, or a page-review list?
Connect one site and check the data flow, then choose the review tools you need. Both plans require installation and verification; Pro also works for a single website.
Free
US$0
Connect one website to review basic events and associated Signal reports.
Pro
US$49 monthly or US$490 annually
Both billing options include a 14-day trial; check the terms shown at checkout.
Use a page-review list, scan details and weekly reports, even for a single website.
Start with one website on Free
You need access to the homepage HTML returned by your server; a colleague who deploys your site can help. Sign in to Console, your maintenance workspace, and register a public domain you are authorized to maintain.
Register the domain you maintain
Free supports one verified domain. Registration is configuration; install the script and complete verification before receiving data you can access.
Install the script and verify the homepage
Place the Console-generated static script in the homepage HTML returned by your server, then run verification in Console. This establishes maintenance access, not legal proof of ownership.
Review received data and choose a page to check
Data may arrive when visits to active Pulse pages meet collection conditions. Free provides basic events; Pro adds the priority list. Review Signal reports separately. ALLY applications are also available on Free and still require review.
Pulse does not record screens or mouse trails, or store form field contents. It still sends bounded events, processed page paths and element selectors. Before installing, review your site’s notices and any consent arrangements needed.
Learn how ALLY applications and ongoing maintenance work
Learn how Pulse handles website data
Turn weekly clues into review and re-testing
Website accessibility monitoring after launch
What an accessibility reporting channel should include
How to respond to accessibility reports
Frequently asked questions
After installation and verification, data may appear when visits to active Pulse pages meet event or scan conditions. A consent tool holding the script, no matching events or disabled scans can mean no new data. That does not mean the site has no barriers.
Free supports one verified domain, the latest 100 account-wide events, associated Signal reports and ALLY applications. Pro is US$49 monthly or US$490 annually, both with a 14-day trial. It adds up to five domains, priority page lists, scan details, the latest 1,000 account-wide events, Console weekly reports and optional English email. Event counts are viewing limits, not retention periods; check trial terms at checkout.
No. Pro shows a limited set of scan rules, guidance, impact, counts and text selectors a developer can use to find elements. The detail view shows at most ten rules and up to three selector examples per rule, not every affected element or a whole-site audit.
No. It combines interaction events from the last seven days with the latest saved scan summary of each page, compared with the previous one. Signal reports are reviewed separately and do not affect priority. Recent scans of the same URL are normally reused within 14 days, unless you choose “Mark fixed and rescan” in Console, which scans the page again on its next visit. Scan findings are not necessarily new this week. Pro includes the Console report; English email delivery is optional.
Clues include repeated clicks, possible keyboard dead interactions, focus reversals, repeated Esc presses with an overlay still open, possible keyboard traps, focus being pulled back and repeated form attempts. Eligible pages may also produce machine-detectable WCAG A/AA and best-practice scan summaries. An event is a reason to investigate, not proof of a failed task.
No. It does not record screens, replay sessions, collect mouse trails or store full page content or form field contents. It still sends bounded events, processed page paths, element selectors and scan summaries. Installers should arrange notices and any consent needed for their site.
No. Maintainers can review only private records associated with current verified domain access. Removing the domain ends that access; verification again, even with the same account, does not restore earlier private reports. Verification establishes maintenance access for Accesserty, not legal proof of ownership.
No. Interaction events and machine summaries are review clues, not a complete audit, assistive-technology test or real-user test. Pulse does not provide legal decisions or conformance proof. No events or scan findings do not establish that the whole site is accessible.
Pulse supports website accessibility maintenance after launch. Free provides basic events; Pro uses collected interaction events and bounded scan summaries to organize pages for human review. Signal reports are shown separately and do not affect the order. Pulse is not a general web analytics tool.
Maintainers with current verified Pulse domain access can apply for ALLY on either Free or Pro. Approval requires continued report handling; it is not page-by-page certification or a compliance guarantee, and it may be revoked if maintenance stops.