The WCAG (1.0) guideline 4, checkpoint 4.2, about ABBR and ACRONYM, has for a long time been too unclear to implement. The drafts for XHTML 2.0 and WCAG 2.0 seem to have solved most problems.
With HTML5 markup in place I started wondering about how CSS would affect things. The first thing I discovered was that Firefox doesn't have much in the way of default styling for the new elements - so setting background colours doesn't have much effect until I added some default styles.
Unlike its predecessors, CSS3 is not a single, monolithic spec, but a collection of modules all of which are at different levels of completeness. For instance the selectors module became a candidate recommendation in November 2001 and is already widely supported. In this post I'm going to be experimenting with the Backgrounds and Borders module and the Transitions module, mostly because the recent Firefox 3.5 release includes improved (but still experimental) support for some of the more interesting bits of it.
There are some new CSS3 features supported in the latest Chrome release and Firefox alpha which make this worth a second post. This time I'm going to focus on background sizing, CSS gradients and RGBA colours.
It has become evident to me that some of my previous comments about HTML 5 and what is going on in the HTML Working Group are the result of misunderstanding and overreacting on my part. I no longer think things are quite as bad.
For most end-users, the debate over Flash is largely a debate about web video. Yes, Flash is used in other ways — for web-based games and ever-decreasingly in website design — but thanks in large part to YouTube, Flash is most commonly associated with web video. Web video is overwhelmingly encoded in H.264. Not only is the H.264 codec the default encoding setting for practically every video service online, it is also by and large the default codec for raw video from digital video cameras.
Answers to questions like: where do Web pages come from? What are all those brackets in the text, anyway? How much HTML do I have to learn? How can I get started quickly? What kinds of HTML authoring tools are available to me?
If you don’t already understand the markup language known as HTML, there’s not necessarily a compelling reason for you to learn. However, if you’d like a better idea of how web pages work, then it’s worth taking some time to understand the underlying concepts. In today’s post, and the ones that follow in this series, I’m going to introduce the basics of how to create HTML documents.
You can link to any tag within the page by quoting its ID. For example, if you have a paragraph with an ID of "intro", then you can link directly to that point without having to insert a bookmark.
HTML is the unifying language of the World Wide Web. Using just the simple tags it contains, the human race has created an astoundingly diverse network of hyperlinked documents, from Amazon, eBay, and Wikipedia, to personal blogs and websites dedicated to cats that look like Hitler. HTML5 is the latest iteration of this lingua franca. While it is the most ambitious change to our common tongue, this isn’t the first time that HTML has been updated. The language has been evolving from the start.
The HTML5 VIDEO element is already supported by most modern browsers, and even IE has support announced for version 9. There are many advantages of having video embedded natively in the browser (covered in the article Introduction to HTML5 video by Bruce Lawson), so many developers are trying to use it as soon as possible. There are a couple of barriers to this that remain, most notably the problem of which codecs are supported in each browser, with a disagreement between Opera/Firefox and IE/Safari. That might not be a problem for much longer though, with Google recently releasing the VP8 codec, and the WebM project coming into existence. Opera, Firefox, Chrome and IE9 all have support in final builds, developer builds, or at least support announced for this format, and Flash will be able to play VP8. This means that we will soon be able to create a single version of the video that will play in the VIDEO element in most browsers, and the Flash Player in those that don't support WebM natively.
Depending on who you ask, HTML 5 is either the next important step toward creating a more semantic web or a disaster that’s going to trap the web in yet another set of incomplete tags and markup soup. The problem with both sides of the argument is that very few sites are using HTML 5 in the wild, so the theoretical solutions to its perceived problems remain largely untested. That said, it isn’t hard to see both the benefits and potential hang-ups with the next generation of web markup tools.
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.
In this article I will look at the doctype in a lot more detail, showing what it does and how it helps you validate your HTML, how to choose a doctype for your document, and the XML declaration, which you’ll rarely need, but will sometimes come across.
As of this writing, HTML and XHTML are both being used to create Web sites. But there are multiple versions of each, with specific changes and ideas attached. The following table shows the current W3C HTML and XHTML recommendations of note.
Calendars, colour swatches, sliding widgets, client side validation: this is the nirvana that the HTML5 forms module promises. Some would say “So what? I’ve seen this on the web for years!”, and they’d be right. There have been some really brilliant people coding some really interesting widget and validation frameworks, so why should we change?
The HTML 5 video element has the potential to liberate streaming Internet video from plugin prison, but a debate over which codec to define in the standard is threatening to derail the effort. Ars takes a close look at the HTML 5 codec controversy and examines the relative strengths and weaknesses of H.264 and Ogg Theora.
You may well ask: “How can I start using HTML5 if older browsers don’t support it?” But the question itself is misleading. HTML5 is not one big thing; it is a collection of individual features. So you can’t detect “HTML5 support,” because that doesn’t make any sense. But you can detect support for individual features, like canvas, video, or geolocation.
This three-part article outlines a common sense, cost-effective approach to Web site acceleration according to the two simple laws of Web performance: send as little data as possible; send it as infrequently as possible.