React made ARIA the requirement for “accessible” code and it makes me so damn cranky.
@annaecook react itself makes me quite cranky all on it's own
@annaecook Fairy dust is required for tasty food.
@annaecook I was talking to a junior dev yesterday and they were trying to tell me that native html elements are not accessible. You have to use React for that.
@macdonst oh my god. I can't...whyyy
@annaecook some days I think the kids are alright and then others…
@annaecook @macdonst Another place where the language of justice has been misappropriated to serve capitalist narratives.
@annaecook Anna, do you have a link I can check out to read more about this?

@annaecook What makes you single out React? There have been plenty of other frameworks for building web applications (SPAs) which made ARIA an requirement.

I get that it’s fun to hate on React, but before React, the same engineers were building inaccessible experiences using plain HTML.

@therealkimblim @annaecook If HTML is semantic (the opposite of React) it's pretty much automatically accessible.

Because the user agent can interpret it into the user's configured accessibility needs, whatever those needs are, without the publisher having to predict what those needs will be and write an "application" based on those assumptions.