What's new in HTML and layout specifications: summer 2025
The summer of 2025 was marked by a number of significant innovations in the HTML and web development ecosystem. Developers' dependence on heavyweight JavaScript libraries to create basic interface components is rapidly decreasing. Browsers are increasingly taking responsibility for complex UIs, improving performance.
These changes concern not only the WHATWG specifications, but also the evolution of accessibility practices (a11y), as well as their direct impact on Core Web Vitals metrics (affecting SEO).
New HTML Living Standard status
WHATWG has published a major update to the HTML Living Standard edition. The era of “div-soup” (wrapping everything in <div>) is officially a thing of the past.
Full tag support <dialog>
element <dialog> is now officially supported in all current browser versions, including the release of Safari 18 on the WebKit engine.
There is no longer any need to include third-party libraries (such as SweetAlert2 or old jQuery UI) to trigger pop-up windows. Native <dialog> It is hardware accelerated by the browser and automatically solves focus problems.
<!-- Нативное, доступное модальное окно -->
<dialog class="dialog" id="promo-modal">
<h2 class="dialog__title">Специальное предложение</h2>
<p>Контент окна. Задний фон автоматически блокируется.</p>
<form method="dialog">
<button class="button-close">Закрыть</button>
</form>
</dialog>
<!-- Вызов модального окна без написания JS логики управления фокусом -->
<button onclick="document.getElementById('promo-modal').showModal()">
Открыть акцию
</button>Interesting fact: According to the study State of HTML 2025, more than 42% of frontend developers have already completely abandoned custom solutions in favor of native ones <dialog>.
Popover API: The Dropdown Revolution
In mid-2025, Chrome, Firefox and Safari finally synced support popover API. This is a mechanism for creating native pop-up elements, tooltips and dropdown menus, which are rendered on top of all other layers (top layer), avoiding conflicts z-index.
The Impact of Semantics on Core Web Vitals
The Chrome UX Report 2025 teams once again confirmed that the right semantics directly affect site performance. According to the results of the global analysis:
- INP (Interaction to Next Paint) optimization: Sites using native controls and correct structure (
<main>,<section>,<article>), exhibit input lag 12% lowerthan projects with deep nesting of divs. It is easier for the browser to parse the semantic tree. - CLS (Cumulative Layout Shift) optimization: Native
<dialog>andpopovershow a 17% improvement in visual stability, since the browser knows in advance their behavior in the Layout loop, unlike JS animations that cause style recalculation (Reflow).
Attribute inert: Full focus control
Although the attribute inert appeared a little earlier, in 2025 it became the de facto standard for creating complex SPA applications.
Addition inert to any element makes it (and all its descendants) physically unavailable for clicks, text selection, and keyboard navigation (Tab).
<main id="app" inert>
<!-- Пока открыто меню или loader, пользователь не сможет -->
<!-- кликнуть или добраться табом до элементов этой секции -->
<h1>Контент</h1>
<a href="#">Ссылка</a>
</main>This is incredibly useful for creating side menus (OffcanvasDrawer) when you need to hard lock the user's focus inside an open panel.
Summary
HTML in 2025 is not just a markup language, it is a powerful declarative UI framework. Switching to native APIs (Dialog, Popover, inert) allows front-end developers to write less code, send less JavaScript over the network, and create interfaces that are Accessible and fast by default.
Specialists NBM-IT follow the latest web specifications. We develop fast and accessible interfaces while adhering to strict Google Core Web Vitals standards, which directly impacts the growth of your SEO rankings.
Free project cost estimate
Answer 4 questions and we will send you a range of prices to suit your needs.