Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There are several things to consider:</p> <ol> <li>First, validation doesn't mean that much, because an HTML page can very well be valid but badly authored, inaccessible, etc. See <a href="http://www.cs.tut.fi/~jkorpela/html/validation.html#icon" rel="nofollow noreferrer">Say <em>no</em> to "Valid HTML" icons</a> and <a href="http://hixie.ch/advocacy/xhtml" rel="nofollow noreferrer">Sending XHTML as text/html Considered Harmful</a> (in reference to the hobo-web tests mentioned in another response)</li> <li>Given this, I'd highly recommend using the new DOCTYPE: the only reason for having it in HTML5 is that it's the smallest thing that triggers standards mode in browsers, so if you want standards mode, go with it; you have little to no reason to use another, verbose, error-prone DOCTYPE</li> <li>As for the forms enhancements, you can use Weston Ruter's <a href="http://code.google.com/p/webforms2/" rel="nofollow noreferrer">webforms2</a> JS library to bring it to non-aware browsers</li> <li>and finally, about the <code>data-*</code> attributes, it a) works in all browsers (as long as you use <code>getAttribute()</code>), b) is still better than abusing the <code>title</code> or <code>class</code> attributes and c) won't bother you with validation as we said earlier that validation isn't <em>that</em> important (of course it is, but it doesn't matter that your page is invalid if the validity errors are willful; and you can already use HTML5 validation in the W3C validator, so...); so there's no real reason not to use them either.</li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload