Posts related to the W3C HTML Working Group and the HTML 5 specification that is currently being worked on.
Having built-in semantics and accessibility in HTML5 is great, but I think we also need specifications like WAI-ARIA that let us add accessibility to less than ideal markup.
HTML5 adds many new types of useful form controls. Some browsers support some of them already.
A platform preview of Internet Explorer 9 is now available for download. News include better performance and improved support for HTML5, CSS3, DOM, SVG, and XHTML.
HTML5, HTML: The Markup Language, HTML5 differences from HTML4, HTML+RDFa, HTML Microdata, HTML Canvas 2D Context, and Additional Requirements for Bidi in HTML.
The W3C HTML Accessibility Task Force will help ensure that HTML 5 provides features to enable Web content to be accessible to people with disabilities.
Vlad Alexander argues that web browsers should display error messages for corrupt HTML 5 and invites Ian Hickson to debate on this topic.
HTML 5 does not have the same strict syntax rules that XHTML does, which opens up for problems in teams of developers and makes teaching HTML more difficult.
Jeffrey Zeldman on how the stricter and clearer rules of XHTML 1.0 made many web professionals improve their markup.
Looking for input from screen reader users with regards to the usefulness of the summary attribute for data tables and the information provided in it.
The current HTML 5 Working Draft lists the summary attribute as an obsolete but conforming feature and tells authors to provide table information to all users.
Sam Ruby, co-chair of the W3C HTML Working Group, has put together a number of select quotes to illustrate the evolution of HTML, from the beginning to where it is now.
In the current editor’s draft of the HTML 5 specification, the alt attribute for images is no longer required. I am not convinced that this is a good idea.
I left the W3C HTML Working Group in July 2007 and rejoined it in August. Here is why.
The HTML Working Group is required to cooperate with the Web Accessibility Initiative to ensure that HTML 5 enables accessibility.
Further thoughts on the HTML Working Group and HTML 5, plus a few suggestions.
Tommy Olsson comments on the possibility of backwards compatibility and standardised error handling being bad for overall code quality.
If you think accessibility and semantics are important and should be improved in the next version of HTML, you need to act.
Browsers claiming to support HTML 5 are required to treat all text/html content according to the HTML 5 specification.
The new W3C HTML Working Group really is open to the community of Web professionals. Consider joining. I did.