How Accesserty Handles Website Data
A plain-language explanation of what Accesserty Pulse and Signal collect, what they do not collect, and how website data is used.
This is not a legal document
Accesserty is built to help people notice, report, and review accessibility barriers without turning accessibility into hidden tracking or an unverifiable compliance promise.
The Privacy Policy and Terms of Service provide the full legal explanation. This page gives website maintainers a plain-language summary before they install the Pulse script.
What Pulse may collect
When a website maintainer installs Accesserty Pulse, Pulse may collect lightweight interaction signals and page-level summaries, such as:
- Page URL.
- Event type, such as repeated clicks, blocked keyboard interactions, focus reversals, Escape failures, or repeated form attempts.
- Timestamp.
- Browser and device context needed to understand the event.
- Page-level scan summaries when available, such as counts of machine-detectable WCAG A/AA and best-practice risks.
What Signal reports may include
When a user sends a report through Accesserty Signal, the report may include:
- The reported page URL.
- Selected issue types.
- An optional message or contact email if the user chooses to provide one.
- Browser user agent.
- Public accessibility signal context for that page when available.
What Accesserty does not intentionally collect
Accesserty does not collect everything on a page, and Pulse is not used as an advertising tracker. Accesserty does not intentionally collect:
- Passwords.
- Payment card data.
- Form input values.
- Full page content.
- Private messages.
- Browsing history across unrelated websites.
- Keystroke logs.
- Screen recordings.
- Advertising identifiers.
Signal is not a search ranking system. Pulse is not an advertising tracker. Accesserty does not sell website visitor data.
What the Pulse script does
The Pulse script runs only on websites where a maintainer installs it. It records selected accessibility-related interaction signals and sends them to the maintainer’s Accesserty Console.
The Pulse script does not change the website interface for visitors. It does not inject accessibility overlays, floating toolbars, or automatic fixes.
Installing Pulse does not mean a website is accessible, compliant, or fully audited.
Why Accesserty uses these signals
Accessibility issues often appear after launch. A page can look fine during review and later become harder to use because of new content, layout changes, form changes, third-party services, or real user behavior.
Accesserty uses these signals to help maintainers know where to look first. A signal is not proof of failure. It is a clue that a page may deserve review.
Who can see the data
Verified website maintainers can view Pulse signals and user reports for domains they have claimed in Accesserty Console.
Accesserty does not expose private Pulse data to the public. Public records, such as accessibility certification sources or accessibility statement links, may be used by Accesserty Signal to help users understand whether a traceable public accessibility reference exists.
Removing Accesserty
A website maintainer can remove the Pulse script from their website at any time. After removal, Pulse stops collecting new signals from that website.
Existing records may remain in the maintainer’s Console for review. Deletion requests are handled according to the Accesserty Privacy Policy and applicable law.
Relationship to accessibility review
Accesserty is not an accessibility audit service, certification body, legal service, or automated compliance guarantee.
Accesserty helps people notice, report, inspect, and maintain accessibility-related issues more easily. Complete accessibility review still requires professional judgment, manual testing, assistive technology testing, and real user feedback.
Related documents
- Privacy Policy
Legal details about data collection, use, storage, and user rights.
- Terms of Service
Service use, subscriptions, refunds, responsibility scope, and limitations.
- How Accesserty Understands Accessibility Signals
Learn what certifications, statements, ALLY, user reports, and machine scan summaries can and cannot prove.
- Accesserty Pulse
Learn how maintainers use Pulse to review interaction events, page summaries, and Signal reports.
Frequently asked questions
No. Pulse is not currently a session replay or heatmap tool. It does not record screens or full interaction sessions.
No. Pulse does not intentionally collect form input values. Its purpose is to provide page-level and interaction-event clues, not to read what users type.
No. Pulse provides maintenance clues. It does not replace a full manual audit, assistive technology testing, or legal compliance analysis.