This morning I ran 2 users through some “widget” scenarios.
Here are the videos: User 1 & User 2.
User #1
Step 1: Log in
No issues.
Step 2: Check out your site
No issues.
Step 3: Go to widgets screen
No issues.
Step 4: Remove widgets
No issues.
Step 5: Add text widget
Looks like he skipped this step…
Step 6: Add pages widget
3:55 – When he saved the changes he had made to the “pages” widget, he clicked the “Save” button multiple times. Looks like he was unsure as to whether the changes were saved.
Step 7: Reorganize widgets
No issues.
Step 8: Preview changes
No issues.
User #2
She says she’s done a lot of blogging (but only on Blogger). She was excited for the chance to try WordPress.
Step 1: Log in
No issues.
Step 2: Check out your site
No issues.
Step 3: Go to widgets screen
2:20 – She got confused by the wording of my instructions. She found her way to the widgets screen, but thought she was in the wrong place. My bad.
3:30 – and she’s back on track…
4:55 – “Well that is different from Blogger, but I really like that. That is so much more simple”, she says referring to the way you can add and remove widgets by dragging and dropping.
Step 4: Remove widgets
No issues.
Step 5: Add text widget
No issues.
Step 6: Add pages widget
No issues.
Step 7: Reorganize widgets
No issues.
Step 8: Preview changes
No issues.
Observations/Thoughts
- Both users skipped step 5 (where I asked them to add a text widget with an image of a dog). This was unintended. Must have been a glitch.
- They both breezed right through this. I guess that’s a good thing.
What else (related to widgets) can I add if I retest these scenarios in the future? - When saving changes to a widgets, we should show the spinner, and then perhaps “saved” for a brief second (like we do now with media properties). That way users don’t have to guess whether their changes were saved.
- The “First Front Page Widget Area” and the “Second Front Page Widget Area” sections only work when a static front page is set. Should they just be hidden until the user sets a static front page?
Jack Tarantino 4:20 am on January 3, 2013 Permalink
Ooh! A message that widgets were saved would be really helpful! I generally have fast hosting and a fast connection. Sometimes I don’t even notice the spinner come up at all when something saves. Should I open a Trac ticket for this?
lessbloat 4:40 am on January 3, 2013 Permalink
If there is not already one, sure! Thanks.
Travis Northcutt 6:08 pm on January 3, 2013 Permalink
What software was used for these videos?
lessbloat 6:47 pm on January 3, 2013 Permalink
usertesting.com
Sheri Bigelow 4:48 pm on January 4, 2013 Permalink
I’ve observed users having trouble with widgets when they’ve added ALOT of them (probably too many). Perhaps test adding/deleting/editing/rearranging widgets when there are a bunch of them on the page.
I’ve heard that accessibility is an issue when it comes to widgets. Test with visually impaired users if you can.
I would vote yes to either hiding them or making them visible-but-inactive with a note explaining why (if that’s possible?).
adamsilverstein 9:53 pm on January 4, 2013 Permalink
i wrote a possible patch for not seeing the spinner on a fast host (or locally) in http://core.trac.wordpress.org/ticket/23120, wondering if any other buttons need similar treatment.
C?t?lin Dogaru 2:46 pm on January 9, 2013 Permalink
Please take a look at: #19159. It may be useful.