@css@front-end.social I'd lean toward role=none. It's a little bit safer in the sense that if you one day forgot and stuck content inside that container, only the container would be pruned from the accessibility tree, not the content. In contrast, with inert, the entire subtree gets removed from the accessibility tree, and if it's not interactive, you'd never know because the inert attribute doesn't have any default visual styling. Imo, this makes the inert attribute dangerous and best avoided unless it's absolutely necessary.