https://veriwasp-playtest-sandbox-6mhjjwaht-veriwasp.vercel.app
desktop · VeriWasp Demo
Want this on your own app?
VeriWasp runs the same kind of test against your site, on demand or on every pull request via the GitHub App. Free credits, no card required.
Run history
Summary
Last step to pass: #01 navigate, Load the homepage (flagged, see below)
[warning] "[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory.
[network] Fetch https://o205439.ingest.sentry.io/api/1323670/envelope/?sentry_key=d00780d432ac4ccf882f60dd02062e14&sentry_version=7&sentry_client=sentry.javascr
✕ Failed: #02 type, the Your name field
could not find an element matching "the Your name field"
⚠ 4 page-level issue(s) (accessibility), see below.
Suggested next step
Steps 2, 4, and 6 all failed to find their target elements ("the Your name field," "the Password field," and the welcome message), while step 3 ("the Work email field") passed — this pattern strongly suggests the signup form on this page doesn't actually have separate "Your name" and "Password" fields matching those descriptions (likely only an email field is present, or the name/password fields use different labels/placeholders than assumed), and since the account creation flow never got real data into those fields, no welcome message appeared. Next action: pull up the actual signup form HTML and check the exact labels/placeholders/ids for the name and password inputs, then update steps 2 and 4 to reference those precise attributes (e.g., by `id` or exact placeholder text) rather than the generic "Your name field" / "Password field" descriptions.
Timeline
Replay
[warning] "[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory.
[network] Fetch https://o205439.ingest.sentry.io/api/1323670/envelope/?sentry_key=d00780d432ac4ccf882f60dd02062e14&sentry_version=7&sentry_client=sentry.javascr
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "the Your name field"
Before
After
Visual diff vs previous run (changed regions highlighted)
Locator: [data-playtest-id="3"]
Before
After
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "the Password field"
Before
After
Visual diff vs previous run (changed regions highlighted)
Locator: [data-playtest-id="11"]
Before
After
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "a welcome message greeting the new user by name"
Before
After
Visual diff vs previous run (changed regions highlighted)
Issues found
WCAG rates each accessibility rule Level A, AA, or AAA. Most teams target Level AA, which means fixing every Level A and AA failure. Level AAA and best-practice items are optional polish, not required for AA.
New to this? Read what WCAG is and why it matters, or how to fix the most common issues.
Step 2 (type) failed after 2 retries: the Your name field
could not find an element matching "the Your name field"
Step 4 (type) failed after 2 retries: the Password field
could not find an element matching "the Password field"
Step 6 (assert) failed after 3 retries: a welcome message greeting the new user by name
could not find an element matching "a welcome message greeting the new user by name"
1 browser console error(s) logged during the test
1 failed third-party request(s) (analytics, telemetry, or another external service), unlikely to affect your users
[network] Fetch https://o205439.ingest.sentry.io/api/1323670/envelope/?sentry_key=d00780d432ac4ccf882f60dd02062e14&sentry_version=7&sentry_client=sentry.javascript.browser%2F7.111.0 failed: net::ERR_FAILED
Elements must meet minimum color contrast ratio thresholds (1 element)
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds
Links must be distinguishable without relying on color (2 elements)
Ensure links are distinguished from surrounding text in a way that does not rely on color
Zooming and scaling must not be disabled (1 element)
Ensure <meta name="viewport"> does not disable text scaling and zooming
All page content should be contained by landmarks (1 element)
Ensure all page content is contained by landmarks
▸ Show step-by-step technical detail
1 console error(s), 1 network error(s) (click to expand)
[warning] "[GSI_LOGGER]: Your client application uses one of the Google One Tap prompt UI status methods that may stop functioning when FedCM becomes mandatory. Refer to the migration guide to update your code accordingly and opt-in to FedCM to test your changes. Learn more: https://developers.google.com/identity/gsi/web/guides/fedcm-migration?s=dc#display_moment and https://developers.google.com/identity/gsi/web/guides/fedcm-migration?s=dc#skipped_moment"
[network] Fetch https://o205439.ingest.sentry.io/api/1323670/envelope/?sentry_key=d00780d432ac4ccf882f60dd02062e14&sentry_version=7&sentry_client=sentry.javascript.browser%2F7.111.0 failed: net::ERR_FAILED
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "the Your name field"
Before
After
Visual diff vs previous run (changed regions highlighted)
Locator: [data-playtest-id="3"]
Before
After
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "the Password field"
Before
After
Visual diff vs previous run (changed regions highlighted)
Locator: [data-playtest-id="11"]
Before
After
Visual diff vs previous run (changed regions highlighted)
could not find an element matching "a welcome message greeting the new user by name"
Before
After
Visual diff vs previous run (changed regions highlighted)
Screenshots and video are deleted 14 days after the run. Use the download buttons at the top of this report to keep it longer.
This report took one paste and a URL.
Run the same kind of test against your own SaaS. Free credits, no card required.
Test your SaaS free →