[wp-trac] [WordPress Trac] #37661: A New Experience for Discovering, Installing, and Previewing Themes in the Customizer

[WordPress Trac]

#37661: A New Experience for Discovering, Installing, and Previewing Themes in the
Customizer
-------------------------------------+-------------------------------------
 Reporter:  celloexpressions         |       Owner:  celloexpressions
     Type:  feature request          |      Status:  reopened
 Priority:  high                     |   Milestone:  4.7
Component:  Customize                |     Version:  4.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-           |     Focuses:  ui, accessibility,
  screenshots needs-testing has-     |  javascript
  user-testing ux-feedback           |
-------------------------------------+-------------------------------------

Comment (by celloexpressions):

 Thanks for the feedback @arush!

 The "add new" functionality is on the same page with installed themes now,
 so I'm guessing you may have actually interacted with it. There is no
 longer search for installed themes - the search is for themes on .org.
 Unless you're testing on multisite. In multisite you can only install
 themes in the network admin, so there's only local search and the
 installed themes available in the customizer.

 I know we should be in pretty good shape in terms of keyboard
 accessibility - I've been testing that as we iterate - and we're generally
 using semantic elements. There are a few places where we use
 `wp.a11y.speak()` and also some `aria-` attributes in the patch, so if
 those aren't working as intended or don't result in a cohesive experience,
 let's work on making that better. I don't have as much experience with
 accessibility for screen readers.

 It sounds like adding some screen-reader-text context to the various
 buttons within the theme controls (such as Live Preview [Theme: $theme])
 would make a big difference? I could see how tabbing through a bunch of
 buttons that say the same thing would be a problem. I double-checked and
 the patch has an `aria-label` attribute on these buttons that includes the
 theme name; is this not being read out? There's also an `aria-describedby`
 attribute on the theme screenshot, which opens the the details view
 (unfortunately this isn't a button, but matches the admin screen). It
 looks like those don't include the theme name for context currently.

 If there are challenges with the current patch I'd definitely like to at
 least try to improve the experience for 4.7; it sounds like there are a
 few minor adjustments that could make a big difference. Within the themes
 panel, we shouldn't be technically constrained by some of the limitations
 that currently exist elsewhere in the customizer.

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