"I've said it before and I'll say it again, but as long as this situation continues, Safari is not an evergreen browser. (I also understand that problem lies with the OS architecture--it must be incredibly frustrating for the folks working on WebKit and/or Safari.)"
"Designing for many means designing for demographic groups whose needs and expectations differ from ours. Our unconscious biases typically keep us in our comfort zones and stem from systemic social constructs that have historically been an anti-pattern for inclusivity."
"Links and buttons have different keyboard triggers (both can be triggered with enter but buttons can also be activated with a space) and if you're a sighted used, you might expect a button and be surprised when space does nothing."
"In the last 10 years tooling has come and gone, frameworks and libraries have been sun-setted, and brand new possibilities like Cascade Layers have been made possible on the Web Platform. But the usefulness and resilience I have enjoyed from a good CSS naming convention has not diminished."
"I'll admit this is a case where WCAG can be confusing-at least it was for me. The Non-Text Contrast criterion (1.4.11) does mention leveraging the rationale for "large-text contrast" in Contrast minimum (1.4.3), which has the 3:1 ratio. But it wasn't immediately clear that text inside of a user interface component would fall under the different success criterion."
"Don't overcomplicate decision points. What we should have done was had a simple, fairly static semantic theme palette for general design use, and then have components use their own palettes with hyper-specific token aliases (based on Nathan Curtis' fantastic article on token naming)."