Web Standards Project

The Web Standards Project, commonly abbreviated as WaSP, was an international coalition of professional web designers and developers established in 1998 to improve support for common web standards. Its central concern was the fragmented state of web browsers and authoring tools, particularly the inconsistent implementation of HTML, XHTML, CSS, the Document Object Model, and ECMAScript. The group argued that standards compliance would make websites less expensive and complicated to build and maintain, while also improving accessibility, interoperability, search visibility, and long-term resilience. WaSP emerged during a period in which browser vendors frequently implemented competing extensions or incomplete versions of web specifications. Developers consequently had to create separate versions of sites for different browsers, and users could encounter content that worked only in a particular software environment. The coalition sought to persuade browser manufacturers, software vendors, educational institutions, and web professionals to implement and teach standards recommended by the World Wide Web Consortium and related standards organizations. Its advocacy was directed especially at the browser market, where Microsoft Internet Explorer, Netscape, and Opera were among the most significant participants. The project credited its early campaign with helping persuade major browser makers to improve support for HTML 4.01, XHTML 1.0, CSS1, and ECMAScript by the early 2000s. More consistent implementation reduced the need for browser-specific development and helped establish conditions for semantic markup, progressive enhancement, accessible interfaces, and the broader evolution of the open Web. WaSP was not a commercial software vendor. It operated as an advocacy, education, and professional-coordination project whose outputs included public guidance, testing initiatives, task forces, articles, community activities, and engagement with companies responsible for browsers and authoring tools. The coalition relaunched in June 2002 with new participants, a redesigned website, and a mission that placed greater emphasis on education and standards compliance in authoring tools as well as browsers. Its task forces addressed Adobe products, higher-education teaching and public websites, Microsoft Internet Explorer and web-platform tools, accessibility, international advocacy, community events, and interoperable client-side scripting. The group also supported or publicized browser tests such as Acid1, Acid2, Acid3, and a mobile-browser compatibility test, which made standards and interoperability problems more visible to developers and vendors. One of its best-known public initiatives was Browse Happy, launched in 2004 as a campaign encouraging users to move away from older Internet Explorer releases toward alternative browsers. The site used security arguments and user testimonials to promote Mozilla Firefox, Opera, Safari, and later Google Chrome. WaSP concluded in 2005 that an explicitly anti-Internet Explorer campaign no longer fit its mission and transferred Browse Happy to Matt Mullenweg; it subsequently continued under WordPress.com stewardship with later community collaboration. The Web Standards Project announced its dissolution on March 1, 2013. Its closure reflected the changed environment in which browser support for core standards had improved and standards advocacy had become distributed across many organizations and communities. Although WaSP no longer operates, its vocabulary and methods—standards-based development, semantic markup, progressive enhancement, graceful degradation, accessibility, and cross-browser testing—remain influential in the history of professional web development.

The Web Standards Project began in August 1998 as a grassroots coalition formed by George Olsen, Glenn Davis, and Jeffrey Zeldman. Its founding objective was to improve the quality and consistency of web clients by persuading browser companies to implement established standards rather than proprietary or incomplete alternatives. At the time, incompatible browser behavior imposed substantial costs on web authors and threatened to divide the Web into collections of sites usable only with particular browsers. The coalition focused on standards associated with the W3C and related bodies, including HTML, XHTML, CSS, the DOM, and ECMAScript. Its work combined public advocacy, technical explanation, industry engagement, and community coordination. WaSP communicated with browser vendors, authoring-tool makers, educators, accessibility advocates, and web professionals. It maintained that common standards could reduce development and maintenance costs while supporting semantic content, assistive technologies, search engines, mobile access, and future reuse of web documents. By 2001, WaSP stated that browser makers including Microsoft, Netscape, and Opera had made substantial progress toward accurate support for HTML 4.01, XHTML 1.0, CSS1, and ECMAScript. The project treated this progress as a major step toward preventing browser fragmentation. Its influence was also expressed through practical testing. Acid1 tested aspects of HTML 4 and CSS1; Acid2 examined conformance involving CSS; and Acid3 expanded attention to CSS 2.1, DOM behavior, and ECMAScript. A separate mobile-browser compatibility effort addressed rendering problems on mobile devices. WaSP relaunched in June 2002 with a redesigned online presence, new participants, and a revised emphasis on education and authoring tools. Its task forces divided the work into specialized areas. The Adobe Task Force, formerly known as the Dreamweaver Task Force, addressed standards compliance in Adobe products. The Education Task Force worked with higher-education institutions on teaching standards and producing standards-compliant public websites. The Microsoft Task Force engaged with the Internet Explorer and web-platform tools teams. Other groups addressed accessibility, international liaison, community events, and interoperable DOM scripting. The DOM Scripting Task Force promoted standards-based JavaScript, progressive enhancement, graceful degradation, and accessible interaction patterns. The organization also supported public-facing campaigns. Browse Happy, created in August 2004, encouraged people to replace older Internet Explorer installations with alternative browsers. It used security concerns and testimonials from users who had changed browsers, initially highlighting Mozilla Firefox, Opera, and Safari and later including Google Chrome. In June 2005, WaSP transferred the project to Matt Mullenweg because it considered an anti-Internet Explorer campaign inconsistent with its broader mission. Browse Happy later continued through WordPress.com and community collaboration. Leadership changed over time. George Olsen led from 1998 to 1999, followed by Jeffrey Zeldman from 1999 to 2002 and Steven Champeon from 2002 to 2004. Molly Holzschlag led from 2004 to 2006. Kimberly Blessing and Drew McLellan jointly led from 2006 to 2008. Derek Featherstone, Aaron Gustafson, and Glenda Sims jointly led from 2008 until dissolution. The project announced its closure on March 1, 2013. Its end came after browser support for core standards had improved and standards work had become distributed among browser vendors, standards organizations, accessibility communities, and developer groups. WaSP's legacy lies less in a commercial product than in helping normalize interoperable, semantic, accessible, and standards-oriented web development.

• 2013

  Project dissolved

  [1]Web Standards Projecten.wikipedia.org

  The Web Standards Project announced its dissolution on March 1, ending its formal organizational activity.

• 2005

  Browse Happy transferred

  [1]Web Standards Projecten.wikipedia.org

  WaSP handed Browse Happy to Matt Mullenweg after determining that its anti-Internet Explorer framing did not fit the project's mission.

• 2004

  Browse Happy introduced

  [1]Web Standards Projecten.wikipedia.org

  WaSP launched Browse Happy, a public campaign encouraging users to move away from older Internet Explorer versions.

• 2002

  Organizational relaunch

  [1]Web Standards Projecten.wikipedia.org

  The project relaunched with new members, a redesigned website, and an expanded mission covering developer education and authoring tools.

• 2001

  Major browser standards progress

  [1]Web Standards Projecten.wikipedia.org

  WaSP reported that leading browser makers had substantially improved support for HTML 4.01, XHTML 1.0, CSS1, and ECMAScript.

• 1998

  Web Standards Project founded

  [1]Web Standards Projecten.wikipedia.org

  George Olsen, Glenn Davis, and Jeffrey Zeldman established WaSP as a grassroots coalition advocating stronger standards support in web browsers.

A noncommercial standards-advocacy coalition focused on making the Web more interoperable, accessible, economical to develop for, and durable across browsers and devices.

• Browser compatibility test

  Acid1

  A browser and rendering-engine test used to expose implementation problems involving HTML 4 and CSS1. It provided a compact, visible way for developers and vendors to compare browser behavior against foundational web specifications.

• Browser compatibility test

  Acid2

  A successor test designed to reveal browser inconsistencies involving CSS and related standards behavior. Its recognizable visual result made standards failures easy to demonstrate to both technical and general audiences.

• Browser compatibility test

  Acid3

  A broader compatibility test covering areas including CSS 2.1, DOM interfaces, and ECMAScript. It helped make differences in scripting and rendering support measurable during a period of rapid browser development.

• Mobile browser compatibility test

  Web Compatibility Test for Mobile Browsers

  A testing initiative focused on rendering and compatibility issues affecting mobile browsers and other constrained web clients. It extended the project's standards concerns beyond desktop browser implementations.

• Browser-awareness campaign · 2004

  Browse Happy

  A public website and campaign that encouraged users to upgrade from older Internet Explorer versions and consider alternative browsers. It combined security messaging with testimonials from people who had changed browsers; ownership and maintenance later moved outside WaSP.

• 2004Browse Happy

  International web users

  Browse Happy urged users to upgrade older Internet Explorer installations and consider alternative browsers, using security concerns and user testimonials.

  Outcome. WaSP transferred the initiative to Matt Mullenweg in 2005; it later continued under WordPress.com and community stewardship.

  Source
• 1998Browser standards advocacy

  International web-development industry

  WaSP campaigned for browser vendors to implement shared web standards accurately and consistently, seeking to prevent incompatible browser-specific versions of the Web.

  Outcome. The project reported major progress by 2001 in support for core HTML, XHTML, CSS, and ECMAScript specifications.

  Source

• 2013

  Dissolve the projectStrategy

  Background

  The browser and web-development environment had changed substantially since WaSP's founding, with standards support and standards advocacy distributed across a broader ecosystem.

  Action taken

  WaSP announced its dissolution on March 1, 2013.

  Aftermath

  The organization ceased formal activity while its practices and advocacy themes continued through standards bodies, accessibility groups, browser projects, and developer communities.

  Source

• 2005

  Transfer Browse HappyStrategy

  Background

  WaSP determined that the campaign's explicit anti-Internet Explorer framing did not align with the project's broader standards mission.

  Action taken

  The project handed Browse Happy to Matt Mullenweg rather than continuing to operate it directly.

  Aftermath

  The site continued outside WaSP, later being maintained through WordPress.com with additional community collaboration.

  Source

• 2002

  Expand the mission through a relaunchStrategy

  Background

  After early browser advocacy produced substantial standards progress, the project reassessed its focus.

  Action taken

  WaSP relaunched with new members, a redesigned website, and a stronger emphasis on education and standards compliance in authoring tools as well as browsers.

  Aftermath

  The relaunch supported a wider task-force structure covering education, accessibility, vendors, international outreach, and DOM scripting.

  Source

1. 1Web Standards Projecten.wikipedia.org
2. 2Web Standards Project official websitewebstandards.org