A multi-step interface keeps the next panel in the document while it is inactive. Hiding it visually with an offset or faded style may leave its links and controls reachable by keyboard. The HTML inert attribute provides a way to make a whole section inactive for interaction.
MDN’s inert reference explains that the element and its relevant descendants cannot receive focus or clicks and are removed from the accessibility tree. Inert also affects text selection and browser find behaviour. It is more than a visual dimming effect.
Use it for the intended state
For a panel that is genuinely unavailable, applying inert can prevent users from accidentally entering controls that do not belong to the current step. When the panel becomes available, remove the attribute and manage focus according to the interaction.
Inert is a Boolean attribute. Writing inert=”false” still leaves the attribute present and therefore active. Remove it or set the corresponding DOM property appropriately. A descendant cannot ordinarily undo an inert ancestor simply by setting its own property to false.
Test the complete transition
Check where keyboard focus is before the state change, where it goes afterwards and whether users can return to the previous step. Confirm that inactive content is presented clearly; inert alone does not automatically provide a visual indication.
Do not make explanatory content inert merely because it contains a disabled action. Users may still need to read why an action is unavailable. For an individual form control, native disabled behaviour may be the appropriate choice instead of deactivating an entire section.
Test keyboard navigation and assistive-technology behaviour in the browsers your product supports. Include the reverse transition, since a panel that never becomes interactive again is an easy implementation mistake. The goal is a predictable interface state, not simply a page with fewer focusable elements.

