inert does not yet exist in the specification, in my opinion, and is not supported by any browser (except to a limited extent: Safari): whatwg/html#4288, https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/inert

@JAWS-test sorry didn't mean the HTML attribute. In this case the Datepicker Dialog uses aria-modal="true" but does not prevent all users from interacting with content outside of it. It also does not visually obscure content outside of it.

As long as the date picker is open, the keyboard focus cannot be moved out of it. Also, aria-modal=true causes the page to be hidden in the background for screen reader users. I think that makes sense. The rest of the page can't really be interacted with while the datepicker is open. Attempting to interact with the page will cause the datepicker to close. Only then can the page be interacted with. The fact that the page is not grayed out in the background is not probematic in my opinion. The HTML inert probably won't gray anything out either.

@JAWS-test A sighted keyboard user can use a mouse and click the links on the page while the datepicker using aria-modal="true" is open. Our note on aria-modal usage says this should not be possible with the phrase "prevents all users from interacting in any way with content outside of it". It seems that either this example needs to be fully developed as a modal or our note on aria-modal usage needs to be changed, see #2204.

I agree that the datepicker example and the explanation about aria-modal at the dialog contradict each other. However, in my opinion, aria-modal is correct at the datepicker, so I am in favor of either

• adjust the explanation at the dialog
• or add to the explanation that this refers only to modal dialogs, but aria-modal can be used in other contexts as well.