Accesserty Pulse
Live website accessibility maintenance, ordered by the pages to review firstAdd one lightweight script. Pulse organizes accessibility reports, interaction-difficulty clues, and low-frequency page scan summaries so maintainers know which live pages deserve review first.
Turn live-site signals into a maintenance order
Live websites keep changing. Content, forms, menus, authenticated states, third-party components, and campaign pages can introduce new barriers after release. Pulse is not about adding more numbers; it helps maintainers decide where to look first.
Pulse brings three records into one maintenance context: user reports, interaction-difficulty events, and machine-detectable page risk summaries. When several signals point to the same live page, maintainers have a clearer reason to review it first.
In the Accesserty system, Pulse helps make post-launch accessibility maintenance more visible by combining recent usage events, reports, page summaries, and scan signals into pages worth reviewing first.
Pulse does not record sessions, act as a heatmap, or provide a complete WCAG 2.2 AA audit, assistive-technology test, or legal compliance decision. It provides maintenance clues so human review can start from the right pages.
Who Is Accesserty Pulse For?
- Website Owners
For people who need accessibility reports, interaction clues, and scan summaries turned into a practical page review order.
- PMs & Designers
See which live flow, copy, error message, or interaction state deserves another look first.
- Developers & QA
Use URLs, elements, event types, timing clues, and latest scan summaries to start review from a clearer place.
How to Use Accesserty Pulse?
Start with one actively claimed domain and turn live-site signals into a weekly maintenance rhythm.
- Step 1. Go to Console
Register a public domain you are authorized to maintain, install the static Pulse script, and verify the homepage installation in Console. This claim controls data access; it is not legal proof of ownership. Free supports one verified domain.
- Step 2. Embed Lightweight Code
Install the <script> snippet from Console. Pulse collects bounded interaction-difficulty events and low-frequency scan summaries, not form contents, full page content, screen recordings, or session replay.
- Step 3. Review the pages that deserve attention first
Use Free for basic events and Signal reports. Upgrade to Pro when you need multiple domains, priority page lists, complete summaries, and weekly reports that keep review moving.
Choose the plan that fits
Start with Free to confirm installation, the active domain claim, and Signal reports. Upgrade to Pro when you actually need more domains and a recurring review rhythm.
Free
US$0
For claiming one domain and confirming Signal reports for that active claim can be reviewed in Console.
- 1 actively claimed domain
- Latest 100 interaction-event records
- Receive and handle Signal reports
- Apply for Accesserty ALLY
- Priority page lists, complete scan summaries, and weekly reports are not included
Pro
US$49 monthly or US$490 annually; both billing options include a 14-day trial
For maintainers who need to track several domains, know which pages to review first, and use a weekly summary to stay on course.
- Up to 5 actively claimed domains
- Latest 1,000 interaction-event records
- Priority page lists and complete scan summaries
- In-Console weekly report and optional email summary
- Also includes Signal report handling and ALLY applications
Claim the domains you maintain with Pulse
Pulse surfaces signs of interaction difficulty and page scan summaries. Its active claim also controls which maintainer can review Signal reports for a domain.
- Register maintained domains
Sign in to Console and enter the domains you maintain, such as example.com.
- Install the Pulse script
Place the generated static script on that domain and verify the homepage installation in Console. Registration and verification do not prove legal ownership.
- Receive Signal reports and apply for ALLY
Current claim holders 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.
Learn how ALLY applications and ongoing maintenance work
Learn how Accesserty separates badges, statements, ALLY, and reports
Learn how Pulse handles website data
Website accessibility monitoring after launch
What an accessibility reporting channel should include
How to respond to accessibility reports
Frequently asked questions
Maintainers with an active Pulse claim can apply for ALLY. After approval, they should keep reviewing and handling Signal reports. ALLY is not an accessibility certification or compliance guarantee, and it may be revoked when maintenance does not continue.
Accesserty Pulse is a post-launch website accessibility maintenance tool. After you add a lightweight script, it organizes user reports, interaction-difficulty events, and low-frequency page scan summaries so maintainers know which live pages deserve human review first.
Free supports one domain, the latest 100 events, Signal report handling, and ALLY applications. Pro costs US$49 monthly or US$490 annually, both with a 14-day trial, and adds up to five domains, priority page lists, complete scan summaries, the latest 1,000 events, an in-Console weekly report, and an optional email summary.
Traditional analytics can show that someone left a page, but not whether they encountered difficulty first. Pulse is not a general analytics tool; it turns bounded interaction clues, scan summaries, and reports into a review order for maintainers.
Repeated clicks, possible keyboard dead interactions, focus reversals, Escape close difficulties, possible keyboard traps, focus being pulled back, and repeated form attempts, plus a page-level summary of automatically detectable WCAG A/AA and best-practice risks.
No. Pulse does not record screens, replay user sessions, collect mouse-movement trails, or store full page content or form field contents. It stores bounded interaction-difficulty events, selectors, URL context, and page scan summaries so maintainers can prioritize review.
No. Pulse’s automated summary only covers machine-detectable issues, and interaction events are review clues. Pulse helps prioritize which pages to inspect first; it does not replace a complete audit, assistive-technology testing, expert review, or real-user testing.
No. Pulse does not provide legal decisions, WCAG conformance proof, certification, or guarantees. It provides maintenance clues and page prioritization so responsible teams can decide where human review and follow-up repair are needed.
The Pro weekly report separates this week’s interaction-difficulty events and Signal reports, the current latest page scan state, and the pages most worth reviewing first. Latest scan state means the most recent stored scan summary for that URL; it is not described as a newly found issue this week.