{
  "id": "whatwg",
  "title": "Web Hypertext Application Technology Working Group",
  "lang": "en",
  "source_lang": "en",
  "summary": "The Web Hypertext Application Technology Working Group (WHATWG) develops and maintains living standards for HTML and other foundational web technologies.",
  "category": "computer-science",
  "subcategory": "software",
  "type": "organization",
  "aliases": [
    "WHATWG"
  ],
  "generated_at": "2026-11-04",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/whatwg/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/whatwg/",
      "json": "https://aiwiki.page/zh/whatwg.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "The Web Hypertext Application Technology Working Group (WHATWG) is a standards community that develops and maintains technical specifications for the World Wide Web, particularly HTML and the interfaces and processing rules used by web browsers. Founded in 2004 by individuals associated with Apple, Mozilla, and Opera, it emphasizes compatibility with existing web content, implementable specifications, and continuous development. Its publications are generally maintained as living standards: documents that are updated as requirements, implementation experience, and agreed technical solutions evolve."
    },
    {
      "heading": "Origins and history",
      "text": "WHATWG emerged during a period of disagreement about the future of web markup and applications. In the early 2000s, the World Wide Web Consortium (W3C) devoted substantial attention to XHTML, which reformulated HTML using XML, and to XHTML 2.0, a proposed successor that did not prioritize compatibility with existing HTML in the same way as browser implementers sought.\n\nRepresentatives of browser developers advocated extending the existing web platform to support richer applications while preserving compatibility with deployed pages. WHATWG was established in June 2004 following disagreements about this direction at a W3C workshop on web applications and compound documents.\n\nIts early projects included Web Forms 2.0, which extended HTML forms, and Web Applications 1.0, which developed a broader application platform around HTML. Work from these efforts contributed to what became known as HTML5.\n\nIn 2007, the W3C established a new HTML Working Group and adopted WHATWG’s work as the starting point for its renewed HTML development. For several years, the two organizations published related specifications through different processes. The W3C produced numbered recommendations, including HTML5 in 2014, while WHATWG increasingly emphasized continuous maintenance rather than successive completed editions.\n\nA governance structure introduced in 2017 established a Steering Group with representatives from Apple, Google, Microsoft, and Mozilla. In 2019, WHATWG and the W3C announced an agreement to collaborate on a single development stream for HTML and the Document Object Model (DOM), with WHATWG maintaining the living standards. The agreement reduced the risk of conflicting authoritative specifications for these technologies."
    },
    {
      "heading": "Living standards",
      "text": "A living standard is a specification maintained through ongoing changes rather than treated primarily as a sequence of fixed releases. Updates can clarify ambiguous requirements, correct errors, document necessary compatibility behavior, or introduce new capabilities.\n\nThis model responds to several characteristics of the web:\n\n- Long-lived content: older pages are expected to remain usable in newer browsers.\n- Continuous browser development: implementations evolve on independent release schedules.\n- Interdependent technologies: changes to document processing can affect scripting, networking, security, and accessibility.\n- Implementation feedback: differences between browsers often expose gaps that require more precise specification.\n\nLiving standards nevertheless have recorded histories. Their development can be traced through version control, issues, and individual changes. Continuous maintenance does not mean that every proposal is accepted immediately or that every browser implements a change as soon as it is published.\n\nThe expression “HTML5” remains common as a historical and informal label, but WHATWG’s actively maintained specification is named the HTML Living Standard, not a periodically numbered successor such as HTML6."
    },
    {
      "heading": "Principal specifications",
      "text": "WHATWG’s work extends beyond markup syntax. Its specifications define interacting components of the web platform.\n\nHTML\n\nThe HTML Living Standard specifies elements, attributes, document structure, forms, and substantial parts of the browser application environment. It also defines detailed parsing rules, including recovery from malformed markup.\n\nThese rules are important because browsers must handle the web as it exists, not only documents that satisfy authoring requirements. A page can violate HTML’s authoring rules while still having precisely specified browser processing behavior.\n\nHTML also defines aspects of navigation, document loading, communication between documents, and the event loop that coordinates tasks and script execution. It integrates with JavaScript but does not define the JavaScript language itself.\n\nDOM\n\nThe DOM Standard defines foundational structures and operations for representing documents as trees and manipulating them through application programming interfaces. It includes nodes, events, and mechanisms for observing document changes.\n\nHTML supplies many element-specific behaviors, while DOM provides common infrastructure used across document technologies.\n\nFetch and URL\n\nThe Fetch Standard defines infrastructure for fetching resources. Its scope is broader than the JavaScript fetch() function: it also supports resource loading initiated by other web features, including document navigation and the loading of images and scripts.\n\nThe URL Standard defines parsing, serialization, and related APIs for URLs. It specifies behavior needed for consistent handling across browsers, including inputs whose processing is not adequately captured by a simple idealized address grammar.\n\nOther infrastructure\n\nOther WHATWG specifications address character encodings, streams, storage, web messaging, and related browser facilities. The Encoding Standard is particularly concerned with consistent treatment of both modern and legacy encodings used by web content.\n\nWHATWG does not maintain every major web technology. For example, Cascading Style Sheets is developed primarily through the W3C, while HTTP is standardized through the Internet Engineering Task Force."
    },
    {
      "heading": "Organization and development process",
      "text": "WHATWG combines public technical participation with a governance structure involving major browser organizations. Its Steering Group oversees institutional matters and the organization’s working arrangements. Editors maintain individual standards and guide their technical development.\n\nDiscussion generally occurs through public issue trackers and proposed changes to specification repositories. Contributors can report errors, identify implementation discrepancies, propose features, or supply tests. Changes are assessed through technical discussion, compatibility considerations, implementation interest, and the requirements of the relevant standard.\n\nThe process is not simply a vote among all participants. Editors have substantial responsibility for maintaining coherent specifications, while implementers provide evidence about feasibility and deployment. WHATWG’s participation and intellectual-property arrangements also establish conditions for contributing to its standards.\n\nWeb Platform Tests, a shared cross-browser testing project, plays an important supporting role. Tests help determine whether different implementations follow the same requirements and can reveal ambiguities or errors in either a specification or browser code."
    },
    {
      "heading": "Design priorities and limitations",
      "text": "A central priority is interoperability: independently developed browsers should interpret the same content in sufficiently consistent ways. Achieving this often requires detailed algorithms rather than broad descriptions of intended behavior. It can also require standardizing legacy behavior that would not be chosen in a newly designed system.\n\nBackward compatibility therefore constrains simplification. Removing an awkward feature may break existing sites, while changing error recovery can alter the interpretation of large amounts of deployed content.\n\nSecurity, privacy, and accessibility also affect specification design. Browser features must account for interactions among documents, origins, permissions, user input, and assistive technologies. A specification alone, however, cannot ensure that an implementation is secure or that a website is accessible.\n\nWHATWG’s close relationship with browser implementers helps align standards with software that can be deployed. It also gives the organizations responsible for those implementations considerable practical influence: a feature generally cannot become interoperable without their engineering participation. Public contribution mechanisms allow wider input, but participation does not guarantee adoption of a proposal.\n\nFinally, specification status and implementation status are distinct. A published requirement may not yet be supported everywhere, and a browser may contain experimental behavior that has not become an agreed standard. Understanding a feature’s availability therefore requires distinguishing the normative specification from the behavior of particular browser versions."
    }
  ],
  "links": [
    "world-wide-web",
    "html",
    "web-browser",
    "world-wide-web-consortium",
    "version-control",
    "event-loop",
    "javascript",
    "application-programming-interface",
    "uniform-resource-locator",
    "character-encoding",
    "cascading-style-sheets",
    "hypertext-transfer-protocol",
    "internet-engineering-task-force",
    "interoperability",
    "data-privacy",
    "web-accessibility"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}