The State of HTML 2026 survey opened on October 1 and closes November 1, 2026, giving anyone who builds for the web a two-week window left to weigh in. It's run by Devographics, the team behind State of JS, State of CSS and State of Devs, takes 10 to 15 minutes, and asks a deceptively simple set of questions: which HTML and web platform features do you actually use, which ones do you avoid, and where do browsers still fall short. Teams doing production web application development are exactly the audience the survey is built for — the data only reflects reality if people shipping real pages, not just spec enthusiasts, fill it in.
It is tempting to treat another annual survey as background noise, but this one has a documented feedback loop. Google funds the State of surveys specifically because the results feed into prioritizing the Interop project for the following year — the cross-vendor effort where Apple, Google, Microsoft, Mozilla, Bocoup and Igalia agree on a shared list of interoperability bugs and missing features to fix across engines simultaneously. The survey's own retrospective credits developer feedback with directly shaping Interop 2024's focus areas, which is how the Popover API and Declarative Shadow DOM ended up getting cross-browser attention in the same cycle rather than shipping in one engine and sitting unimplemented everywhere else for years.
Your answers are not just sentiment — they are weighted input into which bugs get triaged first. If you mark a feature as "heard of it, never dare use it," that is read as an adoption barrier, not apathy, and the open-ended fields are where specific, reproducible complaints about layout quirks, SVG-in-CSS friction, or color and theming gaps get logged for the people setting next year's agenda. Filling out the survey takes less time than filing one well-written bug report, and it reaches six browser vendors at once instead of one issue tracker. For teams maintaining production sites, it is also a useful internal exercise: walking through the question list surfaces which platform features your own codebase still routes around with JavaScript or a polyfill, long after the underlying problem was fixed in CSS or HTML itself.
The survey closes November 1, 2026. Past editions have published aggregate results and write-ups within roughly six to ten weeks of closing, typically landing in December or January, with the Interop steering group reviewing proposals and developer-feedback data shortly after that to assemble the focus areas for Interop 2027. None of that changes what ships in your browser this week — but it is the mechanism that decided which rough edges from 2025's wishlist actually got fixed in 2026, and it is open for exactly as long as the window above says. After November 1, the only way back in is waiting for the 2027 edition.