Accesserty Pulse
Live website accessibility maintenance, ordered by the pages to review firstInstall one lightweight script and complete verification. Console shows interaction-difficulty clues and bounded, low-frequency scan summaries. Pro uses these to prioritize pages for human review; review Signal reports separately.
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.
Console lets maintainers review interaction-difficulty events and machine-detectable page risk summaries, with Signal user reports reviewed separately. Compare these clues to decide which page and task to try yourself.
The Pro priority page list is ordered by interaction events and bounded scan summaries; review Signal reports separately. A specific report of a blocked essential task may deserve attention even if that page is absent from the list.
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 a page review order based on interaction clues and bounded scan summaries, with Signal reports reviewed separately.
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?
Install and verify one website, then start with one page to investigate and follow up.
Step 1. Register a website you are authorized to maintain
Sign in to Console and register the public domain. Free supports one verified domain; registration alone does not grant access to website data.
Step 2. Install the script and verify the homepage
Place the Console-generated <script> in the homepage HTML returned by your server, then run verification in Console. This verifies data access, not legal ownership. Pulse does not collect form contents, full page content or screen recordings.
Step 3. Review the pages that deserve attention first
Free provides basic events and Signal reports. Pro adds priority pages, complete scan summaries and weekly reports. Compare the event period, scan dates and report details, then try one page yourself; its position in the list is not a confirmed defect.
Step 4. 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.
Choose the plan that fits
Both plans require Pulse installation and domain verification before you can access the relevant data. Paying does not bypass verification or give you a previous maintainer’s records. Event counts are viewing limits, not retention periods. Pro also provides priority pages and weekly reports when you maintain just one website.
Free
US$0
Start with one website: install and verify Pulse, then review interaction events and Signal reports received while your access is active.
- 1 verified monitoring domain
- View the 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
Choose Pro when you need to decide which pages to review first and use a weekly summary to plan follow-up. It is useful for one website and supports up to five verified domains.
- Priority page lists and complete scan summaries
- In-Console weekly report and optional English email summary
- Up to 5 verified monitoring domains
- View the latest 1,000 interaction-event records
- Also includes Signal report handling and ALLY applications
Verify the domains you maintain with Pulse
Pulse surfaces signs of interaction difficulty and bounded scan summaries. Current verified access lets a maintainer review only Signal reports associated with that domain verification.
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
While verified access remains active, review its associated Signal reports in Console and apply for ALLY when actively maintaining accessibility. Removing and verifying the domain again does not restore earlier private records. ALLY is a reviewed maintenance signal, not an accessibility certification.
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
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.
Accesserty Pulse helps teams maintain website accessibility after launch. Once you add its lightweight script, it uses interaction-difficulty events and low-frequency scan summaries to prioritize pages for human review. Signal user reports are shown separately and do not affect that ranking.
Free supports one verified domain, viewing 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, access to the latest 1,000 events, an in-Console weekly report, and an optional English email summary. Event counts are viewing limits, not retention periods.
Traditional analytics can show that someone left a page, but not whether they encountered difficulty first. Pulse is not a general analytics tool; it uses bounded interaction clues and scan summaries to prioritize human review. Signal reports are listed separately for maintainers to review and are not used to calculate that priority.
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.