Nokia and Apple have privately pushed to give Ogg the noose treatment (and so far succeeded) in HTML5. This destroyed all hope of having free (as in freedom) media embedded in HTML5 in an interoperable way.
Quisiéramos creer que nuestra moral viene de nuestra sana capacidad para emitir juicios racionales… pero eso es solo un deseo. Un fascinante experimento revela lo contrario:
Recuerdan el reciente artículo making a magazine out of WordPress? Hoy podrán ver, en exclusiva, un avance preliminar:
Remember yesterday’s post about making a magazine out of WordPress? Today, you’ll get to see an exclusive sneak peek:
Here are the five most important tenets to keep in mind when building high-quality Web applications. I won’t go into standards compliance here, because that topic has already been debated to death, and the conclusions are old news now. Instead, let’s review the modern tendencies applied in high-quality Web applications:
When writing HTML by hand, these are the most common mistakes that lead to invalid HTML or XHTML:
I’ve been talking regularly about the importance of HTML/XHTML validation in Web pages and blogs.
Well, now, there’s a new reason… or, actually, it’s a pretty old one. Section 508 of the US Rehabilitation Act makes a few requirements for public Web sites and blogs, to improve accessibility for their users.
thTeong WebLog|Blog About Everything asks whether validation is important.
Here’s my take on the issue: it’s very important.
If your content does not validate, your RSS feeds might be broken as well. Most feed readers will barf when fed broken XML/XHTML. That means fewer readers.
Validation is also important in another sense: when you focus on validation, you inevitably end up doing somethign about semantics in your markup. Everyone benefits from this, especially you, the author, because Google and other search engines benefit from semantic markup.
Plus, broken HTML/XHTML may render in unpredictable ways with different browsers. XHTML-based blogs may not even render under certain circumstances (we’re talking about the famous application/xml+html content type here). I don’t suppose you’d want to harm your readers’ reading experiences, do you?
To help you in your thankless task of ensuring that your WordPress blog always remains valid HTML/XHTML, I’ve written a special plug-in for it: the WordPress XHTML validator. Download it today!
By the way, thanks for the reference link, thTeong!
Articles on this site are licensed under a
Creative Commons Attribution-Noncommercial-Share Alike 3.0 License
Commenters and other types of contributors retain their copyrights on their content.