[wp-trac] [WordPress Trac] #22058: Improve custom background properties UI

[WordPress Trac]

#22058: Improve custom background properties UI
-------------------------------------+-------------------------------------
 Reporter:  grapplerulrich           |       Owner:
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Future Release
Component:  Customize                |     Version:  3.4.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch ui-feedback    |     Focuses:  ui, accessibility,
  needs-testing has-screenshots      |  administration
-------------------------------------+-------------------------------------

Comment (by karmatosed):

 Firstly, I think a lot of the issues with this solution come from not
 creating one from observing and testing real users. Note I say real
 because we are all not normal in our use and creating any solution just
 because we think it's a good idea without observing, testing and then
 creating from that point, it isn't a good idea. If we identify a possible
 issue, we should gather data, observe and then come up with a solution.
 Not cobble together a best intention. I don't doubt that what has been
 created is meant to be that and has great intentions at its heart.
 Unfortunately, it falls short of usability.

 What we seem to have after a lot of input and various voices is something
 very over-engineered for the solution. Something this complex we should
 always stop carrying on the complexity and consider where we went wrong.
 I'd say the wrong point here is not actually creating after observing or
 looking for designer input earlier. That later may have just been a case
 of us not having enough to spread to Customizer, we're are all try and fix
 that though and slowly have a better team.

 This all said, user testing and actually finding out what does and doesn't
 work for users isn't something only designers can do. I at no point unless
 mistaken see this happening for this enhancement. This has got over time
 more and more complex and more and more iterations without ever having
 user tested. That's something we should stop as a behaviour. I know we
 don't always have the people around, but this really is important. I'm
 happy to help anyone find out how they can do user testing - it shouldn't
 be down to just a few people or just designers.

 This UI to me is a classic example of a paradox of choice, your eyes can't
 settle and no clear path is obvious. That's bad and not going to ensure it
 works. I actually beyond that have a lot of issues with even knowing where
 the positions are in these images. I do not feel this at all is the right
 path.

 I don't think the intention of this ticket is bad and I actually think
 with some research we could come up with a solid solution. I do not feel
 the current one on table is that. @melchoyce shows how .com does it and I
 think that's worth adding as a simpler but just as effective solution. Do
 we have to do that? No. But, lets actually pause and find the point we
 escalated without user testing and iterating through a user focused design
 process.

 I am commenting late in this tickets life and I know that can be horrible
 to do. I don't meant to drive by comment, but we are trying as said
 earlier to give the attention Customizer tickets deserve from the design
 team. Please drop tickets like this into the design weekly chat - I'm
 fairly sure I can speak for everyone that comes to that chat and say we'd
 love that and promise to take action. I'm also going to spend a few hours
 tomorrow and look over any flagged for Customizer UI or UX, hopefully we
 can ensure we don't have to come in late on other features, but we can
 work together.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/22058#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform