WordPress.org

Make WordPress Core

Opened 12 months ago

Last modified 9 months ago

#48998 new enhancement

:active buttons in 5.3.1. all look the same in different user colour schemes

Reported by: studiotwee Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.3.1
Component: Administration Keywords: needs-design-feedback
Focuses: ui, css Cc:

Description

This is a follow-up to #48598.

Are we sure that completely removing the custom button style when not hovering over a button is a good fix for this? In 5.3.1, all buttons have a blue outline, no matter if you are in :hover, :active or in default status.

In the screenshots below you can see the different :hover actions.

Default Colour Scheme
https://i.imgur.com/RbKr49C.png

Midnight Colour Scheme
https://i.imgur.com/vtXECXE.png

Ocean Colour Scheme, non-hover
https://i.imgur.com/QXMUR0p.png

Ocean Colour Scheme, hover
https://i.imgur.com/2BxEdd9.png

I'm all for a11y and this is a vast improvement over how it was, but it seems the buttons lost a bit of flair with this update. The buttons look incredibly boring and are not as in-your-face as they were before.

Change History (5)

#1 @SergeyBiryukov
12 months ago

  • Focuses ui accessibility css added

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


12 months ago

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


9 months ago

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


9 months ago

#5 @afercia
9 months ago

  • Focuses accessibility removed
  • Keywords needs-design-feedback added

This ticket was discussed during today's accessibility bug-scrub. @studiotwee thanks for your report. To our (a11y team) understanding this relates only to the various "Add new" buttons, correct?

The "Add new" use different CSS from the default buttons and they went through some recent CSS changes. Regardless, it appears this is more a design / UI issue rather than an accessibility one. Adjusting the ticket properties accordingly.

Note: See TracTickets for help on using tickets.