Hacker News Reader

Sorry, I don’t buy it. There’s nothing “expert-tier” about plain accessible HTML, and with LLMs, there’s even less excuse. I’m not primarily a frontend web engineer and I can manage it.

View on HN

Yes, I’m certain you can “manage it” despite not considering things like screen readers, page layout reversals, mobile responsiveness, working with legacy codebases that are 30 years old (when was the last time YOU had to update a site that simply must shut down every night for processing?), etc.

Everything looks easier from the outside. Maybe we should focus on getting private corps to provide a small amount of accessibility before forcing onerous requirements on our already-underpaid civil servants?

We're talking about governmental document-like websites with relatively simple forms here, not your particular legacy web app, there is no excuse for not getting them right. Gov.UK did. Plain HTML, used in a straight-forward way that is very clear from the approachable documentation on, say, MDN, is already responsive, readily consumable by screen readers, and works with any backend that already exists. If you have to fix a mess left by someone else you have my sympathy - I've been there too. But the original post is appealing to people who have a choice between plain, standard-use HTML, and any alternatives. And yes, I'm all for much harsher penalties for private companies that produce inaccessible web sites/apps too.

Reply on news.ycombinator.com