Web?
For $REASONS, I ended up in control (probably temporarily) of a rather introductory «Web Development» course with a bit of HTML/CSS/JS/Docker that I plan (and promised) to keep in a mostly recognisable shape. I do want to add more reminders that progressive enhancement is good, though; and I ask for advice on good points/references. I am going to keep NodeJS backend assumption, so any JavaScript-the-language feature can be demonstrated on backend. So just learning to use JS in general is not as much of an excuse for silly things in-browser. My plan includes telling more than before about (and probably giving links to): https://madcampos.dev/blog/2026/07/accessibility-from-scratch/ — usability and accessibility benefits of proper HTML https://shkspr.mobi/blog/2021/01/the-unreasonable-effectiveness-of-simple-html/ — accessibility in wider sense of things that work on pure and minimal HTML https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies/defaultjavascriptjitsetting — MS Edge having a secure mode where JS JIT is off (and JS is slow) https://developer.chrome.com/blog/timer-throttling-in-chrome-88/ — even Google admits that JS is bad for battery life… https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html — as a reminder not to trust too much work done on frontend https://github.com/lwthiker/curl-impersonate — for general trolling (more seriously, to remind how many sites pretend to need JS but give Blink-based browsers fully sufficient HTML, then try to make it hard for any other browsers, and often fail) And I guess general stressing that document, form, and application are three different things. I would be grateful for suggestions of other/same-but-well-made points towards progressive enhancement, not spending extra effort to break accessibility, etc. Ideally I hope to cover what has normally been covered previously, but with a viewpoint shift towards healthy approaches. Active improvements to accessibility are probably beyond what would fit and beyond what I can explain well.
This is a summary aggregated from Lobsters. Read the complete article on the original site:
Read full article at Lobsters