FEDIDEVS

@julia_miocene Do you have to put a “No Divs Were Harmed in the Making of This Character” disclaimer next to your creations?

#CSSDay 🤯

Thanks @fantasai and everyone in the Web Standards world for doing what you are doing. The people in this #CSSDay church and online would probably not have the career they’re having without you.

Live at #CSSDay 2024. 🙌
https://cssence.com/2024/cssday/

I limit inline styles to #CSS custom properties.

https://cssence.com/2020/css-variables-in-style-attributes/

(Also makes things easier on #CSSNakedDay.)

#CSSDay

Big yes to `reading-order-items`, #A11y FTW!

That said, I don't wanna be a browser maker having to implement this. 😰

@rachelandrew #CSSDay

Here’s hoping I’ll use that #CSSDay hashtag wisely. (But feel free to mute me until the end of the week.)

I’ll start with a question for @adactio and @mia: How does MCing feel compared to giving a talk?

Ah yes, `.visually-hidden`, curious to see where we are heading on that front.
https://cssence.com/2024/native-visually-hidden/

#CSSDay #A11y

I remember @tink talking about a Firefox flexbox “bug” that changed tab order at my first #CSSDay eight years ago. It’s really important that we get ways to manage tabbing and reading order.

https://cssence.com/2016/cssday/#comment-25

@rachelandrew #A11y

The original sin(). 😶

@matthiasott #CSSDay

@pixelambacht Mission (already) accomplished, many times over. 👏

#CSSDay