| ABOUT | DATA | RESEARCH | LEARNING | NEWS | PROJECTS & OPERATIONS | PUBLICATIONS | COUNTRIES | TOPICS |
| ABOUT | DATA | RESEARCH | LEARNING | NEWS | PROJECTS & OPERATIONS | PUBLICATIONS | COUNTRIES | TOPICS |
-webkit-* vendor prefix and promising to update the sites under your control.Our goal is to make it easy for anyone to get started contributing to the platform, whether that’s learning more about how it works, teaching others, or writing specs. The web has grown due to people like you, and we want to make it even easier for people like you to give back.The web page is packed full of a generous range of ideas, from how to learn, and how to help other people learn, to how to hack the web and contribute to specs. There are few excuses left when the ideas are well organized allowing you to pick and choose what you, or your organization can handle. I’m impressed with the generosity of time and effort this group of devs have contributed to put this amazing resource together. Don’t miss it — Move the Web Forward!
You can make the web as awesome as you want it to be. Browser vendors, standards editors and library creators actively seek your voice and your contribution. Together we can move the web forward.Also check out Addy Osmani’s article on Smashing Magazine with more details on just how you can help move the web forward.
Web Standards Sherpa’s experts provide helpful, pragmatic and up-to-date advice on best practices for web professionals everywhere.In terms of format, our plan is to bring on amazing authors for a period of 3-6 months or more at a time, with new articles coming out weekly. We’ve kicked things off with pieces by Erin Kissane, Jared Spool, and yours truly; Dan Rubin and Derek Featherstone are on deck for the next two issues.
The current accessibility support implemented in browsers lags behind their implementations of the sexy new features themselves. These are still early days in the implementation of HTML5 features, so lets keep our fingers crossed that Google, Apple (Safari on Windows) and Opera will get their acts together to provide at least a basic level of HTML support in their browsers for assistive technology users. Equally it is hoped Mozilla, Apple (Safari on Mac) and Microsoft will strive to have their rate of accessibility support match their rapid implementation of the new HTML5 features.To address the need for standardizing the implementation of accessibility features, Steve and others have begun working on the HTML to Platform Accessibility APIs Implementation Guide.
This is a good start, but there is still a lot to be done. The main HTML5 logo page still includes non-HTML5 (or event HTML5 web app-related) technologies such as CSS3, SVG, etc. And the Badge Builder still assembles a badge that makes these technologies appear subordinate to HTML5 as opposed to framing them as complementary, but distinct entities. We hope the FAQ change is not the end of their efforts to fix the potential confusion they have caused and that they will continue putting things right over coming days.Is W3C saying that CSS3 is part of the HTML5 specification?
No. However, many HTML5 Web sites and applications do take advantage of CSS3 for styling and presentation.
…we realised that the demand for new features in HTML remained high, and so we would have to continue maintaining HTML and adding features to it before we could call “HTML5″ complete, and as a result we moved to a new development model, where the technology is not versioned and instead we just have a living document that defines the technology as it evolves.At first blush, many of us were a little distraught by this decision because we thought the W3C might decide to follow suit, but after thinking on it a bit, the decision makes sense: the WHATWG can work on the HTML markup language in a fluid way and the W3C can take snapshots of that work and christen it with a version number for reference purposes.
The logo is a general-purpose visual identity for a broad set of open web technologies, including HTML5, CSS, SVG, WOFF, and others.This really isn’t good—I appreciate that it is good to have an umbrella term for a group of related technologies and techniques that would otherwise be difficult to talk about in conversation. “Ajax” and “Web 2.0” serve that purpose well. And it is ok to talk about closely-related specs such as Geolocation and Web Sockets as being under the HTML5 umbrella, as long as you clarify it somewhere (you can find a good example in Get familiar with HTML5!). But this is different—HTML5 and CSS3, for example, are two distinctly different technologies, and should not be confused with one another. To do so will impede learning and cause problems with development, documentation, and all manner of other things.
Badge of Shame, and Bruce Lawson also gave a good view in On the HTML5 logo, as well as providing a good rant to put things straight: HTML5 != CSS3. At Opera, my colleagues and I are constantly reiterating a more accurate definition of HTML5 to help overcome such confusion, and many allies at other browser vendors are doing the same.
Dear W3C,]]>
We are writing to address a major concern we at WaSP (and in the web professional community in general) have with the newly-unveiled HTML5 brand. While we are excited that the W3C is doing so much to promote new technologies being developed, we are incredibly concerned that using “HTML5” as the umbrella for these technologies does more harm than good.
“HTML5,” as a term, has become a bit of a beast and is already presenting problems:
First, you’ve got HTML5 “the spec” which isn’t just HTML markup anymore, but includes specifications for everything from local databases to web workers. Explaining what we mean when we talk about “HTML5” requires use of modifying phrases, as in “HTML5 the markup language” or “HTML5 geolocation”.
Then Apple and Google began promoting the use of “HTML5” as as a catch-all term for marketing their browser advancements, much as Microsoft and Netscape (and journalists) had used “DHTML” in the past. The term became less meaningful because it was being used to cover more ground and, consequently, it made communications between developers and clients more difficult because both sides did not have the same understanding of what HTML5 meant.
Now the W3C has come out and essentially condoned the branding of everything from CSS to actual HTML5 to WOFF as “HTML5”. We can’t imagine a single action that will cause more confusion than this misguided decision (and the W3C has produced some pretty impenetrable specs in its time). Our own Jeremy Keith summed it up perfectly when he said
What we have here is a deliberate attempt to further blur the lines between separate technologies that have already become intertwingled in media reports.We need for the W3C, as a standards body, to understand the importance of clarity with regard to the term “HTML5”. Without being able to draw clear distinctions between technologies, clear communication about those technologies becomes increasingly difficult if not impossible. As an organization of web professionals promoting the inclusion of web standards in the education of future web professionals and the adoption of web standards among practicing professionals, we are deeply concerned that your decision will make our job even harder.
So, when push comes to shove, what do we want you to change? Well, we think a good place to start is backing away from the use of “HTML5” as a catch-all term. If you feel you need a catch-all term, come up with something else, but as Jeremy also said
We [developers] never needed a term to refer to “XHTML 1.0 plus CSS2.1” or “HTML4.01 plus JavaScript” or “any combination of front-end technologies.” Why this sudden all-conquering need for a term that covers so many different technologies as to be completely meaningless?With a new moniker for the umbrella of modern web technologies, the blurred distinction between the diverse languages and systems that comprise it will evaporate and we won’t have to worry (as much) about the potential for miscommunication. Hey, it will even give you a chance to create another logo.
Signed,
The Web Standards Project
canvas; as PPK just confirmed, their CSS3 support is nearly complete; and several benchmark tests put them right up there with Chrome in terms of speed.