[wp-trac] [WordPress Trac] #46698: Twenty Nineteen: use better color names for the editor palette

[WordPress Trac]

#46698: Twenty Nineteen: use better color names for the editor palette
-----------------------------------------+--------------------------------
 Reporter:  afercia                      |       Owner:  (none)
     Type:  defect (bug)                 |      Status:  new
 Priority:  normal                       |   Milestone:  5.3
Component:  Bundled Theme                |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  has-screenshots needs-patch  |     Focuses:  ui, accessibility
-----------------------------------------+--------------------------------

Comment (by aduth):

 Replying to [comment:9 afercia]:
 > So when a custom hue is set via the Customizer, it wouldn't be possible
 to get a name for the Primary and Secondary colors in Gutenberg. Would it
 be possible to fallback to the `hex` value in this case?

 Unless I'm mistaken, that would be on the theme to not provide a name for
 the custom color, which would then trigger the behavior you describe in
 falling back to the hex value.

 Or, do you mean: Still allow the custom color to be named "Primary" or
 "Secondary", but otherwise provide a hint to Gutenberg to assign the
 `aria-label` as announcing the color code instead of this name? I could
 imagine a separate property of the colors object entry, e.g. `'dynamic' =>
 true` (`userSelected`, etc).

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