3 ms·
Nope, it's not "done right". It's a table layout from the nineties. But probably there's an api so noone would have to scrape a wiki page, I never needed to do
by xab9 8y ago
Nope, it's not "done right". It's a table layout from the nineties. But probably there's an api so noone would have to scrape a wiki page, I never needed to do that fortunately :)
- worble 8y agoAnd what exactly is not "done right" about that? If it displays the information it's supposed to in a clean and organised way, and loads as fast as any other website, then I couldn't care less if it's a '90's table layout' or using whatever the hot new JS framework is.
- Nadya 8y agoTry to read today's Featured Article in a text-to-speech program. The markup is so mangled it can't even read a complete sentence because it breaks anytime the text links out.
- shakna 8y agoJAWS didn't have any issues for me, which reader are you using?
- Nadya 8y agoNVDA - aka the "2nd choice" - but I think it may have been a configuration issue on my end as the markup on the page, after looking into why NVDA was struggling with it, is just a <p> with some <a> in it which NVDA should handle fine.
- shakna 8y agoNVDA can be difficult to configure, for sure. I couldn't get it to play nicely with Sublime, probably my fault. Reason I shelled out for JAWS.
- boomlinde 8y agoJust taking a quick look at the MacOS article posted earlier in this thread, the whole page uses tables exactly as tables should be used: for tables. How do you suppose tables should be implemented? I've seen plenty of idiotic examples of tables being implemented with a bunch of styled <div>, probably because people keep parroting the idea that tables are bad because table based layouts are bad.