4 ms·

Since the article's main point is that you should use semantics as much as possible, it's probably better that you used the "wrong" tag when choosing between <s

Since the article's main point is that you should use semantics as much as possible, it's probably better that you used the "wrong" tag when choosing between <section> or <article>, than using the wrong tag and choosing <div>s for lack of not even having asked the question "what should this be?". While rewriting what's already out there may be a business decision, choosing between what HTML tag to use when changing/writing new ones, is completely business agnostic.

player2121 7y ago
There are plenty of apps out there where you cannot apply HTML document semantics or that would be a waste of time (money) doing so. If using canvas or web-assembly would be easier/possible than using HTML tags for a rendering layer, nobody would ever disturb the HTML document designers with this div "soup" :) Semantic HTML serves 2 purposes: lets search engines correctly index your content and makes it easier for a human to edit this HTML directly. Other than that, there is no other reason which requires semantic HTML. True accessibility is achieved through other means.