Summary

  • On 28 September 2026, W3C announced seven Consortium Member-elected directors for two-year terms beginning 30 September. They join three Partner-appointed directors; Tim Berners-Lee participates without a Board vote.
  • The election fills corporate fiduciary seats. W3C's own guidance says directors owe duties to W3C, oversee its finances and management, and do not manage its technical agenda.
  • Members retain the exclusive bylaw power to amend the W3C Process. A nominating organization's identity is not evidence that its nominee may carry an instructed standards vote into the Board.

A nomination is not a proxy

The election result names Koichi Moriyama, Chris Needham, Theresa O'Connor, Florian Rivoal, Avneesh Singh, Léonie Watson and Hongru (Judy) Zhu as the seven people elected by W3C Consortium Members. The public nomination page identifies members that put candidates forward and records affiliations and campaign statements. Those are useful origins for an election. They are not instructions that follow a successful candidate into every corporate decision.

This is the change in status that a list of names can obscure. Before the result, a candidate can seek support and explain priorities. Once seated, a director has fiduciary responsibility to World Wide Web Consortium, Inc. as a whole. W3C describes duties of care, loyalty and obedience, including placing the organization's interests before personal interests. An employer or nominator may have legitimate expertise and preferences. Neither becomes the director's legal principal for Board votes merely by appearing on the nomination page.

W3C says the seven elected directors join Dominique Hazaël-Massieux, Chunming Hu and Tatsuya Kurosaka, whom its current Partners appointed. Tim Berners-Lee participates as a non-voting Board member. The result dates the terms from 30 September 2026 through 30 September 2028. It reports winners, not individual vote totals, turnout, committee assignments or future decisions. No such missing detail is evidence of an improper election.

Two kinds of authority, one institution

The bylaws specify seven Consortium-elected seats, up to four Partner seats and two Board-elected seats within a seven-to-thirteen-director range. The announced seven-plus-three composition is therefore a current cohort, not the permanent ceiling. The same bylaws give Consortium Members the exclusive right to amend the W3C Process. That boundary matters because corporate oversight and technical standard-setting can affect each other without becoming the same act.

The Board can set corporate strategy, oversee management and finances, approve budgets and commission audits. The Board's own skills and expectations document explicitly says it is not an operational body and is not responsible for W3C's technical agenda. Process decisions belong to the Consortium's standards machinery, not to a new Board slate. Election to the Board does not certify a specification, rewrite a Process rule or make a director's employer the voice of all Web users.

There is still real power in a budget and a CEO evaluation. A technical group may hold the formal agenda while its capacity depends on staff time, infrastructure and funding governed at corporate level. Calling the Board "non-technical" must not make that indirect leverage disappear. Conversely, recognizing that leverage must not be inflated into a claim that directors can order a Working Group to adopt a favored standard. The proper account identifies which decision belongs to which body and how one decision changes the conditions under which another can work.

This election is not a report of capture or misconduct. The public materials establish a selection result and standing role boundaries, not how any incoming director will vote. The earlier BTW examination of the interim executive's concurrent Board position concerned a specific oversight relationship. This result instead tests a broader handoff: how Member participation becomes corporate fiduciary authority without becoming a delegated mandate over standards.

Sources