[wp-trac] [WordPress Trac] #40432: Customizer: Should we stop contextually hiding features?
WordPress Trac
noreply at wordpress.org
Tue Apr 18 10:32:51 UTC 2017
#40432: Customizer: Should we stop contextually hiding features?
-------------------------+------------------------------
Reporter: melchoyce | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Customize | Version:
Severity: normal | Resolution:
Keywords: | Focuses:
-------------------------+------------------------------
Comment (by karmatosed):
I have seen time and time again in usability tests showing something that
is hidden cause issues for a user. We have to be so careful to look beyond
our headspace with this. Sure we know its hidden, that the widget area is
behind that slide out section, yet most users do not. This doesn't help
them, it makes them feel stupid - lets not do that. I have heard so many
times in usability tests a user apologise when its not their fault they
don't get the 'WP way' - the frustratingly awkward bad experience WP way.
As far as the solution, my concern with graphically disabling is we then
have to do so that users get what that really means. We can maybe test
this. I do however think just stopping doing this is a good step one.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/40432#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list