Account services

Semantically correct HTML

You should create semantically correct HTML thinking on how applications interpret it more than how users view it. Machines cannot tell you that they misunderstood since they are not aware of it, so there's no automatic validation for semantic markup. Respecting Web standards (XHTML, WAI, XML, etc.) does not ensure semantically correct pages.

Markup guidelines

Good semantic HTML structure is based on logic, order, and using semantically correct markup. Those elements provide meaning to the content, making them semantically correct, in addition to being solid HTML structure.

Why?

The benefit for EEA is that content that is tagged semantically is much easier to style consistently, and it is easier to change the style globally. Semantically correct XHTML is easier to repurpose. We can convert it to PDF and lists will remain lists. We can embed it in other XML formats and not have surprises.

References