All 141 tools / Research and usability testing
Check whether a page answers Krug's six trunk-test questions: site, page, sections, options, location, search
Trunk testFreeFor designers, researchers and product teams
15/day
free runs a day, no sign-in.
Before: what you give it
The example input, as typed in. You give it a page address.
<header><a href="/" class="logo"><img src="/logo.svg" alt="Larder Books"></a><nav aria-label="Main"><a href="/shop">Shop</a><a href="/events">Events</a><a href="/about">About</a></nav><form role="search" action="/search"><input type="search" name="q" aria-label="Search the shop"></form></header><nav aria-label="Breadcrumb"><ol><li><a href="/">Home</a></li><li><a href="/shop">Shop</a></li><li aria-current="page">Cookbooks</li></ol></nav><main><h1>Cookbooks</h1></main>
After: what comes back
The first lines of a real run on that input. Nothing here is edited by hand.
# Trunk test (from markup) Krug's trunk test asks whether a visitor dropped on any page can answer six questions. This tool answers them from static markup only. It cannot see layout, size, contrast, script-built menus or what a person notices at a glance, so the real test (print a page, hold it at arm's length, squint, circle the answers) is still the test. 5 answerable, 0 partial, 1 missing of 6. ## What site is this? [answerable] A site name sits in the header or metadata. - logo or home link in header: "Larder Books" ## What page am I on? [answerable] One h1 names the page. - h1: "Cookbooks" ... full output on the tool page
What you get
Each question marked answerable, partial or missing, with the markup evidence found
What it cannot do
Reads static markup only; it cannot judge layout, prominence or script-built menus, so it does not replace the paper test.
Who it is for
- Designers
- Researchers
- Product teams
Free and Pro
| Free | 15 runs a day per IP address, up to 100,000 characters a run. |
|---|---|
| Pro | No daily limit, 300 requests a minute, up to 200,000 characters a run. |
Use it from your assistant
The tool is called trunk_test. Connect the server once, then ask for it by name or just describe the job. Install steps for each app.
claude mcp add --transport http designers https://designers.allthepossibles.com/mcpcurl -X POST https://designers.allthepossibles.com/api/trunk-test -H 'content-type: application/json' -d '{"html":"<header><a href=\"/\" class=\"logo\"><img src=\"/logo.svg\" alt=\"Larder Books\"></a><nav aria-label=\"Main\"><a href=\"/shop\">Shop</a><a href=\"/events\">Events</a><a href=\"/about\">About</a></nav><form role=\"search\" action=\"/search\"><input type=\"search\" name=\"q\" aria-label=\"Search the shop\"></form></header><nav aria-label=\"Breadcrumb\"><ol><li><a href=\"/\">Home</a></li><li><a href=\"/shop\">Shop</a></li><li aria-current=\"page\">Cookbooks</li></ol></nav><main><h1>Cookbooks</h1></main>"}'Try it here
The form starts with the same example input, so you can run it first and then swap in your own.
More in research and usability testing
- Usability numbers
Score SUS results and work out sample sizes for usability tests, A/B tests and surveys.
- Heuristic review
Get a Nielsen heuristic worksheet for a screen or flow, with signals showing where to look first.
- Critique plan
Plan a design critique for the stage the work is in, with timed rounds, roles and feedback to hold back.
- Research questions
Find leading, double-barrelled and hypothetical questions in an interview or survey script and rewrite them.
- Form check
Check a form's markup against Wroblewski's Web Form Design rules and get a fix for each finding
- Card sort analyser
Turn open card-sort results into a similarity matrix and suggested categories from participant agreement