Browser extension and live axe

The Pandus browser extension becomes “the SDK on the page”: open your own site and see the live data on top of it.

Live data

When the site has the SDK and the extension is connected to your team:

• barrier markers on the elements, such as “focus got stuck here 214 times in 7 days”;
• a heatmap over the live page: clicks, focus and rage clicks;
• the problems of this page with their statuses;
• Open recordings of this page and Open in the dashboard.

Overlays are drawn in a Shadow DOM layer and do not touch the page's styles.

SDK debugger

Like a tag assistant: is the SDK on this page, which modules are on, the consent state, CSP errors and the event stream of the current tab. Debug mode is one click away.

Events by pointing

Pick an element, name the event, save. The event counts back in time at once: see Events without code.

Check a fix

The extension runs axe locally on the page and asks the scanner for a re-check. The problem becomes “fixed, waiting for confirmation from live visitors”.

Pages behind a login

Checks of the cart, the account and other pages behind a login made in the extension go into What to fix with the source “Extension”.

No SDK yet

On a site without the SDK the extension shows Install the SDK with the snippet and a hint for the platform it detects.

Permissions

The extension asks for no new permissions: activeTab, scripting, storage and access to pandus.online. It reads data from our API with a token of your team that has the rights insights:read and events:write.

Live axe

On a small sample of page views (the share is set by your plan), the SDK runs axe-core in idle time on the real state of the page: open dialogs, a filled cart, the account. The scanner never sees these states.

• Only after analytics consent, loaded lazily, in idle time; a run that would block the page is split or skipped.
• Sent: the rule, the selector and the HTML structure with every text and value attribute replaced. Pages behind a login contain personal data, so nothing readable leaves the page.
• Results join What to fix as live signals with the source “live axe”.