Chat Summary: 7th May 2020…

CSSCSS Cascading Style Sheets. Chat Summary: 7th May 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1588885269423200

I (@notlaura) facilitated the meeting.

CSS audit updates

It’s not specifically part of the audit inititive, but let’s celebrate: CSS for unsupported IE versions was removed in commit 47771. 🎉

Color Scheming Updates

@ryelle experimented with custom properties for color schemes in a Gutenberg PR and left comments on the Iterating on Color Schemes ticketticket Created for both bug reports and feature development on the bug tracker., and mentioned that @nrqsnchz & @joedolson will be working on the design and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) side of color schemes.

Also for reference is the Dark Mode project which was not merged due to the difficulty in overriding CSS in parts of the adminadmin (and super admin). Part of the work to do regarding the color schemes initiative is to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it so that we can have dark mode, and a solution that allows control of all colors in the admin.

I mentioned the design systems practice of abstracting colors (the design tokens) into contextually named custom properties, and offered to add a comment to the ticket.

That was all for this week!

#summary #core-css