3 ms·

You mean people don't read webpages without a screen-reader? There's no such thing as Reader mode? Web developers don't read HTML and want to write it in an o

You mean people don't read webpages without a screen-reader? There's no such thing as Reader mode? Web developers don't read HTML and want to write it in an organized way? Sure, there should be nothing outside of accessibility. /s If you read the post (and I can't really blame you for not reading it all the way through), you'd see that the author is suggesting that there are reasons besides supporting accessibility features for using these semantic HTML tags. I just don't agree that they are objectively good reasons for why one "should" do so. Oh yeah, and semantic HTML is by no means the only way to write pages that are accessible. Everything that a semantic tag can do, the role attribute can do, too. I never said to not care about accessibility.

bXVsbGVy 4y ago
There is also portability. If you use main, article, etc is easier to write apps to process the page. Firefox reader mode use the main element to know how get the text from the page.
extra88 4y ago
> Everything that a semantic tag can do, the role attribute can do, too. <button> does far more than <div role=button> can do. Even if you meant to only refer to landmark roles, why write <div role=main> or <div role=region> when you can write <main> and <section>? As someone else pointed out, Reader modes don’t recognize roles and user stylesheets don’t either.