I would argue the biggest contributors to bad accessibility are browsers themselves.
We still don't have a <select> element that style itself even remotely nicely. Let alone looking alike within multiple browsers. This is single-handedly probably the biggest contribution ever to non-accessible website since the dawn of internet.
<dialog> is nowhere supported enough yet and if I'm not mistaken, people are already picking out stuff out of the few browser implementations that isn't accessible.
There's no such thing as a native menu... Like it's not been what? 20 years we need that component?
Don't start me on date pickers...
Then we have companies like Igalia asking for funding to implement plenty of features in different browsers... Features that should have been implemented by the browser's companies themselves.
Which is infuriating when you think about it, because Microsoft, Google and Apple are 1+ trillion market cap companies!!! Are you telling me they don't have ressources to fix their s***???
I will also point my big fat finger at Safari here, this is the new IE by a long shot. And yet, it's made by the richest company on Earth... They certainly don't need extra funding or Igalia to do their job...
And finally, there is not 1 day without an article asking us, developers, to make our sites accessible...
I think it's high time, we, as developer, get the pitchforks out!
P.S. I'm all for making our sites accessible, I always strive to, but I think there's a mountain of work to be done by the browsers and they're letting us do all the work.
I'd argue that Chrome is the new IE by a long stretch:
Has an almost monopolistic position, and even other browsers (Opera, Edge, etc) have switched to the Chromium engine because it's more cost effective than chasing Chromes new CSS features that aren't spec.
Implement their own features that aren't in the spec. Most of the -webkit- prefixes in CSS are their fault, and is developers use them for core behaviour rather than progressive enhancement, meaning a lot of websites don't work well on other browsers (Fx & Safari)
They're removing features that have been part of the web for decades (alert(), confirm(), & prompt() in cross-origin iframes) which cause huge functional and accessibility problems.
So much of this reminds me of some of the very same things that Microsoft was doing in the early IE era (4 - 5.5).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would argue the biggest contributors to bad accessibility are browsers themselves.
We still don't have a
<select>element that style itself even remotely nicely. Let alone looking alike within multiple browsers. This is single-handedly probably the biggest contribution ever to non-accessible website since the dawn of internet.<dialog>is nowhere supported enough yet and if I'm not mistaken, people are already picking out stuff out of the few browser implementations that isn't accessible.There's no such thing as a native menu... Like it's not been what? 20 years we need that component?
Don't start me on date pickers...
Then we have companies like Igalia asking for funding to implement plenty of features in different browsers... Features that should have been implemented by the browser's companies themselves.
Which is infuriating when you think about it, because Microsoft, Google and Apple are 1+ trillion market cap companies!!! Are you telling me they don't have ressources to fix their s***???
I will also point my big fat finger at Safari here, this is the new IE by a long shot. And yet, it's made by the richest company on Earth... They certainly don't need extra funding or Igalia to do their job...
And finally, there is not 1 day without an article asking us, developers, to make our sites accessible...
I think it's high time, we, as developer, get the pitchforks out!
P.S. I'm all for making our sites accessible, I always strive to, but I think there's a mountain of work to be done by the browsers and they're letting us do all the work.
I'd argue that Chrome is the new IE by a long stretch:
-webkit-prefixes in CSS are their fault, and is developers use them for core behaviour rather than progressive enhancement, meaning a lot of websites don't work well on other browsers (Fx & Safari)alert(),confirm(), &prompt()in cross-origin iframes) which cause huge functional and accessibility problems.So much of this reminds me of some of the very same things that Microsoft was doing in the early IE era (4 - 5.5).