Accesserty Pulse
Interaction monitoring and detectable accessibility risks for live websitesAdd a lightweight script to track rage clicks, blocked keyboard interactions, focus reversals, failed Escape attempts, and repeated form submissions. Pulse pairs those signals with page-level scan summaries to help teams decide what to investigate first.
Find where people may be struggling
Analytics can show that someone left a page, but not always what happened first. Pulse captures a focused set of observable interaction signals and adds a page-level automated accessibility summary:
Rage clicks: repeated clicks on the same element within a short time, which may indicate that a button, link, or interactive area did not respond as expected.
Keyboard dead interactions: Enter or Space is pressed on a non-native interactive element, which may indicate that something looks operable but lacks correct interaction semantics.
Focus U-turns and Escape failures: records quick focus backtracking and repeated Escape attempts, helping teams inspect whether keyboard flows, dialogs, or overlays are trapping users.
Repeated form attempts: repeated submit or button actions after input may indicate unclear validation, field rules, or process feedback.
Page accessibility scan summaries: when users open a page with Pulse installed, Pulse runs axe-core in the browser at a low frequency; the same URL and scan version are not scanned again within 14 days. It summarizes machine-detectable WCAG A/AA and best-practice risks, but is not a full WCAG 2.2 AA audit or a legal compliance decision.
Who Is Accesserty Pulse For?
- Website Owners
When support teams receive a vague report about a form or service flow, use Pulse to check for repeated clicks, blocked keyboard interactions, or repeated form attempts.
- PMs & Designers
When reviewing flows and interaction design, Pulse event logs can point teams to places that deserve another look at design, copy, error messages, or interaction states.
- Developers & QA
Review event types, affected elements, URLs, and timing in production or staging to turn a vague usability concern into a concrete place to investigate.
How to Use Accesserty Pulse?
Register a domain, install the lightweight script, and begin collecting interaction events and page accessibility summaries.
- Step 1. Go to Console
In the Console, set up the domains you want to monitor. (Login required)
- Step 2. Embed Lightweight Code
Place the <script> snippet generated in Console on your site. Behavior events and page scan summaries are stored with your view key and domain.
- Step 3. Get Insights
In Console, review page accessibility scan summaries, trend charts, behavior distribution, common locations, and raw event logs.
Choose the plan that fits
Start with Free to establish domain verification and report handling. Upgrade when you need complete scan details or several domains.
Free
US$0
For verifying one domain, reviewing interaction events, and establishing a Signal report-handling workflow.
- 1 verified domain
- Latest 100 interaction events
- Receive and handle Signal reports
- Apply for Accesserty ALLY
- Does not include complete scan summaries or page issue lists
Pro
US$49 monthly or US$490 annually
For teams managing several domains that need complete page risk details and regular summaries.
- Up to 5 verified domains
- Latest 1,000 interaction events
- Complete scan summaries and page issue lists
- Optional weekly Signal/Pulse email report
- Also includes Signal report handling and ALLY applications
Verify the domains you maintain with Pulse
Pulse surfaces signs of interaction difficulty and page scan summaries. It also verifies domains for Signal reporting, helping reports reach the team that actually maintains the site.
- Register maintained domains
Sign in to Console and enter the domains you maintain, such as example.com.
- Install the Pulse script
Place the generated script on that domain. After the first Pulse event is received, the domain is treated as verified.
- Receive Signal reports and apply for ALLY
Verified domains can review and handle Signal reports in Console and apply for ALLY when the site is actively maintaining accessibility. ALLY is a reviewed maintenance signal, not an accessibility certification.
Frequently asked questions
Maintainers of verified domains can apply for ALLY. After approval, they are expected to keep reviewing and handling Signal reports and may receive spot checks and follow-up reminders. ALLY is not an accessibility certification or compliance guarantee, and it may be revoked when active maintenance does not continue.
Accesserty Pulse monitors interaction signals and detectable accessibility risks on live websites. After you add a lightweight script, it records rage clicks, blocked keyboard interactions, focus reversals, failed Escape attempts, and repeated form submissions, then pairs them with machine-detectable WCAG A/AA and best-practice risk summaries.
Free supports one domain, the latest 100 events, Signal report handling, and ALLY applications. Pro costs US$49 monthly or US$490 annually and adds up to five domains, the latest 1,000 events, complete scan summaries, page issue lists, an in-Console weekly report, and an optional weekly email report.
Traditional analytics can show that someone left a page, but not what happened first. Pulse captures a focused set of interaction signals so teams can identify the pages and controls that deserve investigation.
Rage clicks, blocked keyboard interactions, focus reversals, failed Escape attempts, and repeated form submissions, plus a page-level summary of automatically detectable WCAG A/AA and best-practice risks.
No. Pulse’s automated summary only covers machine-detectable issues. It helps you prioritise which pages to inspect first; it does not replace expert review or real-user testing.