Detect Accessibly

PluginView evaluates public page signals in these classes when identifying Accessibly. Individual fingerprint rule bodies are proprietary and are not published.

• Script sources
• JavaScript globals

Illustrative indicators derived from public catalog metadata for Accessibly. A live scan may match additional proprietary rules beyond these examples.

• accessibly.onthemapmarketing.com
• accessibilityWidget.name: bound

Establishes

One or more public signals on the scanned page matched a known Accessibly signature (2 rules) at the time of the scan.

Does not establish

A sitewide install of Accessibly, an active vendor contract, exclusive use, or that Accessibly is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Accessibly signals.
2. 2. PluginView reads only public responses (script sources, javascript globals) and scores them against the Accessibly signature set (2 rules).
3. 3. Review the confidence score and text explanation for Accessibly on the results page.

Can PluginView detect Accessibly without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Accessibly — typically script sources, javascript globals. It does not bypass authentication or paywalls.

What category is Accessibly?

Accessibly is classified under Accessibility in the PluginView directory.

How many fingerprint rules cover Accessibly?

This reference currently tracks 2 fingerprint rules across script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Accessibly?

Illustrative public indicators for Accessibly include accessibly.onthemapmarketing.com; accessibilityWidget.name: bound. A live scan may match additional proprietary rules beyond these examples.