We found 6 issueson trytofu.aiworth fixing.
Watch the inspection.
We navigate your site the way customers would. Idle time is skipped.
How the composite score works
The overall score is a weighted average: Visual 18.75%, Accessibility 25%, Buttons and links 31.25%, Under the hood 12.5%, and Mobile 12.5%. Unassessed categories are excluded and the remaining weights are normalized.
Product categories start at 100. Each distinct verified finding deducts 30 points for a reproduced flow defect, or 18 for critical, 12 for high, 7 for medium, and 3 for low stored detector severity. Scores stop at zero and round to whole numbers. All verified findings count, including those beyond the displayed list. The formula is fixed and versioned, so the same saved evidence always receives the same score.
The pricing page and the terms disagree on paid billing
The pricing card on / states "Tofu $9.99/mo For up to five apps that need builds and ongoing updates" with the feature line "Up to 5 apps with managed hosting". The terms page states "Paid plans are billed monthly per app. The current paid plan is USD 9.99 per app per month". One describes $9.99 covering five apps, the other $9.99 for each app, so a customer running five apps would owe either $9.99 or $49.95 per month depending on which page they read. Both statements are present on the live routes.
Try it: Open / and read the paid Tofu card, then open /terms and read the "Plans and what you pay" section; compare the per-app wording against "up to five apps".
The MCP bridge tool count differs between features and docs
The /features page states "Twenty-two tools do the same work as the dashboard: upload, framework confirmation, the safety check, deploy, status, logs, history, rollback, environment names, a repair brief, the app's managed database and a domain you own." The /docs page, describing the same MCP bridge and the same device-flow connection, states "The bridge exposes 30 tools:" followed by the grouped table of tool names. Both passages describe the tool set of the bridge, so one of the two counts is out of date.
Try it: Open /features and search for "Twenty-two tools", then open /docs and search for "The bridge exposes 30 tools", and compare the two counts against the tool table on /docs.
The Cross-Origin-Resource-Policy header is missing
The response from https://trytofu.ai/ is missing Cross-Origin-Resource-Policy.
Try it: Run curl -sI https://trytofu.ai/ and look for a Cross-Origin-Resource-Policy line in the response headers.
Small grey labels fall below the contrast minimum
Several 10.5px grey labels on the landing page sit below the WCAG AA contrast minimum of 4.5:1. The hero helper text "or paste this into your agent" measures 3.85:1 (#767c8e on #f5f6f9), the comparison heading "What you'd wire up yourself · list prices" measures 3.91:1 (#767c8e on #f7f8fa), and service sublabels such as "Hosting" in the pricing grid measure 4.16:1 (#767c8e on #ffffff). axe-core flags the same color-contrast rule at serious impact on /, /features, /about and /privacy.
Try it: Open / on desktop and sample the grey 10.5px labels ("or paste this into your agent", the "Hosting" and "Auth" sublabels) with a contrast checker against their backgrounds.
Inline links are set apart only by color
Inline links inside body paragraphs on /features, /docs, /terms and /privacy carry no underline or other non-color styling, so color alone marks them as links. The axe-core rule link-in-text-block fails at serious impact: the "setup page" link (a[href="/agent"], link text #3e37c4) sits at 1.29:1 contrast against the surrounding text color #595f72, below the 3:1 minimum. This maps to WCAG 2.0 A, success criterion 1.4.1.
Try it: Open /features and look at the inline "setup page" link in the body copy: it has no underline and its color is nearly the same as the paragraph text around it.
Code blocks on /docs cannot be scrolled by keyboard
On /docs, the setup command block in the "Give the work to your coding agent" section (section:nth-child(2) > .project-module__H4hNEG__prose > pre) scrolls horizontally but is neither focusable nor contains focusable content, so a keyboard user cannot reach the clipped text. The block's third line runs past the right edge at "codex mcp add tofu --env TOFU_URL=https://app.trytofu.ai --env TOFU_CLIENT=codex -- <absolute-node> <absolut...". axe-core reports scrollable-region-focusable at serious impact against WCAG 2.1.1 and 2.1.3, and a similar node was suppressed as a duplicate.
Try it: Open /docs, tab through the page, and try to reach and scroll the horizontally clipped command block without a mouse.
Probie fixes this for you.
This report came from one visit. When installed on your project, Probie watches real sessions, reproduces failures, and opens tested fixes as pull requests.
Sign up and get this fixedFree inspection
What should Probie inspect next?
Enter a project URL. There is nothing to install.
Probie checks every issue twice, respects robots.txt, and backs off at bot challenges.
Enter an address and we will email the report card link.