What is Open UI (open-ui.org)?

Updated

Open UI is a W3C Community Group whose purpose is to let web developers style and extend built-in web UI components and controls — dropdowns, checkboxes, radio buttons, date and color pickers, and similar elements. If you have ever rebuilt a <select> from scratch just to control its appearance, Open UI is the group working to make that unnecessary.

What Open UI is trying to change

Today, component frameworks and design systems routinely reinvent common web UI controls so that designers get full control over appearance and behavior. Open UI starts from the premise that this reinvention should not be required for built-in controls.

To get there, the group's stated work includes:

  • Fully specifying the component parts, states, and behaviors of built-in controls
  • Defining the necessary accessibility requirements
  • Providing test suites to ensure compatibility
  • Implementing polyfills for extensible web UI controls

The scope is deliberately broad: it covers not just how a control looks, but how it is structured, what states it can be in, how it behaves, and how it remains accessible.

Who benefits, and how

Two audiences are addressed directly in Open UI's own framing.

Developers who want to style native controls. The specification work and test suites are aimed at making built-in controls styleable and extensible without a full custom rebuild.

Teams that choose to build their own anyway. Open UI expects design systems and component frameworks to benefit from its specifications and test suites even when they decide to implement their own controls — the specs give them a shared reference for parts, states, behaviors, and accessibility.

Long term, the group hopes to establish a standard process for developing high-quality UI controls suitable for addition to the web platform.

How to get involved

Open UI describes itself as community-supported, and points contributors to two channels: Discord and GitHub. Both are the practical entry points if you want to follow the work, raise a use case, or contribute to specifications and polyfills.

For the complete outline of goals and process, the group's full charter is the authoritative document to read rather than secondhand summaries.