INTERACTIVE SAMPLE · FICTIONAL DATA
Interactive sample report
Start here: the first finding is selected below. Read why it matters, inspect the example, then try writing a note for a developer.
Filter the example findings, select one, and edit its reviewer note. The CSV preview includes the filtered findings; the ticket preview follows the selected finding.
No sign-in or scan credits needed. This demo stays available when shared scanning capacity is full. Notes stay in this tab only and reset when you reload. Do not enter private information.
Why this matters
Where to look
This fictional page and CSS selector identify the affected element. The selector helps a developer locate it in the page code.
What to change
Example after the change
Retest the page after making the change. This example illustrates a fix; it does not verify your website.
Edits update both previews below. A note does not change the automated finding or verify a fix.
CSV preview — filtered findings
Ticket preview — selected finding
Plan the manual checks too
Alongside keyboard, focus and screen-reader checks, review pointer target size and spacing, activation with an actual dwell-click tool, on-screen keyboard use, and browser zoom at 200% and 400%. Record the input method, tool settings and page state for each outcome. Automated findings do not verify these interactions.
These examples demonstrate the workflow, not a live assessment. Automated checks support manual testing.