Developers still search for HTML6 and CSS5. Neither exists nor is planned. Browsers now ship useful features one at a time, each with its own level of support. The real task for teams in 2026 is to judge which ones are ready for production.
The WHATWG maintains the HTML Living Standard and updates it continuously. A feature reaches developers when browsers ship it, not when a version number is announced.
CSS works in modules. Each module has its own level, such as Selectors Level 4 or Color Level 5. The name CSS Color Level 5 explains much of the CSS5 confusion. It describes one module, not the whole language.
Web APIs sit apart from both. WebRTC and WebGPU have their own specifications and are not part of HTML.
Searches for HTML and CSS features in 2026 return long lists. This table sorts them by readiness as of October 2026. Established means safe for most projects. Newly available means supported in core browsers, though older devices may lack it.
| Feature | Problem It Solves | Status |
|---|---|---|
| Popover API and <dialog> | Menus, tooltips, and modals without a library | Established |
| Custom Elements and Shadow DOM | Native reusable components | Established |
| Container queries | Components that respond to their container | Established |
| CSS nesting, @layer, :has() | Cascade control and conditional styles | Established |
| @scope | Scoped CSS styling | Newly available, December 2025 |
| CSS anchor positioning | Tooltips and dropdowns positioned relative to a trigger | Newly available, January 2026 |
| field-sizing: content | Auto-growing text fields and textareas | Newly available, June 2026 |
| sibling-index() and sibling-count() | Position-aware styling without JavaScript | Newly available, August 2026 |
| Invoker commands (command and commandfor) | Buttons that control dialogs and popovers | Newer; verify browser support |
| Customizable <select> | Styled dropdowns that retain native behaviour | Limited; Chromium first |
| CSS if() | Inline conditional values | Experimental; Chrome and Edge only |
| Grid lanes (native masonry) | Masonry-style layouts without JavaScript | Experimental; Safari only |
| WebGPU | GPU-accelerated graphics and compute | Available, with browser, platform, and hardware limitations |
The biggest HTML changes replace small JavaScript libraries with native elements. The popover attribute and the dialog element handle menus, tooltips, and modals. The two behave differently and work best as separate tools. An automatic popover closes when a user clicks outside it or presses Escape. A modal dialog opened with showModal() stops interaction with the page behind it and manages focus.
Invoker commands let a button open a dialog without an event handler. The feature is new. A script should remain as a fallback.
Forms improved too. The :user-valid pseudo-class styles a field only after interaction.
Customizable select, set with appearance: base-select, allows styled dropdowns with native keyboard behavior. Chrome and Edge shipped it first. Other browsers show a normal select.
Web Components offer native features for reusable elements. Custom Elements define behavior. Shadow DOM encapsulates markup and styles. Declarative shadow DOM reached baseline. Widely available in August 2026. Larger applications still need other tools for state, routing, and rendering.
The latest CSS features arrive at different speeds. Container queries let a component respond to the size of its container instead of the viewport. They have been stable since 2023. Native nesting and @layer reduce the need for preprocessors and specificity hacks. The: has() selector, often called the parent selector, reached Baseline Widely available in June 2026.
Color Level 5 adds color-mix() and relative color syntax. Together with oklch() and light-dark(), these simplify theming, though text contrast still needs testing.
Newer features need a fallback. The @scope rule gives real style scoping and reaches all three major engines in December 2025. CSS anchor positioning ties a tooltip or dropdown to its trigger without scripted math. Its core became baseline and was newly available in January 2026.
Some sub-features remain limited. The sibling-index() and sibling-count() functions replace long :nth-child() ladders for staggered animations. Both became baseline newly available in August 2026.
The if() function works only in Chrome and Edge. Grid lanes, the native masonry layout, ships unflagged only in Safari 26.4 and later. A plain responsive grid should come first.
A product card shows three features working together. Container queries set the card layout from its available space. The popover attribute opens and closes a specs panel. Anchor positioning places the panel beside its button. Browsers without it still open the panel in the default position. The content stays usable.
Latest-browser support does not guarantee safety for an audience. Newly available means a feature runs in the core browsers. Widely available means it has done so for about 30 months. Baseline cannot show which devices real users own. Analytics should set the threshold. Teams should build the core experience with stable features and add newer ones on top. Feature detection with @supports gives older browsers a sensible fallback.
One of the web development trends of 2026 made clear is selective adoption. Container queries, : has(), popovers, and dialogs are ready now. Anchor positioning, @scope, field-sizing, and the sibling functions suit progressive enhancement. The if() function, grid lanes, and customizable select should stay behind @supports until more browsers catch up.
Native features will keep replacing scripts and libraries. The teams that benefit most will track browser release notes early and adopt each feature once their audience can use it. The platform rewards patience more than speed.