#38150 closed defect (bug) (duplicate)
Stop using dashicons to show checked state of checkboxes
Reported by: | EmpireOfLight | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Administration | Keywords: | color-contrast form-controls |
Focuses: | ui, accessibility | Cc: |
Description
Checkboxes should use the default system to indicate they are checked. (<input type="checkbox" checked> uses a dashicon check icon instead of the system's default check ui.
Attachments (1)
Change History (12)
This ticket was mentioned in Slack in #design by empireoflight. View the logs.
8 years ago
#4
@
7 years ago
Is the issue here that the browser's default is being replaced, or that the font color of the dashicon checkmark doesn't meet AA standards? The contrast ratio is 3.78, so if we're just worried about contrast here, darken the blue and we're done.
No need to decouple the dashicon system's that has been built on top of the browser default if all we have to do is improve the color a bit.
Update:
[WordPress Blue, 0073AA](http://codepen.io/hugobaeta/full/RNOzoV/) fulfills our color contrast goal without swapping out the SVG implementation.
#5
follow-up:
↓ 6
@
7 years ago
The issue arose when testing svg replacement of the dashicons font in the admin, the checkbox and radios broke and would need to be re-coded (see https://make.wordpress.org/core/2016/10/23/converting-dashicons-to-svg/) . Rather than adding those to the list of fixes, it makes more sense to leave form rendering/chrome to the browser. The admin recently switched to system fonts, and similarly, removing the extra layer of styling might even be a performance boost.
#6
in reply to:
↑ 5
@
7 years ago
Works for me :)
@afercia, should we drop this one from the Color Contrast project as a result?
#8
@
6 years ago
- Keywords form-controls added
- Milestone changed from Awaiting Review to Future Release
Checkboxes use a checkmark dashicon, but they should just use the normal built in browser styling