4 ms·
That surprises me. I'm a webdev and I've long considered HN to be a bit of an atrocity in terms of markup and a11y. Nested tables, no sr text to explain the th
by oliwarner 3y ago
That surprises me.
I'm a webdev and I've long considered HN to be a bit of an atrocity in terms of markup and a11y. Nested tables, no sr text to explain the thread structure, JS-only links scattered around. It works but only by the mercy of many text-based browsers being started in the 90s, so they're used to this pre-semantics rubbish.
I can't tell if it's hubris but if I were king for a day, I'd like to think I'd leave HN in a better state. At the very least, I'd clean up the cruft.
- ezconnect 3y agoWow, I never knew HN layout was using tables. That was surprising, all this years and I never checked.
- bbkane 3y agoHN loads large amounts of comments really quickly on my phone's browser and there's no jank or lag when navigating it, and no popups. I love it, especially compared to the pain of using Reddit's mobile site for similar comment-browsing tasks
- lynx23 3y agoThe table layout on the main page is more of a problem for a modern web bgrowser then it is actually for Lynx. Modern browsers will announce the table, and your position in it, which is totally irrelevant on the main page. That is definitely the wrong semantic tag for the job at hand. It should be a ordered-list, because that is what it is. However, most markup things tends to get rendered quite nicely in Lynx. The only thing I notice which I somethimes wish would work differently is the lack of the ability to know who is replying to whom...