WCAG, HTML, and CSS: Maybe the Standards Need a Break
Post from June 15, 2007 (↻ December 12, 2016), filed under Web Development.
This and many other posts are also available as a pretty, well-behaved e-book: On Web Development.
These worries and respective criticism look legitimate and valid—there are problems with the Web Content Accessibility Guidelines (hopefully being addressed by the WCAG Working Group, alternatively addressed by the WCAG Samurai), there’s demand for an update to HTML (formerly addressed by the WHATWG, currently addressed by the new HTML Working Group, orchestrated by the W3C), and finally, there appears to be need for the sustained development of the CSS standard.
Let’s all try to contribute to the necessary improvements, yet we’ll probably benefit from a break soon after the release of WCAG 2.0, HTML 5, and CSS 3.
Why? By then (2010?), there will be need for a look backwards and a thorough revision of these standards, mainly meaning additional quality assurance (unfortunately, the W3C process doesn’t even allow to fix typos once a spec is stable) and, above all, time for implementors. For years we’ve all been in a hurry to update and extend standards that we don’t seem to notice that our complaints about missing or false implementations might be caused by exactly that rush. (Current problems and criticism might make this sound ironic, but it’s not.)
Sure, there’s a particularly strong need to fix certain spec parts, but we’ll benefit from a time where we explicitly want just two things: QA and rest. A “spec freeze” would also allow us to focus more on learning and teaching standards.
Someday, let’s take a break.
I’m Jens Oliver Meiert, and I’m a web developer and author. I love trying things, including in the fields of philosophy, art, and adventure. Here on meiert.com I share some of my thoughts and experiences.
If you have any suggestions or questions about what I write, leave a comment or a message.
You said: “(unfortunately, the W3C process doesn’t even allow to fix typos once a spec is stable …)”
That is plain wrong. It is called erratas and it is perfectly defined. Looked on the HTML 4.01 spec.
I have replied to Molly on the QA Weblog: Fixing the Web together.
Hi Jens. Note also that errata can be brought into the specification via the PER part of the process. For example, the XML spec is currently in its 4th edition. HTH.
Have a look at the most popular posts, possibly including:
- Requirements for Website Prototypes (and Design Systems)
- Load Time, the UX Factor: Facts and Measures
Perhaps my most relevant book: CSS Optimization Basics (2018). Writing CSS is a craft. As craftspeople we strive to write high quality CSS. In CSS Optimization Basics I lay out the, at least some of the most important aspects of such CSS.
Looking for a way to comment? Comments have been disabled, unfortunately.