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.
The review focuses on the opportunities that were discussed in the summer of 2025. Best practice updated October 30, 2026: Verify support for a specific feature in target browsers before implementing. The previous edition provided usage rates and metrics improvement percentages without verifiable sources; these ratings have been removed.
New HTML Living Standard status
HTML Living Standard is updated continuously. It is not a separate “HTML 2025” release: check each element and API, and preserve the core user flow in browsers that do not support them.
Native modal window <dialog>
element <dialog> gives built-in modal window mechanisms when called showModal(). For acceptance, check the available title, initial focus, keyboard close, and return focus to the open button. The presence of a native element does not negate the accessibility testing of the finished interface.
In the example, the modality includes showModal(). Easily adding an attribute open shows the window without the same modal behavior.
Popover API: The Dropdown Revolution
Popover API allows you to show modeless pop-up elements in the top display layer. Popover doesn't block the rest of the page as a modal dialog; roles, keyboard control and button binding need to be thought out for a specific component.
The Impact of Semantics on Core Web Vitals
Semantic markup helps describe the structure of a document, but does not in itself guarantee an improvement in INP or CLS. After replacing a component, measure Core Web Vitals in real-world scenarios: interaction processing latency, layout shifts, and amount of JavaScript executed. You need to compare identical pages and conditions.
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>
<!-- While the menu or loader is open, users cannot -->
<!-- click or tab into this section -->
<h2>Content</h2>
<a href="#">Link</a>
</main>Attribute inert excludes the subtree from the interaction and accessibility tree. It does not create a modal window or transfer focus to the panel itself: managing focus and the available method of closing remain part of the implementation.
Summary
Native elements can reduce the amount of custom code. Accept a replacement only after checking browser support, keyboard interaction, and performance.
If the interface is built via npm or works together with a Node.js server, check the build and launch environment separately. In plan to update Node.js to a supported LTS branch There is a dependency check and rollback. A static HTML page without such a build does not require a Node.js update.
When corporate website development Include accessibility, target browsers, and measurable performance criteria in your requirements.
Free project cost estimate
Answer four questions to request a price range for your project.