Posts related to the W3C HTML Working Group and the HTML 5 specification that is currently being worked on.
When using the HTML5 sectioning elements, make sure the document outline created by the headings is backwards compatible.
The placeholder attribute is meant to give the user a nonessential hint before filling in a form field, not replace the label element.
HTML5 allows links to contain block level elements instead of just inline elements. This can be useful but there are currently potential usability issues with screen readers.
The outline algorithm in HTML5 lets you use only h1 elements for all heading levels and still get a proper document outline. But browser and AT support is lacking, so use with care.
HTML5 and several closely related specifications have reached Last Call status, and the W3C has called for broad review of the documents.
My current thinking on document outlines in HTML5 and how and when to use the new sectioning elements, all with HTML4 compatibility in mind.
If you for some reason have to use the non-standard X-UA-Compatible header to force standards mode in IE, be aware that it is invalid HTML5. Fortunately it is easy to fix.
Getting the document outline you want is not as easy as you might think if you want to use the new sectioning elements in HTML5.
The HTML5 Validator extension for Firefox has received a number of updates and is now hosted on GitHub.
How to automatically validate HTML5 in Firefox by installing a local copy of Validator.nu and my HTML5 Validator Extension.
The WHATWG announces that they will now work on a versionless version of HTML, making it a moving target that may make it less than ideal for web developers to reference in their daily work.
The W3C HTML5 logo FAQ has been updated to clarify what the logo and its accompanying icons represent and that CSS3 is not part of HTML5.
Having a nice-looking logo for HTML5 is neat, but I think it’s unfortunate that the W3C are reinforcing the widespread misconception that HTML5 is pretty much anything “Web” that isn’t Flash.
HTML5 allows almost anything as the value for the id attribute. This opens up possibilites but can also lead to bugs and maintainability problems unless used wisely.
A few guidelines that will help you produce understandable and maintainable HTML5. Executive summary: stick to the syntax rules of XHTML.
Many people mean a lot of things when they talk about HTML5. I think some related technologies are ok to bundle with HTML5, but not CSS.
The longdesc attribute, which can be used to provide a longer description of an image, is currently not included in the HTML5 specification.
I’m looking for a browser extension that supports HTML5 and automatically validates the markup of every page I load in the browser without sending anything to a remote server.
Two types of mistakes that I see every now and then are using end tags on void elements and using self-closing start tags on elements that can have content.