Our own audit
We ran our own site through our own product.
These are the audits we ran on our own site with Your UX Agent, on our preview server rather than on youruxagent.com. They went through the quote, credit, queue, access-profile and API steps a customer's audit takes, but the first run used a development copy of our audit software, not the release customers' audits use. The dates, durations and test-credit costs below are the recorded values, not a summary of them.
A passing automated run does not establish usability or accessibility conformance; keyboard, focus, zoom, screen-reader, content, and visual review remain required.
The runs
First full run
Covered /, /blog, /sign-in, and the saved authenticated /app target.
Authenticated control, after the fixes
Covered the saved authenticated /app target.
Exact-page containment control
Covered exactly /app, one page and no journeys.
Full-site control
Covered /, /blog, /sign-in, /app, plus the open-primary-cta journey.
What changed is listed below, item by item: which check found it, what we changed, and which later run, if any, covered the same page and no longer found it. The two rule families audit 77 still reported are named at the bottom of this page rather than averaged away.
Found and fixed
- Fixed
An audit table forced an 884-pixel document on a phone
Found by our own Playwright checks, not by a product run. Below 768 CSS pixels the audit history now renders as labelled, scan-friendly cards instead of a table that pushed the document past the viewport. The record names no product run that checked it again.
- Fixed
Small supporting copy and success badges failed contrast
Found by the first product run, with two occurrences on the dashboard workspace chooser alone, and by our own Playwright checks. Supporting text and the green pass badges moved to darker production colours that meet AA. Audit 77 found no contrast issue left on the dashboard.
- Fixed
Controls were too small to hit
Found by the first product run on every page and screen size it sampled, and by our own Playwright checks. Audit filters, tabs, selects, the dialog close, back, select-all, audit actions, and the workspace control were all undersized. The shared controls outside the app shell now carry a 44px target. Audit 77 found no undersized control left on the dashboard.
- Fixed
Text spacing clipped content
Found by the first product run. The worked example above: audit 77 found no text-spacing issue left on the dashboard.
How the text-spacing violation was confirmed gone
Audit 77 re-ran the same target and inspected every eligible rendered text candidate — 51 of 51 at 320, 390, 504, 536 and 604 CSS pixels, 45 of 45 at 834, and 62 of 62 at 1280. No text-spacing finding remained.
A later audit covered the page and the violation was absent. In the product, only a later audit like that can move a task to resolved.
What the audit retained as evidence
Coverage counts from the authenticated control run. An inspection that ran out of time has to report incomplete coverage rather than pass, so a zero here means zero.
- Text contrast samples
- 286
- Interaction state samples
- 148
- Non-text candidates
- 79
- Typography samples
- 362
- Design density samples
- 7
- Indeterminate checks
- 0
Still open
An audit that only shows what was fixed is marketing. These are the findings our product still reported when it audited the signed-in dashboard again, after our fixes, on 20 August 2026, and why we had not acted on them.
- Open
Long main-thread tasks
performance-long-tasksReal diagnostics, but the threshold has not been validated yet. Until it is, promoting these to a release gate would be asserting a number we have not justified.
- Open
Readability of page copy
plain-languageAdvisory by design — it is advice a site is free to decline, so it is reported as a suggestion and never counted as a violation. The wording still needs review before we would act on it.
What this page is not
It is not a conformance statement and not a certification. It covers the pages listed above at the viewports listed above, and nothing else. Keyboard, zoom, screen-reader, content and visual review by a person remain necessary, and no automated result replaces them.
The automated checks we run before we release, and what they leave out, are in our accessibility statement.
Scan one page of your own siteFree, and no sign-up.