Had we learned and implemented style sheets well, especially the Cascade and the original use of the !important declaration the answer would be user style sheet. I fully Sarah's assessment for today's real #a11y priorities. Not preference really. Dark mode compromises my vision.
Ahmad Al-Shagra | ابو المنتج
 @afahad
3 Jul 2021
@mholzschlag how do you feel about this from an #a11y predictive? I'm for more standardized approaches users are used than efficacy e.g Qwerty vs Dvorak etc

Jul 4, 2021 · 12:17 AM UTC

2
5
Replying to @mholzschlag
I don't know that I agree. I've been trying to explain to folks that CSS in JS screws with user styles, making users have to modify or switch their workarounds. The response has pretty much been "meh, development needs are more important". I'm not sure it was about us.
1
I'd agree with the "not about" us in "just us" - it's a lot of factors. But we did land a steamy mess on backward compat, iterop, -- stuff the Web was meant to mitigate at best... :)
Replying to @mholzschlag
Mobile is changing the landscape at a fundamental level. The technical #a11y aspects web delivered, are being reinvented for mobile/watch/tablet...etc It's as if every new viewport development tribe starts over. Perhaps techie culture lacks transgenerational a11y story telling
1
1