EchoFillEchoFill › Tools › Autofill Test Form
The Autofill Test Form
Most form fillers work on a simple contact form and fall apart on the forms that actually waste your time. This page collects 18 of the fields that break them, the same patterns job portals, government sites and web apps use every day. Run any autofill tool on it, browser autofill included, and the scorecard shows exactly which fields it handled.
- Fill the form in by hand once, or use your tool's "record" or "save" feature.
- Reload the page. Several fields change their hidden IDs on every load, just like real web apps.
- Run your autofill tool. For the wizard, click Next step and run it again, the same as on a real multi-step form. Then read the scorecard.
What each test checks
| Field | Why tools fail it | Where you meet it |
|---|---|---|
| Placeholder or aria-label only | No <label>, so tools that match by label text find nothing. | Sign-up forms, modern web apps |
| Changing IDs | The field's id and name are new on every load, so tools that remember IDs miss it. | Workday, Salesforce, most React apps |
| App-controlled input | Setting the value silently looks filled, but the page's state stays empty and the value vanishes on submit. | Anything built with React, Vue or Angular |
| Button-and-list dropdown | It isn't a real <select>; it has to be opened and an option clicked. | Workday, Greenhouse, government portals |
| Type-to-search box | Typed text alone doesn't count; an option from the list has to be chosen. | React-Select, location and school pickers |
| Step 2 of a wizard | The fields don't exist when the page loads. | Applications, onboarding, checkout |
| Iframe | The field lives in a separate document inside the page. | Embedded application forms, payment steps |
| Web component | The field sits inside a shadow DOM that normal page searches can't see. | Salesforce, design-system based sites |
| Rich-text editor | It's an editable region, not an input, with its own internal state. | Listings, cover letters, CRM notes |
How EchoFill does
We built this page partly to keep ourselves honest, and it has already paid off. Record the form once with EchoFill, reload, click Autofill, then click Next and Autofill again for step 2. Result: 16 of 17 scored fields. The miss is the rich-text editor, which EchoFill doesn't support yet.
The first time we ran it, the score was 15. This page caught a bug: a type-to-search box sitting next to its own label and hint text looked "already answered", so EchoFill skipped it. That pattern is common on real job portals, so we fixed it.
If you try another tool, we'd like to hear how it scored: contact@echofill.app.
Common questions
Is anything I type here saved or sent anywhere?
No. The form has no submit button and the page sends nothing. Reloading clears it, unless your autofill tool fills it back in, which is the point.
Can I use this page to test my own extension or app?
Yes. It's free to use and to link to. Every field uses standard HTML and plain JavaScript, so what you see in your browser's developer tools is everything there is.
Why does a field show "Looks filled, not registered"?
The City field is controlled by app state, like a React form. If a tool sets the value without the events a real keystroke produces, the box shows text but the app never hears about it. On a real site that answer would disappear when you submit.