Web platform

State of HTML 2026: built-in elements win, form controls still hurt

State of HTML 2026: built-in elements win, form controls still hurt

Somewhere, right now, someone is building a disclosure widget out of three divs, a click handler and an aria-expanded they'll forget to flip. According to the State of HTML 2026 results, that person is getting lonelier. Good.

The numbers, via Frontend Focus #767: <details>/<summary> is the most used interactivity feature at 72.5%, with <dialog> close behind at 67.8%. Use of the Popover API reached 40%, and Frontend Focus links that to the API now working in every major browser. The newsletter's one-line read is that declarative, element-based features are the winners. (Think about what the top two have in common. Both elements hand you open and closed state for free. No state library, no toggle function, just markup.)

The form-control wall is still standing

Here's the less fun half. <select> and date inputs rank as the hardest elements to style. Customizable select is the feature most held back by browser support, and Firefox has yet to ship it. So the fix aimed at the biggest styling complaint is the one you can't count on in every engine yet. Rough.

<datalist> is the weird one. Usage jumped from 30% to 44%, while positive sentiment fell from 44% to 34%, and respondents pointed at styling, accessibility and browser bugs. More people tried it and fewer of them liked it, which is basically every nu-metal band's second album.

The wishlist is telling. Native data tables with built-in sorting and filtering came out on top, ahead of tabs, comboboxes and switches, and HTML includes showed up again too. I'll admit the sortable table one got me. I've written that sort-by-column handler more times than I want to count, and every copy was slightly broken in a new way. A platform version would delete a lot of my old code.

Kilian Valkhof's conclusion to the survey lands on the hopeful side: "Our industry might be in turmoil, but I think our foundation is in good shape."

I'm with him on that. The disclosure and modal stuff is solved, and people are actually using the solutions. Forms are where the work is left. Foundation: 8/10. Form controls stay at a 5 until customizable select ships in every engine.

Source: Frontend Focus (frontendfoc.us)

Related
Accessibility & semantics

Customizable `<select>` is still a `<select>`: keep the text

WebKit's golden rule for the new customizable `<select>` is the rule we should have been following all along: every option needs real text, even when icons or swatches do the visual work.

June 20, 2026
Browser releases

Safari Technology Preview 249 drops attr(), if(), @function, popover=hint and Temporal in one build

WebKit's July 29 preview stacks nine CSS additions, a new HTML popover value, the dialog closedby attribute, and the JavaScript Temporal object into a single release — one of the feature-densest STP drops of the year for hand-authored HTML and CSS.

July 30, 2026
Accessibility & semantics

A primary-nav flyout built on `popover`, not `aria-expanded`

Adrian Roselli has rebuilt his 2019 disclosure-widget primary nav on the native HTML `popover` attribute. The rebuild is a clean map of what the platform now carries for you, and where you still need ARIA.

July 9, 2026