@aral@mastodon.ar.al one small suggestion: you might want to create a ToastWrapper that's always in the page, because live regions should generally be present *before* sending updates
The easiest way to introduce #CSS cascade layers into your existing codebase today:
1. Move your CSS resets into a layer named "reset". Because the selectors in your reset should already be pretty weak, there should be almost no net effect.
2. Move (some of) your third party styles into a layer named "thirdparty". Third-party styles should already have lower priority than your own styles, so this again has very little impact.
All the rest of your styles can continue to stay unlayered.
@aral i'm curious about the choice to use JS interpolation syntax (`${SLOT}`) inside the fragment markup, vs just using HTML (`<my-slot>` or `<Slot>`) 🤔
maybe the fundamental disconnect here is that instead of seeing disabled people as human, techbros see them as a problem that can be "solved" by using more computers
it shouldn't surprise me though. in-person conferences have always been bad at this. the very premise of charging large amounts of money for *physically* bringing people together in a closed room to *look* at slides and *hear* the speaker, is rooted in exclusivity, inequity and ableism.
i am seeing so many conferences returning, being all like "finally, covid is over! we can all have drinks in person", with absolutely no requirements on vaccination/masking/distancing…
it's not like thousands of people are still testing positive every day or anything 🙄
when these conferences also market themselves being inclusive and accessibility-focused, their hypocrisy really shows.