wp-admin UX failures that look like “the plugin works”
It saved; nobody could find the control. That’s still a fail. Runtime success without findability is not a ship gate you can defend.
Your plugin activates. The setting persists. The shortcode renders for you. A cold admin still cannot complete the job in wp-admin. Support tickets sound like “where is X?” while your changelog says “works.”
That gap is a UX failure with a technical alibi. Static checks and your own muscle memory will not close it.
Failures that look green
- Buried settings — three nested menus, no search hit, label that does not match the docs.
- Success without feedback — save works; no notice; user re-clicks and duplicates state.
- Wrong mental model — “Enable” means something else than the checkbox implies.
- Role confusion — works for administrator; editor sees a blank screen or missing menu.
- Docs vs UI drift — screenshot from last year; control moved.
None of these are “the PHP is broken.” All of them block real use. Related: what Plugin Check can’t see in a real wp-admin.
Brief for findability, not vibes
Do not ask “was it intuitive?” Ask whether a cold person finished a named job:
- Start URL: wp-admin dashboard (or the first screen a new installer sees).
- Mission: e.g. “Enable feature X and confirm it on a sample post” — steps in your words.
- Success: observable done state (“notice shown,” “meta box appears,” “option value Y”).
- Form: finished / blocked; where they looked first; what label they expected; severity.
Isolated sandboxes keep leftover options from poisoning the next tester: WordPress plugin sandboxes.
What “works for me” hides
You know the menu. You already activated the license. You are logged in as the right role. Cold testers are the product. If two of three cannot find the control within the mission, you have a pattern — rename, move, or add an onboarding tip — then re-run the same brief.
On QATested
WordPress plugin testing on QATested gives each tester a fresh wp-admin with your zip. Post a findability mission, require recording + structured answers, approve or reject on evidence. How to post: post a Structured QA test.
Related: briefing conflict tests · uninstall leftovers · brief, high-signal tests.