Example Pulse weekly report
A page with no scan findings can still have interaction clues worth checking.
A Pulse weekly report groups scan findings by rule and element, so one element repeated on many pages is one problem. It adds interaction events, a comparison with last week and Signal reports, so you know what to fix first and which element to look at. Look at the clues, then try the task yourself. The report does not determine whether a visitor completed a task.
6 problems to fix, 3 high priority. 1 problem resolved since the previous scan. 2 repeated interaction signals not tied to a scan problem.
Fix these first
Elements are redacted CSS selectors from the latest saved scan, at most three per rule. Different elements can share a selector, so confirm on the page.
High priority: label
Form elements must have labels
Element:
#card-numberPages: /checkout/payment (1 page, 2 elements)
Repeated interaction signals on this element: 6 events.
Impact: Critical
High priority: image-alt
Images must have alternative text
Element:
img.product-heroPages: /products/tents (1 page, 4 elements)
Impact: Critical
High priority: aria-dialog-name (new)
ARIA dialog and alertdialog nodes should have an accessible name
Element:
div.order-dialogPages: /account/orders (1 page, 1 element)
Repeated interaction signals on this element: 6 events.
Impact: Serious
Medium priority: list
Lists must only directly contain <li>, <script> or <template> elements
Element:
header nav > ulPages: /, /products/tents, /blog/winter-guide (3 pages, 3 elements)
Impact: Serious
Medium priority: color-contrast
Elements must meet minimum color contrast ratio thresholds
Element:
.pay-summary .mutedPages: /checkout/payment (1 page, 3 elements)
Impact: Serious
1 more problem in your Console.
After fixing a problem, choose "Mark fixed and rescan" in your Console. The page is scanned again on its next visit, and next week's report shows whether the problem is resolved.
Compared with last week
- Interaction events: 35 this week, 41 in the previous 7 days.
- New problems: 1
- Resolved problems: 1
- button-name on
button.apply-coupon(/checkout/payment)
- button-name on
Only pages rescanned this week can show new or resolved problems: 5 of 6 pages.
Repeated interaction signals
Signals on at least 3 page views across 2 days, outside the problems above. Page views count only page loads with recorded interaction events, not total traffic or unique visitors.
/products/filter
Element:
button.filter-applyPossible keyboard dead interactions: 7 events on 4 page views across 3 days.
Next step: Check that this element works with Enter or Space and has the right role.
/checkout/payment
Element:
div.couponPossible keyboard traps: 5 events on 3 page views across 2 days.
Next step: Use the keyboard on this element: check focus order and where focus goes next.
Watching
Below that threshold; not yet worth acting on.
- /products/filter,
input#price-max: Focus reversals: 4 events on 4 page views across 1 day - /account/orders,
div.order-dialog: Escape close difficulties: 3 events on 2 page views across 2 days - /blog/winter-guide,
a.share: Repeated clicks: 4 events on 1 page view across 1 day
Data health
- Pages with a saved scan: 6
- Scans older than 14 days: 1
- Newest scan: 2026-09-03 09:12:44 UTC
- Oldest scan: 2026-08-12 07:30:00 UTC
Domain details
northfield-outdoors.example
Interaction-difficulty events: 35 (previous 7 days: 41)
- Repeated clicks: 4
- Possible keyboard dead interactions: 7
- Focus reversals: 4
- Escape close difficulties: 3
- Repeated form attempts: 6
- Possible keyboard traps: 5
- Focus pulled back: 6
Pages with a saved scan: 6
Signal reports received: 2
What this report is not
This is a triage aid, not a conformance verdict. Problems are ordered by scan impact and raised one level when a repeated interaction signal (at least 3 page views across 2 days) appears on the same element. Review Signal reports separately. Machine scans find only some problems, so an unlisted page is not a tested page. A specific report of a blocked task deserves review even when its page is absent.
An interaction event alone does not establish a barrier or its cause. A focus reversal may warrant review, or someone may simply have changed their mind. Page views count only page loads with recorded interaction events, not total traffic or unique visitors. Event counts are not counts of failed tasks. Check the actual interaction and any report details.
What can you do with this report this week?
- Compare event dates, scan dates and release dates. The latest saved scan may not describe the current page.
- Try one page: for the filter example, choose a condition, update results and move focus onward. Record expected and actual results; keep unreproduced clues marked for review.
- Assign an owner and dates for the fix and re-test in your existing issue tracker. After the fix, choose "Mark fixed and rescan" in the Console so next week's comparison lists resolved problems, and still repeat the task on the fixed page; fewer events do not establish resolution.
See this for your own site
Pulse Pro supports five domains with optional weekly email reports. Review its features and data handling before deciding whether it fits your maintenance needs.