|
3 posts total
Web Platform Baseline, recently re-announced by Google Chrome, does not consider browser support for #accessibility features built into the web platform. Accessibility is a fundamental requirement for devs (legal compliance, contracts). Yet Web Platform Baseline does not actually cover baseline support. I am still confounded people use ‘MPA’ to mean ‘web pages’ because ‘SPA’ proponents convinced an industry that web pages were bad but now those same people realize SPAs were built on hubris and lies (as opposed to open and scalable standards). @aardrian Thank you! "Browser navigation is slow because we throw MBs of JS into each request so we solved a problem we created by making SPAs" 🤡  @aardrian I use it as a deliberate juxtaposition because SPAs are still actually webpages. Just like we should always ask “Could this meeting have been an email?” …we should always ask “Could this PDF have been a web page?”
Show previous comments
 |
Gregory's Server
@aardrian Another (lesser) thing: I'd love for Baseline to indicate how gracefully a new feature degrades.
I'm not a fan of encouraging "evergreen browsers".
@aardrian ...and it simultaneously fails to highlight which engines need to catch up to make the situation better for developers! There's a huge risk that "baseline" mostly serves to reduce pressure on laggards by steering developers away from features they really should be using.