3 ms·
> Sure, you can make a non-JS fallback version of your interactive elements, but that often takes twice as long This is largely just not true and the results a
by ogre_codes 6y ago
> Sure, you can make a non-JS fallback version of your interactive elements, but that often takes twice as long
This is largely just not true and the results are often no-entirely-legal. The majority of interactive controls can be supported by extending and styling bone stock html and using progressive enhancement. The only way it takes less time to roll your own solution for most of these components is when you don't bother implementing accessibility for your controls.
That isn't just a few esoteric users at this point, you are now brushing up against the ADA and have just exposed your site to potential legal action, lawsuits, and a big honking fine. (Not to mention the fact that you being an ass to a bunch of people who need that functionality.)
- mikl 6y agoNonsense. Anything that interacts with the server with AJAX and the like, or does client-side rendering will need a completely separate implementation to work without JavaScript. As for the ADA, there’s nothing in there that demands your site works without JavaScript, it just has to be accessible to screen readers and the like, which all support JavaScript.
- ogre_codes 6y agoAh, gotcha. I didn't realize you were thinking about web requests.