Organizations

World Wide Web Consortium (W3C)

Summary

The World Wide Web Consortium (W3C) is the international standards body behind many of the technical standards websites are built on, including CSS, XML and the Web Content Accessibility Guidelines (WCAG). Tim Berners-Lee founded it on October 1, 1994, at MIT in collaboration with CERN. After 28 years run through host institutions, it became an independent public-interest nonprofit in January 2023.

What the W3C is

The World Wide Web Consortium (W3C) is an international membership organization that writes technical standards for the web. Its stated mission is to make the web work for everyone.1

W3C calls its finished standards W3C Recommendations. They are written by its Working Groups, following a rulebook called the Process Document.2

The standards are free to use. W3C states that its standards may be used by anyone at no cost, that the work is done in the open, and that decisions are made by consensus.1

Its About page, with figures last updated on January 9, 2026, lists 335 Members, a staff of 45 to 55 people and more than 14,700 developers taking part in standards work.1 The staff page describes the W3C Team as 50 people as of October 22, 2026.3

Membership has varied over time. CERN recorded more than 400 W3C member organizations in September 2018,4 and W3C cited “more than 400 Member organizations” again in January 2023.5 Revenue comes mainly from membership dues, with some grants.1

Founding and the host years (1994 to 2022)

The web began at CERN, where Tim Berners-Lee proposed it in 1989.6 By 1994, companies were investing more in the web, and W3C’s own history says the decision to form a consortium came at their urging.6

W3C’s timeline records that in September 1993 David Gifford suggested contacting Michael Dertouzos of MIT’s Laboratory for Computer Science as a possible host for a consortium.7

In July 1994 an agreement between MIT and CERN to start the organization was announced. The World Wide Web Consortium was founded on October 1, 1994, and held its first Consortium meeting at MIT in Cambridge, Massachusetts, on December 14, 1994.7

Berners-Lee founded W3C at MIT’s Laboratory for Computer Science (MIT/LCS), in collaboration with CERN and with support from DARPA (the US Defense Advanced Research Projects Agency) and the European Commission.6

CERN soon stepped back. On December 16, 1994, it decided not to continue web development and, with the European Commission and INRIA, transferred the WebCore project, which it had proposed with the European Commission, to INRIA.7 CERN’s account says it judged further web development to be outside its primary mission.4

For its first 28 years W3C was not a legal entity of its own. Host institutions managed the contracts with Members and employed the staff, an arrangement W3C now calls the hosted model.61

Host institutionRoleFrom
MIT Laboratory for Computer ScienceFounding host1994
INRIAFirst European hostApril 1995
Keio University (Shonan Fujisawa Campus)Asian host1996
ERCIMEuropean host, taking over from INRIA2003
Beihang UniversityFourth host2013

Source for the table: W3C’s history page.6

How a W3C standard is made

Work is organized into groups. Working Groups produce the deliverables listed in their charters, while Community Groups and Business Groups follow a separate process document.2 W3C describes its processes as resting on the consensus of the Membership, the staff (called the Team) and the public.2

Each specification moves through named stages, which tell readers how settled it is.8

  • Working Draft: a work in progress published for review and not yet endorsed by W3C.
  • Candidate Recommendation Snapshot: a version that has the group’s consensus and has had public review, published to gather final feedback from implementers, the people building it into browsers and tools.
  • W3C Recommendation: a specification endorsed after extensive consensus-building, which may be cited as a W3C standard.

Old standards are relabeled rather than deleted. A Recommendation replaced by a newer version becomes Superseded, one without enough market relevance becomes Obsolete, and one W3C no longer endorses becomes Rescinded.8 HTML 4.01, for example, has been a Superseded Recommendation since March 27, 2018.9

Not everything W3C publishes is a standard. A Group Note is a stable reference for material that is not meant to be a formal standard, and it must not be cited as one.8

Two elected bodies sit above the groups. The Technical Architecture Group (TAG) has as its mission “stewardship of the Web architecture.” It has 12 seats: Berners-Lee as a life member, three people appointed by the W3C staff and eight elected by the Advisory Committee, which represents the Members.2

The Advisory Board has nine to eleven elected participants2 and guides changes to the Process Document.1 The current Process Document is dated August 18, 2025.2

Patents are handled by the W3C Patent Policy. Its goal is that W3C specifications can be implemented on a royalty-free basis, meaning no one has to pay patent fees to build them.10 The version dated February 5, 2004, was endorsed by the W3C Director as the W3C Patent Policy,11 and WCAG 2.0 was among the standards produced under it.12 The current version is dated May 15, 2025.10

Standards that shaped websites

W3C’s standards cover how pages are displayed, how they work across devices and the architecture of the web. Technologies it names as examples include HTML, CSS, SVG, WOFF, WebRTC and XML.13

StandardWhat it isRecommendation
CSS level 1Style sheet language by Håkon Wium Lie and Bert Bos14December 17, 1996
HTML 3.2HTML written by Dave Raggett with vendors including IBM, Microsoft, Netscape and Sun Microsystems15January 14, 1997
XML 1.0General markup format edited by Tim Bray, Jean Paoli and C. M. Sperberg-McQueen16February 10, 1998
HTML 4.01Revised HTML 4, superseded in March 20189December 24, 1999
WCAG 2.0Web Content Accessibility Guidelines17December 11, 2008
HTML5Revision of HTML developed with the WHATWG18October 28, 2014
WCAG 2.2Current accessibility guidelines17October 5, 2023

Accessibility became a standing program on April 7, 1997, when W3C launched the Web Accessibility Initiative (WAI). The launch release said the program was endorsed by the White House and named IBM, Lotus Development Corporation, Microsoft, Riverland Holding and SoftQuad International as charter sponsors.19

WAI publishes the Web Content Accessibility Guidelines (WCAG). WCAG 2.2 is also an international standard, ISO/IEC 40500:2025, which W3C says is exactly the same as the October 2023 version.17

The HTML split and the WHATWG agreement

After HTML 4, the W3C membership decided to stop evolving HTML and to work on an XML-based successor, XHTML, instead.20

Browser makers pushed back. At a W3C workshop on web applications and compound documents in San Jose, California, on June 1 and 2, 2004,21 Mozilla and Opera proposed evolving HTML. The proposal was rejected because it conflicted with the direction W3C had already chosen.20

Individuals from Apple, the Mozilla Foundation and Opera Software then founded the WHATWG (Web Hypertext Application Technology Working Group), citing concern about W3C’s direction with XHTML and its lack of interest in HTML.22

W3C changed course. In 2006 it said it wanted to take part in HTML5 after all, and in 2007 it formed a working group to develop HTML5 together with the WHATWG.20 W3C published HTML5 as a Recommendation on October 28, 2014. Ian Hickson of Google is listed as the WHATWG editor, alongside six W3C editors.18

The groups still disagreed about publishing. W3C wanted a finished HTML5, while the WHATWG wanted to keep a continuously maintained Living Standard.20

A memorandum of understanding settled the matter from May 28, 2019. It states that HTML and DOM “shall be developed principally in the WHATWG,” and W3C dropped its plans for its own HTML 5.3 and DOM 4.1.23 The DOM (Document Object Model) is the in-memory model of a page that scripts use to read and change it.24

In a W3C blog post the same day, Jeff Jaffe wrote that two distinct HTML and DOM specifications both claiming to be normative was generally harmful to the community, and that the two organizations had been exploring ways to work together since December 2017.25

Under the agreement W3C endorses WHATWG snapshots, called Review Drafts, as W3C Recommendations, and expects to do so at least once every 12 months.23 It endorsed its first DOM snapshot on November 3, 2020, and its first HTML snapshot on January 28, 2021.26

An independent nonprofit since 2023

On January 31, 2023, W3C announced that it had begun the year by forming a public-interest nonprofit organization incorporated in the United States.5 That made W3C its own legal entity and ended the 28-year hosted model.1

A Board of Directors with a majority drawn from W3C Members guides the organization, and Berners-Lee keeps a permanent seat on it.5 W3C now lists him as Emeritus Director and an Honorary Member of the Board.1

On October 2, 2023, W3C announced Seth Dobbs as its new CEO, starting November 13, 2023. Ralph Swick was interim CEO at the time.27

On May 28, 2026, W3C announced that Dobbs was stepping down and that the Board had named Dominique Hazaël-Massieux interim CEO with immediate effect.28 The staff page still lists him as interim CEO as of October 22, 2026.3

W3C says its community has developed several hundred open standards.1 At the 2023 relaunch it put the figure at nearly five hundred.5

Timeline

  1. Seth Dobbs steps down; Dominique Hazaël-Massieux named interim CEO28
  2. WCAG 2.2 published17
  3. W3C announces Seth Dobbs as CEO, starting November 13, 202327
  4. W3C announces it has become a public-interest nonprofit5
  5. W3C endorses its first WHATWG HTML snapshot as a Recommendation26
  6. Memorandum of understanding moves HTML and DOM development to the WHATWG23
  7. HTML5 becomes a W3C Recommendation18
  8. Beihang University announced as the fourth host6
  9. WCAG 2.0 published17
  10. W3C workshop in San Jose rejects the proposal to keep evolving HTML20
  11. Royalty-free W3C Patent Policy version endorsed11
  12. XML 1.0 becomes a W3C Recommendation16
  13. Web Accessibility Initiative launched19
  14. CSS level 1 becomes a W3C Recommendation14
  15. World Wide Web Consortium founded7

What it means for your website

Few site owners deal with the W3C directly, but its standards decide what “accessible” and “valid” mean for your pages, and anyone can use them at no cost.1

  • Accessibility is measured against WCAG. The US Department of Justice’s 2024 rule for state and local governments adopts WCAG 2.1 Level AA as the technical standard for their websites and mobile apps. After an April 2026 extension, the deadlines are April 26, 2027, for governments serving 50,000 or more people and April 26, 2028, for smaller ones.29 If you build for a public body, ask which WCAG level your templates target. Our guide to US website laws covers private businesses.
  • Start with a quick check. W3C’s Easy Checks walk through page titles, image text alternatives, headings, contrast, keyboard access and forms. W3C says they cover only a few issues and are not definitive.30 Our web accessibility glossary entry explains the terms.
  • Validate after big changes. The W3C Markup Validation Service checks a page by its address, by file upload or by pasted code.31 Errors that come from a theme or plugin are worth reporting to whoever maintains it.
  • Prefer standard formats. W3C’s patent policy aims for standards anyone can implement without royalties.10 Content stored as plain HTML and CSS is easier to move than content locked in one vendor’s format, so ask how much you can export before you commit. See how to choose a website builder.

See also

References

  1. About us. World Wide Web Consortium. 2026-01-09. accessed October 22, 2026.
  2. W3C Process Document (18 August 2025). World Wide Web Consortium. 2025-08-18. accessed October 22, 2026.
  3. W3C Team. World Wide Web Consortium. accessed October 22, 2026.
  4. A short history of the Web. CERN. accessed October 22, 2026.
  5. W3C re-launched as a public-interest non-profit organization (press release). World Wide Web Consortium. 2023-01-31. accessed October 22, 2026.
  6. W3C history. World Wide Web Consortium. accessed October 22, 2026.
  7. A Little History of the World Wide Web (created by Robert Cailliau, maintained by Dan Connolly). W3C. accessed October 22, 2026.
  8. Types of documents W3C publishes. World Wide Web Consortium. accessed October 22, 2026.
  9. HTML 4.01 Specification (W3C Recommendation). W3C. 1999-12-24. accessed October 22, 2026.
  10. W3C Patent Policy (15 May 2025 version). World Wide Web Consortium. 2025-05-15. accessed October 22, 2026.
  11. W3C Patent Policy (5 February 2004 version). World Wide Web Consortium. 2004-02-05. accessed October 22, 2026.
  12. Web Content Accessibility Guidelines (WCAG) 2.0 (W3C Recommendation). W3C. 2008-12-11. accessed October 22, 2026.
  13. Web standards. World Wide Web Consortium. accessed October 22, 2026.
  14. Cascading Style Sheets, level 1 (W3C Recommendation). W3C (Håkon Wium Lie, Bert Bos). 1996-12-17. accessed October 22, 2026.
  15. HTML 3.2 Reference Specification. W3C (Dave Raggett). 1997-01-14. accessed October 22, 2026.
  16. Extensible Markup Language (XML) 1.0 (W3C Recommendation). W3C (Tim Bray, Jean Paoli, C. M. Sperberg-McQueen). 1998-02-10. accessed October 22, 2026.
  17. WCAG 2 Overview. W3C Web Accessibility Initiative. 2026-09-17. accessed October 22, 2026.
  18. HTML5: A vocabulary and associated APIs for HTML and XHTML (W3C Recommendation). W3C. 2014-10-28. accessed October 22, 2026.
  19. World Wide Web Consortium (W3C) Launches International Web Accessibility Initiative (press release). World Wide Web Consortium. 1997-04-07. accessed October 22, 2026.
  20. HTML Living Standard, section 1: Introduction (History). WHATWG. 2026-10-20. accessed October 22, 2026.
  21. W3C Workshop on Web Applications and Compound Documents. W3C. 2004-06. accessed October 22, 2026.
  22. FAQ. WHATWG. accessed October 22, 2026.
  23. Memorandum of Understanding Between W3C and WHATWG. W3C and WHATWG. 2019-05-28. accessed October 22, 2026.
  24. Introduction to the DOM. MDN Web Docs (Mozilla). accessed October 22, 2026.
  25. W3C and WHATWG to work together to advance the open Web platform. W3C blog (Jeff Jaffe). 2019-05-28. accessed October 22, 2026.
  26. WHATWG Review Drafts of HTML and DOM endorsed as W3C Recommendations. W3C blog (Philippe le Hegaret). 2021-01-28. accessed October 22, 2026.
  27. World Wide Web Consortium (W3C) welcomes Seth Dobbs as new Chief Executive Officer (press release). World Wide Web Consortium. 2023-10-02. accessed October 22, 2026.
  28. W3C leadership transition (press release). World Wide Web Consortium. 2026-05-28. accessed October 22, 2026.
  29. Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments. U.S. Department of Justice, Civil Rights Division (ADA.gov). accessed October 22, 2026.
  30. Easy Checks: A First Review of Web Accessibility. W3C Web Accessibility Initiative. accessed October 22, 2026.
  31. Markup Validation Service. W3C. accessed October 22, 2026.

Web Building Encyclopedia. First published October 22, 2026. Last reviewed October 22, 2026. Every fact on this page is linked to a source we opened. Spotted an error? Write to [email protected].