My mind can’t assist however attempt to make connections between seemingly disparate concepts. And that’s what occurred yesterday after I learn:
What we’ve is:
- A semantic situation of claiming that particular person parts can conform to WCAG. We would have the ability to “optimize” a part for accessibility, however accessible experiences are composed of full internet pages containing parts designed to work collectively.
- A want to automate all issues in a design system. Replace it right here and it updates throughout. However there’s nonetheless this matter of realizing if altering one part in a design system impacts different parts.
- A musing over a attainable new CSS “base” unit. The thought is to set one component as a “base” that enables different components to inherit its font-related properties as roots for higher vertical rhythm between components, regardless of their proximity.
Makes me suppose:
- Might a base unit in CSS make parts extra interoperable? Like, if buttons may inherit its font dimension relying on what different part it’s in? Sorta like container question items, however with no need extra wrappers within the markup.
- Would that enable design programs adjustments to cascade between parts extra easily?
- Will properties inherited by a base component make parts extra optimized for WCAG conformance when applied on a web page with different parts?
- Does this overlap with CSS
@scopein any respect?
Sorry for the bathe ideas, nevertheless it’s fascinating to think about how these concepts work collectively.
