4 ms·
Wouldn't raw html be better for accessibility than a JS framework? Saying this as a non-front end dev.
by the_real_cher 3y ago
Wouldn't raw html be better for accessibility than a JS framework? Saying this as a non-front end dev.
- ivan_gammel 3y agoIf done correctly it doesn’t matter. SSR can yield an accessible HTML page and you won’t notice the difference. Client-side JS can adapt the web site to your needs -a personalization that is hard to achieve in static.
- marcosdumay 3y agoWhen was the last time... Or rather, when have you ever seen a framework-based page with accessibility done correctly?
- ivan_gammel 3y agoI have seen many sites scoring well on various accessibility metrics. There’s no inherent technical limitation of frameworks that would make accessibility impossible, even when dealing with text to speech. We will see many more next year with EAA coming into effect (and many European companies do care about compliance).
- jilijeanlouis 3y agoDespite regulation I don’t Believe it will actually get implemented even governments have regulations around audio accessibility for education in particular, for years now, and still nothing moves.
- Conlectus 3y agoRaw HTML: potentially. Big blocks of undifferentiated ASCII art: no.