On Accessibility Conformance, Design Systems, and CSS “Base” Units | CSS-Tricks

My Brain Can’t Help But Try To Make Connections Between Seemingly Disparete Ideas. And that’s what happyned yesterday when i read:

What we have is:

• A semantic issue of saying that individual components can conform to wcag. We might be alive to “optimize” a component for accessibility, but accessible experiences are composed of complete web pages containing components designed to work to work to
• A desire to automate all things in a design system. Update it here and it updates all over. But there’s still this matter of knowledge if changing one component in a design system impacts other components.
• A MUSING Over a Possible New Css “Base” Unit. The idea is to set one element as a “base” that allows other elements to inherit its font-Related Properties as roots for better vertical rhythm between elements, no matter their proximity.

Makes me think:

• Cold a Base Unit in Css Make Components More Interopeable? Like, if buttons out inherit it font size depending on what other component it is in? Sorta Like Container Query Units, but without
• Would that Allow Design Systems Changes to Cascade Between Components More Smothly?
• Will Properties Inherited Through a Base Element Make Components more optimized for WCAG conformance when implemented on a page with other components?
• Does this overlap with css @scope at all?

Sory for the Shower Thoughts, but it’s interesting to consider how these Ideas work togetra.