Pluro Behavior Scan is a Chrome DevTools extension for recording real user flows and detecting behavioral accessibility issues that static scans may miss.

Contact Support

Email: it@pluro.ai

When contacting support, include the extension version, Chrome version, operating system, action that failed, visible error message, and a sanitized Diagnostic Log exported from Settings. Include the page URL only when it is not confidential.

Do not email Client Keys, passwords, cookies, authorization headers, private customer data, raw form values, or unredacted screenshots containing sensitive information.

Requirements

– Google Chrome with Developer Tools available;
– a Pluro account and valid Client Key;
– an active licensed domain in MyPluro;
– the exact HTTPS page registered and authorized in MyPluro.

Getting Started

1. Open an authorized website in Chrome.
2. Open Chrome DevTools and select the **Pluro** panel.
3. Open **Settings**, paste your Client Key, and select **Check current page**.
4. Confirm that authentication, domain licence, and page permission are valid.
5. Open **Record Flow** and record one focused user journey.
6. Stop recording and select **Run Local Analysis**.
7. Review Results, Timeline, and Evidence.
8. Select **Send to MyPluro** only when you want to sync sanitized findings.

Common Issues

The Pluro panel is missing

– Confirm that the extension is enabled in `chrome://extensions`.
– Close and reopen DevTools after installing or updating the extension.
– Reload the inspected page.

Client Key is invalid

– Paste a current Client Key issued by Pluro.
– Confirm that it has not expired or been revoked.
– Do not add `Bearer` before the key; the extension adds the Authorization scheme.

Domain is not licensed

The current hostname is not associated with an active licensed domain for the Client Key. Contact your MyPluro administrator or Pluro support.

Page is not registered

Register the exact HTTPS page URL in MyPluro and select **Check page** again. URL matching may include the path, query, fragment, protocol, and trailing slash.

Recording does not start

– Use a regular HTTPS website; Chrome internal and extension pages are unsupported.
– Confirm that MyPluro authorizes the exact page.
– Reload the page and reopen DevTools after extension updates.

Local Analysis returns few or no findings

Behavior Scan evaluates only the interactions exercised in the recorded journey. Open dialogs, submit invalid forms, use keyboard navigation, activate menus, and trigger meaningful dynamic updates. A result with no behavioral findings does not mean the page has no accessibility issues.

Sync fails

– Check the Client Key and exact-page permission.
– Confirm that MyPluro is reachable.
– Wait before retrying if the service returns a rate-limit or temporary-service error.
– Export a sanitized Diagnostic Log and contact support if the problem continues.

Privacy and Security

Behavior analysis runs locally in the browser. The extension stores settings, recording state, diagnostic events, and recent results in Chrome local extension storage. Sensitive input fields are masked, and the Client Key is not sent to the inspected page or included in exports.

Only sanitized findings are sent to MyPluro when the user selects the sync action. For details, see the Pluro Privacy Policy

Product Scope

Behavior Scan complements Pluro structural accessibility scanning. It does not claim to test every WCAG requirement or replace manual accessibility testing.

Pluro website: https://pluro.ai/