How Apple Participates in W3C and WHATWG for Safari

This article provides an overview of how Apple, primarily through its WebKit engineering team, actively shapes the modern web by participating in the World Wide Web Consortium (W3C) and the Web Hypertext Application Technology Working Group (WHATWG). It covers Apple's leadership roles within these organizations, the step-by-step process its engineers use to propose new web technologies, and the strict criteria—such as privacy and energy efficiency—that Apple applies when reviewing third-party specifications before implementing them into the Safari web browser.

Leadership and Governance

Apple does not just contribute code; it holds foundational leadership positions in both major standards bodies.

  • WHATWG Steering Group: Apple is a founding member of the WHATWG and holds a permanent seat on its Steering Group alongside Google, Mozilla, and Microsoft. This gives Apple direct oversight over the "Living Standards" of HTML and the DOM (Document Object Model).
  • W3C Working Groups: Apple is a major financial and technical contributor to the W3C. Apple engineers co-chair numerous W3C working groups, including those for CSS, WebApps, Privacy, and Accessibility. Apple representatives also frequently serve on the W3C Advisory Board and the Technical Architecture Group (TAG).

How Apple Proposes New Specifications

When Apple wants to introduce a new capability to the web and implement it in Safari, it follows a structured incubation and standardization process.

  1. Identifying the Need: Proposals usually originate from limitations developers face on iOS and macOS, or from hardware capabilities Apple wants to expose safely to the web (such as 3D graphics or biometric authentication).
  2. Incubation: Apple engineers draft an explainer document detailing the problem and proposed solution. They typically introduce this in a W3C Community Group, such as the Web Incubator Community Group (WICG), to gather initial feedback from other browser vendors.
  3. Drafting the Specification: If the idea gains traction, Apple engineers act as specification editors. For HTML and DOM features, they submit pull requests directly to the relevant WHATWG GitHub repositories. For features like CSS, WebGPU, or WebAuthn, they work within the specific W3C Working Group to transition the idea into an official Working Draft.
  4. Prototyping in WebKit: Simultaneously, Apple builds an experimental implementation of the feature in WebKit (Safari’s underlying engine). Developers can test these proposals in Safari Technology Preview by toggling feature flags, allowing Apple to gather real-world data to refine the specification.

How Apple Reviews Specifications

Because Google (via the Blink engine) proposes a massive volume of new web APIs, a large part of Apple’s standards work involves reviewing, modifying, or blocking external proposals.

The WebKit Standards Positions Process Apple manages its review process publicly on GitHub through the WebKit Standards Positions repository. When another browser vendor or developer group proposes a new specification at the W3C or WHATWG, they file an issue in this repository asking for Apple’s stance. WebKit engineers discuss the proposal and assign a formal label, such as "Support" or "Oppose."

In both the W3C and WHATWG, true standardization requires multi-engine support. If Apple opposes a specification and refuses to implement it in WebKit, the proposal often stalls, preventing it from becoming an official web standard.

Apple's Review Criteria When reviewing a specification in W3C or WHATWG meetings, Apple evaluates the proposal against four strict criteria:

  • User Privacy: This is Apple's primary filter. Apple routinely rejects or demands rewrites of specifications that could be used for covert user tracking or "fingerprinting" (identifying a user based on their device configurations).
  • Security: Apple reviews how a proposed API interacts with the underlying operating system, ensuring it does not bypass sandboxing or expose users to malware.
  • Power and Performance: Because Safari runs predominantly on battery-powered devices (iPhones, iPads, and MacBooks), Apple pushes back against specifications that require excessive CPU usage or drain battery life.
  • Accessibility: Apple insists that new web standards—especially UI components and media features—have built-in support for screen readers like VoiceOver and other assistive technologies.

Achieving Interoperability

Once a specification passes Apple's review and reaches consensus in the W3C or WHATWG, Apple collaborates on the Web Platform Tests (WPT) project. Engineers write shared automated tests to ensure that Safari's implementation of the specification behaves identically to Chrome’s and Firefox’s. Furthermore, Apple participates in the annual "Interop" benchmark project, working directly with rival browser makers to fix bugs in existing W3C and WHATWG specifications to ensure a consistent experience for web developers.