This is hilariously silly from a developer perspective because Safari exists. Safari is literally the bane of my existence in WebDev because it’s usually the browser that does something weird and not according to standards (which is classically the IE problem). Apple WebKit has significantly deviated from KHTML/Blink in ways that are worse for developers. Chrome does inject defaults to standard interfaces to make websites “work better” where Firefox is much more strict about the standard.
To pretend that Chromium/Blink/V8 is worse than Firefox or any other competitor is just burying your head in the sand. Blink and V8 are extremely highly optimized and standards driven, there’s a reason Node didn’t choose SpiderMonkey. Dev Tools have significant difference in speed and usability, and I’m a Firefox daily driver and use it for development.
What Google is doing that’s ridiculous and stupid is using it’s weight to influence the design of Chromium such as the deprecation and removal of Manifest V2 to prevent adblockers under the guise of “safety” or whatever, as well as driving more telemetry and anti-features into the Chromium core product.
Also of course “MagicLasso” doesn’t say Safari is the IE because it’s a adblocker for Safari. lol
Honestly the “old web” was also a hellscape for accessibility.
There’s been a lot more advances for accessibility in the last 5 years because of ADA lawsuits being successful against large companies with websites, so it’s seen as a liability.
In my personal experience in general this has been a big impetus for companies to start take WCAG seriously. However in practice a lot of this is box checking because it’s expensive and complicated.
A lot of our newer contracts have had explicit terms for various levels of accessibility, but this has lead to a problem in the sense that accessibility is something that is designed, and in practice the company has a very hard time changing it’s SDLC in most teams. So in effect the expectation from higher ups is that it’s a magic wand, these kinds of top down initiatives fail because they’re often just having people internally rewrite a11y tutorials or act as consultants to projects they know don’t have the resources to actually become accessible.