4 ms·
I agree with the sentiment, but why is this still attributed to JavaScript. This applies to essentially everything exposed to UX, well beyond JS and web. We did
by flagsarecolored 3y ago
I agree with the sentiment, but why is this still attributed to JavaScript. This applies to essentially everything exposed to UX, well beyond JS and web. We didn’t JavaScript it away, we bad-developered ourselves through a narrowing hallway until a point where we ended up with a black sheep. JavaScript didn’t enable this, there’s as many issues in this space in environments where JavaScript is not even a player, it may have been a carrier but not the root cause.
- austin-cheney 3y agoI don't blame the developers for this at all. I consider myself strong with accessibility and yet at the last job I was intimidated to bring it up. There accessibility was an anti-pattern. At many places they are just struggling to put text to screen. At these places you need a billion lines of code in multiple frameworks to display "hello world". How can you blame the JavaScript developer when nobody knows what they are doing and everybody points fingers at each other? This doesn't just apply to accessibility. It also applies to security, performance, and a variety of other things that never happen unless a law suit is coming or a major client stops paying.