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 scan findings to check, 3 high priority. 1 problem resolved in this period. 2 repeated interaction signals not tied to a scan problem.
5 of 6 pages with saved scans were scanned in this period; 1 scan is over 14 days old. Older findings may need a fresh check.
Check these first
Each problem is one scan rule, shown with one element the latest scan sampled for it; other sampled elements are listed with it. Elements are structural paths (element names and positions, no ids or classes), at most three per rule. A path can point to a different element after the page changes, so confirm on the page.
High priority: A form field needs a label
Priority basis: Critical scan impact; 1 page, 2 elements. Repeated interaction signals (6 events) also match this element.
- Pages:
- /checkout/payment (1 page, 2 elements)
- Repeated interaction signals on this element:
- 6 events.
- Impact:
- Critical
Technical details
Rule: label
Element reported by the page:
body > main > form > div:nth-of-type(2) > inputForm elements must have labels
High priority: An image needs a text alternative
Priority basis: Critical scan impact; 1 page, 4 elements.
First check: Decide whether the image informs, performs an action or is decorative; check for matching text, or an empty alt for decoration.
- Pages:
- /products/tents (1 page, 4 elements)
- Impact:
- Critical
Technical details
Rule: image-alt
Element reported by the page:
body > main > *:nth-child(1) > imgImages must have alternative text
High priority: A dialog needs a name (new)
Priority basis: Serious scan impact; 1 page, 1 element. Matching repeated interaction signals (6 events) raised the priority.
- Pages:
- /account/orders (1 page, 1 element)
- Repeated interaction signals on this element:
- 6 events.
- Impact:
- Serious
Technical details
Rule: aria-dialog-name
Element reported by the page:
body > div:nth-of-type(3)ARIA dialog and alertdialog nodes should have an accessible name
Medium priority: A list contains incorrectly nested content
Priority basis: Serious scan impact; 3 pages, 3 elements.
- Pages:
- /, /products/tents, /blog/winter-guide (3 pages, 3 elements)
- Impact:
- Serious
Technical details
Rule: list
Element reported by the page:
body > header > nav > ul<ul> and <ol> must only directly contain <li>, <script> or <template> elements
Medium priority: Text may not have enough contrast
Priority basis: Serious scan impact; 1 page, 3 elements.
- Pages:
- /checkout/payment (1 page, 3 elements)
- Impact:
- Serious
Technical details
Rule: color-contrast
Element reported by the page:
body > main > aside > p:nth-of-type(3)Elements must meet minimum color contrast ratio thresholds
1 more problem in your Console.
Recheck the fix first. A page is scanned again only on a visit with Pulse running, normally from 14 days after its last scan; "Rescan these pages" allows it on the next visit. The comparison changes after that scan.
Compared with last week
- Interaction events: 35 this week, 41 in the previous 7 days.
- New problems: 1
- No longer detected on some pages (still listed or not ruled out elsewhere): 0
- Failing-element counts that changed:
- Text may not have enough contrast (/checkout/payment): 5 → 3
- Resolved problems: 1
- A button needs a name (/checkout/payment)
Technical details
button-name ·
body > main > form > div:nth-of-type(4) > button
- A button needs a name (/checkout/payment)
Pages scanned this week, first scans included, are compared with their last scan before this week, or their first scan this week when no earlier one is kept. Pages scanned this week: 5 of 6 pages.
Repeated interaction signals
Signals on at least 3 page views across 2 days, outside the problems above. The same element in sibling copies of a component and on other pages is combined. Page views count only page loads with recorded interaction events, not total traffic or unique visitors.
Possible keyboard dead interactions
/products/filter
Possible 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.
Technical details
Element reported by the page:
body > main > form > buttonPossible keyboard traps
/checkout/payment
Possible keyboard traps: 5 events on 3 page views across 2 days.
Next step: Check that you can enter and leave with the expected keys. An open dialog may intentionally cycle focus; check its keyboard-accessible close action and focus return.
Technical details
Element reported by the page:
body > main > form > div:nth-of-type(4)
Watching
Below the repeat threshold; check anyway if someone reports being blocked.
- /products/filter: Focus reversals: 4 events on 4 page views across 1 day
Technical details
Element reported by the page:
body > main > form > input:nth-of-type(2) - /account/orders: Escape close difficulties: 3 events on 2 page views across 2 days
Technical details
Element reported by the page:
body > div:nth-of-type(3) - /blog/winter-guide: Repeated clicks: 4 events on 1 page view across 1 day
Technical details
Element reported by the page:
body > main > article > *:nth-child(5) >> button
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.
- Plan the fix and re-test in your existing issue tracker. Recheck the fix first. A page is scanned again only on a visit with Pulse running, normally from 14 days after its last scan; "Rescan these pages" allows it on the next visit. The comparison changes after that scan.
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.