Working together for standards The Web Standards Project

Buzz Archives: DOM Scripting TF

The W3C Web API Working Group

W3C announces the Web API group to develop specifications that enable improved client-side application development on the Web.

By Jeremy Keith | November 23rd, 2005

How to Create User-Friendly Pop-Under Ads

A pop-under ad that avoids the problem of blocking access to content.

By Christian Heilmann | November 7th, 2005

moo.fx Makes it Easy to Add Transition Effects

A small JavaScript library to add powerpoint or flash-like transition effects to web sites: moo.fx.

By Christian Heilmann | October 31st, 2005

Debugging JavaScript with jsTrace

Aaron Gustafson gives us a very handy tool for debugging scripts: jsTrace.

By Jeremy Keith | October 27th, 2005

Spreading the Word

With the release of his new DOM Scripting book, I’ve been on a little talking spree around the Web.

By Jeremy Keith | October 24th, 2005

… And the Winner Is …

We have a winner for the addEvent() recoding contest!

By Peter-Paul Koch | October 18th, 2005

addEvent() Recoding Contest

Here's one for lovers of the language of the rhinos:- over on the WaSP DOM Scripting Task Force blog, PPK announces the launch of a JavaScript addEvent() recoding contest. Write your own version of addEvent() and removeEvent(), submit it by adding a comment to this page, and win JavaScript fame. Entries will ...

By Drew McLellan | September 10th, 2005

addEvent() Recoding Contest

Launching an addEvent() recoding contest.

By Peter-Paul Koch | September 8th, 2005

Unobtrusive Behaviour Layer

Steve Chipman presentation (audio and slides) covers all of the important aspects of modern-day JavaScript in a clear informative way.

By Jeremy Keith | September 3rd, 2005

A Heavy Onload to Carry

Solving the window.onload problem, Allesandro runs through the pros and cons of possible solutions.

By Jeremy Keith | August 29th, 2005

IBM Donates DOM Scripting Accessibility Code to Firefox

IBM’s donation will help developers write accessible DOM Scripting applications, and make Firefox browser more accessible all-round.

By Chris Kaminski | August 16th, 2005

Sortable Lists

Nifty demo of drag’n'drop sortable lists using JavaScript and CSS.

By Chris Kaminski | July 30th, 2005

JavaScript and Screenreaders

What do you get when you cross JavaScript with a screen reader? James Edwards, Bob Easton, Mike Stenhouse and Derek Featherstone find out.

By Derek Featherstone | July 28th, 2005

Best Practices

A nice round-up of best practices for using JavaScript.

By Jeremy Keith | July 27th, 2005

Collaborative bug squashing

Lucian Slatineanu is putting together a DOM script to replace the default form widgets supplied by the browser with other, more customisable elements. He calls the script Niceforms.

By Jeremy Keith | July 25th, 2005

Accessible Event Pairs

In order to keep our pages accessible to non-mouse users, we must use non-mouse events like focus or keydown in addition to mouse events like mouseover and click. On I created the new Event pairs page to study this problem.

By Peter-Paul Koch | July 21st, 2005

Unobtrusive Flash Objects

Bobby van der Sluis just published a new article: Unobtrusive Flash Objects (or UFO). His script allows you to specify a placeholder DIV for a Flash object with a message meant for noflash browsers. The script then silently checks if the user has the proper Flash version, and if so replaces ...

By Peter-Paul Koch | July 20th, 2005

Image Previews with DOM and CSS (and a dash of PHP)

Sometimes it might be a good idea to give visitors an insight of what is lurking behind a link. Normally this is achieved via a thumbnail, but what about inline links?

By Christian Heilmann | July 20th, 2005

Mehr Presse

Jo Bager has written a short-but-oh-so-sweet blurb on our humble Task force for Heise Online. Vielen Dank, Herr Bager!

By Chris Kaminski | July 19th, 2005

Accessible Alternative vs. Direct Accessibility

The progressive enhancement approach, also called the ‘accessible alternative’ approach, is indeed the most common and best-understood. It’s not the whole shooting match, though. There’s a second approach to making ECMAScript-enhanced pages accessible: direct accessibility.

By Chris Kaminski | July 19th, 2005

Presentation Slides with DOM and CSS

Eric Meyer’s S5 standards based presentation slides system is used quite a lot by webstandardismos for their presentations. My personal challenge was to come up with something that is as cool as Eric’s system, but much easier to use and more lightweight when it comes to creating your own slides.

By Christian Heilmann | July 18th, 2005

JavaScript and WCAG2.0 progress

The Web Content Accessibility Guidelines (or WCAG) is a series of pointers and tips on making web content accessible to people with disabilities (with a useful side-effect of making the content more accessible to practically all devices). JavaScript has a bigger profile within the current WCAG2.0 work.

By Mike Davies | July 18th, 2005

The DOM Scripting Task Force

In an effort to boost the quality of scripting on the world wide web, the Web Standards Project today announced the formation of the DOM Scripting Task Force.

By Jeremy Keith | July 18th, 2005


Here it is: the website of the newly formed DOM Scripting Task Force, set up under the auspices of the Web Standards Project.

By Jeremy Keith | July 18th, 2005

Practical Ajax

Cameron Adams, the antipodeon man in blue, has written a nice hands-on guide to using Ajax. The article, over on SitePoint, is called Usable Interactivity with Remote Scripting.

By Jeremy Keith | May 10th, 2005

The Web Standards Project is a grassroots coalition fighting for standards which ensure simple, affordable access to web technologies for all.

Recent Buzz

Our Work Here is Done

By Aaron Gustafson | March 1st, 2013

Thanks to the hard work of countless WaSP members and supporters (like you), Tim Berners-Lee’s vision of the web as an open, accessible, and universal community is largely the reality.

When The Web Standards Project (WaSP) formed in 1998, the web was the battleground in an ever-escalating war between two browser makers—Netscape and Microsoft—who were each taking turns “advancing” HTML to the point of collapse. You see, in an effort to one-up each other, the two browsers introduced new elements and new ways of manipulating web documents; this escalated to the point where their respective 4.0 versions were largely incompatible.

Realizing that this fragmentation would inevitably drive up the cost of building websites and ran the risk of denying users access to content and services they needed, Glenn Davis, George Olsen, and Jeffrey Zeldman co-founded WaSP and rallied an amazing group of web designers and developers to help them push back. The WaSP’s primary goal was getting browser makers to support the standards set forth by the World Wide Web Consortium (W3C).

In 2001, with the browser wars largely over, WaSP began to shift its focus. While some members continued to work with browser vendors on improving their standards support, others began working closely with software makers like Macromedia to improve the quality of code being authored in tools such as Dreamweaver. And others began the hard slog of educating web designers and developers about the importance of using web standards, culminating in the creation of WaSP InterAct, a web curriculum framework which is now overseen by the W3C.

Thanks to the hard work of countless WaSP members and supporters (like you), Tim Berners-Lee’s vision of the web as an open, accessible, and universal community is largely the reality. While there is still work to be done, the sting of the WaSP is no longer necessary. And so it is time for us to close down The Web Standards Project.

Many (if not all) of us are continuing to work in the world of web standards, but our work is now largely outside the umbrella of WaSP. If you are interested in continuing to work on web standards-related projects along with us, we humbly suggest you follow these projects:

  • A List Apart – The magazine “for people who make websites” is run by WaSP founder Jeffrey Zeldman and is a consistent source of forward-thinking articles and tutorials.
  • HTML5 Doctor – A solid resource and discussion forum on all things HTML5, brought to you by Bruce Lawson and his team.
  • W3C Community Groups – If you have a passion for a specific web technology, you can help make it better by participating in one (or more) community groups. In particular, you might be interested in one of these: Core Mobile Web Platform, Responsive Images, Web Education, and Web Media Text Tracks.
  • – A fantastic web standards resource, providing up-to-date documentation, Q&As, tutorials & more. Chris Mills, Doug Schepers, and a number of other standards advocates are involved in this project.
  • Web Standards Sherpa – An educational resource founded by WaSP which continues to operate under the leadership of Chris Casciano, Virginia DeBolt, Aaron Gustafson, and Emily Lewis.
  • Web Standards + Small Business – An outreach project started by WaSP that educates small businesses about why they should care about web standards. This project is overseen by Aaron Gustafson.

The job’s not over, but instead of being the work of a small activist group, it’s a job for tens of thousands of developers who care about ensuring that the web remains a free, open, interoperable, and accessible competitor to native apps and closed eco-systems. It’s your job now, and we look forward to working with you, and wish you much success.

Nota bene: In the near future, we will be making a permanent, static archive of and some of our other resources like WaSP Interact to preserve them as a resource and to provide a record of our 15-year mission to improve the web.
Bruce Lawson and Steph Troeth contributed to this post.

Filed in WaSP Announcement | Comments (89)

More Buzz articles

Title Author
Call for action on Vendor Prefixes Rachel Andrew
An End to Aging IE Installs Aaron Gustafson
Beyond the Blue Beanie? Stephanie (Sullivan) Rewis
The Sherpas are Here Aaron Gustafson

All of the entries posted in WaSP Buzz express the opinions of their individual authors. They do not necessarily reflect the plans or positions of the Web Standards Project as a group.

This site is valid XHTML 1.0 Strict, CSS | Get Buzz via RSS or Atom | Colophon | Legal