Re: [csswg-drafts] [css-view-transition-1] `visibility: hidden` analogy is misleading, elements remain keyboard-focusable and accessible (#12629)

I don't have a strong preference regarding the default behavior around accessibility, focusability, and interactivity.

To avoid confusion between these aspects, here’s the mental model I use:

| # | Visible | Accessible | Focusable / Interactive | Example                         |
| - | ------- | ---------- | ----------------------- | ------------------------------- |
| 1 | ✅       | ✅          | ✅                       | `visibility: visible`           |
| 2 | ✅       | ✅          | ❌                       | ?                               |
| 3 | ✅       | ❌          | ✅                       | `aria-hidden="true"`            |
| 4 | ✅       | ❌          | ❌                       | `inert`, `interactivity: inert` |
| 5 | ❌       | ✅          | ✅                       | `opacity: 0`                    |
| 6 | ❌       | ✅          | ❌                       | ?                               |
| 7 | ❌       | ❌          | ✅                       | ?                               |
| 8 | ❌       | ❌          | ❌                       | `visibility: hidden`            |

2. Maybe a `interactivity: none` proposal.
 Or maybe a modified `inert` [polyfill](https://github.com/WICG/inert/blob/main/src/inert.js) that don't apply `aria-hidden="true"`.

6. Maybe `opacity: 0` plus a modified `inert` polyfill that don't apply `aria-hidden="true"`.

7. Maybe `aria-hidden="true"` plus `opacity: 0`.

-- 
GitHub Notification of comment by sb3nder
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12629#issuecomment-3243344695 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 1 September 2025 22:44:40 UTC