I honestly believe that the groupthink allowing people to think of performance as equivalent to a11y is resulting in a failed regime that attempts (but fails) to push the responsibility onto end developers and doesn't accomplish its own stated goals.
-
-
-
"secure by default" was an acknowledgement that applying this kind of thinking to security is catastrophic. It's like teaching people to cook with chainsaws and adding a chainsaw safety class to the beginning of the course.
-
The same is true about performance. Web browsers and frameworks working together to improve performance by default is the only way forward.
-
Incidentally, one success story: modern frameworks are naturally much much better at phasing DOM reads and writes than the jQuery style of coding in large part because web frameworks took the problem seriously in collaboration with web browsers.
-
Mhh, I half agree. A11y is more of a necessity, as slow sites *can* still be used (by those with fast connections). I also love your utopian idea of a 'fast by default' web, but to my knowledge, no programming environment ever achieved that.
-
What we have now is slow by default, and web browsers thinking they can solve it by reaching each individual developer one person at a time when people are mostly working on adding features for their job.
-
If you follow it to its conclusion, you get the increasingly shrill (and ineffective) shaming campaigns we've seen come out of Google in the past and which I don't want to see crop up again. If you're worried about TTI, pervasive route-based code splitting would do a lot.
-
Concrete ideas like building: code splitting, tree shaking, DOM phasing, more work off the UI thread into frameworks will go much further than trying to get already-burdened curricula to cover the low level details that people can use to try to do it themselves.
- 3 more replies
New conversation -
-
-
-
I think a11y is something we should encourage from an early stage, but mostly by pointing people in the direction of semantic HTML and teaching them to look out for GUI libs that claim to care about a11y.
-
The a11y community has been very effective at creating standards and great GUI libs that use them, and most of the time when a lib claims to care it works decently (and if it doesn't, they'll happily take bug reports and fix ASAP)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.