to MyPluro, validate a licensed domain, record a user flow, and review
accessibility findings that static scans may miss.
- 1
Create an API Key
Generate a secure Extension API Key inside MyPluro. - 2
Connect the Extension
Paste the key into the Pluro Chrome DevTools extension. - 3
Validate the Domain
Confirm that the current page is licensed and authorized. - 4
Record and Review
Capture a user flow and review results, timeline, and evidence.
API Key Configuration
Create a dedicated Extension API Key in MyPluro before using the
Behavior Scan extension.
Step 1: Open the Extension Key page
Log in to your MyPluro account and navigate to:
Account Configs → Extension Key
Step 2: Create a new API key
Select New API Key.
In the dialog:
- Enter a clear key name, such as MyPluro Extension.
- Select an expiration date.
- Select Create Key.
Step 3: Copy and securely store the key
The newly created key appears in the Extension Key list. Copy the
complete key when it is generated and store it securely.
The API key allows the extension to connect to MyPluro on your behalf.
Deleting the key in MyPluro immediately invalidates it.
Connect the Extension to MyPluro
Add the generated key to the Pluro panel inside Chrome DevTools.
Step 1: Open Chrome DevTools
Open the website you want to test and launch Chrome DevTools:
- Press F12.
- Press Ctrl + Shift + I on Windows.
- Press Command + Option + I on macOS.
- Right-click the page and select Inspect.
Select the Pluro tab in Chrome DevTools.
Step 2: Open Settings
In the extension navigation, select:
6. Settings
Step 3: Paste the API key
Paste the key into the Token / Client Key field.
The production API endpoint is managed by Pluro:
https://my.pluro.ai/dashboard/api
The API Base URL is fixed in the production extension and cannot be
edited.
Step 4: Confirm the connection
After the key is saved, the extension displays the current MyPluro
access status.
Valid
Active
Allowed
Validate the Domain
The current website must be registered and licensed in MyPluro
before a Behavior Scan can run.
Step 1: Open the page you want to test
Navigate to the exact website page on which you want to record the
interaction flow.
Step 2: Check the current page
In Settings, select
Check current page.
The extension verifies:
- Whether the API key is valid.
- Whether the domain has an active MyPluro license.
- Whether the current page is authorized for scanning.
Successful validation
When validation succeeds, the extension displays:
- Success
- Page authorized by MyPluro
- The validated domain name
You should also see the following confirmation:
Authentication valid. Domain licensed. Current page is registered
and ready.
MyPluro organization is being used, and the domain has an active
license. Also check differences between the www, non-www, and subdomain
versions of the website.
Record and Analyze a User Flow
Record a real interaction and let Pluro analyze the behavior that
occurred during the browser session.
→
Start Recording
→
Interact With Page
→
Stop Recording
→
Run Local Analysis
→
Review Results
Step 1: Prepare the page
- Open the page at the beginning of the user journey.
- Close unnecessary dialogs or browser panels.
- Choose one specific interaction flow to test.
- Enable any accessibility mode required for the test.
When testing a website that uses the Pluro accessibility widget,
enable the relevant widget mode before recording. Some applied fixes
may only be active when Screen Reader Support is enabled.
Step 2: Start recording
Select Start Recording and perform the flow naturally.
Example interactions include:
- Navigating with Tab and Shift + Tab.
- Opening and closing a menu.
- Opening a modal dialog.
- Completing and submitting a form.
- Triggering validation errors.
- Expanding an accordion.
- Activating dynamically updated content.
- Using the Pluro accessibility widget.
Step 3: Use the recording controls
- Start Recording — begins capturing the user flow.
- Pause / Stop Capture — temporarily pauses event capture.
- Stop Recording — ends the recording session.
- Clear — removes the current recording.
- Export JSON — exports the captured flow.
- Run Local Analysis — analyzes the recorded interaction.
Step 4: Run Local Analysis
After stopping the recording, select
Run Local Analysis.
The extension displays the number of:
- Accessibility findings
- Timeline steps
- Recorded actions
Understand the Results Interface
The captured session is organized into results, timeline, and
supporting evidence.
Overview
Displays authentication, domain authorization, scan readiness,
recording status, analysis status, and general finding counts.
Record Flow
Provides the recording controls and shows the captured interaction
sequence, including actions and relevant page elements.
Results
Shows accessibility findings related to keyboard behavior, focus,
modals, forms, errors, and dynamic content.
Timeline
Presents the recorded interaction in chronological order to help
reviewers understand and reproduce each issue.
Evidence
Provides supporting information such as selectors, events, focus
changes, DOM details, screenshots, and recorded page state.
Settings
Controls authentication, page authorization, evidence capture, and
privacy-related recording options.
Common findings
Depending on the recorded flow, Pluro may identify issues involving:
- Keyboard navigation
- Unexpected focus movement
- Keyboard dead ends
- Modal focus management
- Form validation
- Error announcements
- Dynamic content updates
- Status messages
- Accessible names
- Controls that cannot be operated correctly
Evidence and Privacy Settings
Control the level of evidence captured during each recording.
Default scan options
Available options may include:
- Capture screenshots
- Capture DOM snapshot
- Mask email values in recorded flows
- Mask phone values in recorded flows
Screenshots and DOM snapshots should only be enabled when richer
evidence is required.
Recommended Testing Process
Test one focused user journey at a time for clearer and more useful
results.
Example: Test a contact form
- Open the contact form.
- Start recording.
- Navigate through the form using the keyboard.
- Submit the form with required fields left empty.
- Review how validation errors are presented.
- Stop recording.
- Run Local Analysis.
- Review Results, Timeline, and Evidence.
Create a separate recording for another journey, such as opening a
modal, navigating a menu, operating an accordion, or using a dynamic
interface.
Troubleshooting
Review these common checks when the extension cannot connect,
authorize, or record correctly.
Authentication is invalid
- Generate a new Extension API Key.
- Confirm that the complete key was copied.
- Verify that the key has not expired or been deleted.
- Remove the saved key and enter it again.
Domain license is inactive
- Confirm that the domain exists in MyPluro.
- Verify that its subscription or license is active.
- Confirm that you are using the correct organization.
Current page is not allowed
- Confirm that the URL belongs to the registered domain.
- Check differences between www and non-www addresses.
- Check whether the page uses another subdomain.
- Select Check current page again.
No events are recorded
- Confirm that recording has started.
- Keep Chrome DevTools open during the session.
- Interact with the page after selecting Start Recording.
- Reload and authorize the page again when necessary.
No findings are displayed
A scan with no findings does not confirm that the entire page is
accessible. It means that no supported behavior issues were
detected in the specific recorded flow.
Combine Behavior Scan with:
- Automated scanning
- Manual accessibility testing
- Keyboard testing
- Screen-reader testing
- Expert review