Adrian Roselli on Nostr: npub1atk2w…lk3se I cannot make out that code (and it is not at a URL I can test), ...
npub1atk2wyywh2lwcvp2tm3wlsn35x0q5duqclftlgcjvk7mmh696dtsalk3se (npub1atk…k3se)
I cannot make out that code (and it is not at a URL I can test), but the issue I have raised (and which still exists) is that `display: contents` on an *interactive* element is where it falls down. Not the wrapping element.
As I note at https://adrianroselli.com/2022/07/its-mid-2022-and-browsers-mostly-safari-still-break-accessibility-via-display-properties.html, in Chrome and FF (last row & last column in each table) it is possible to activate the buttons with a mouse only.
I did not cover links in that post, but same deal.
npub1qwkaun0pqpnzswj2c0gtn2aggllvxwzvt855qnft7vw3zcc5dh2sjh8gvk (npub1qwk…8gvk)
I cannot make out that code (and it is not at a URL I can test), but the issue I have raised (and which still exists) is that `display: contents` on an *interactive* element is where it falls down. Not the wrapping element.
As I note at https://adrianroselli.com/2022/07/its-mid-2022-and-browsers-mostly-safari-still-break-accessibility-via-display-properties.html, in Chrome and FF (last row & last column in each table) it is possible to activate the buttons with a mouse only.
I did not cover links in that post, but same deal.
npub1qwkaun0pqpnzswj2c0gtn2aggllvxwzvt855qnft7vw3zcc5dh2sjh8gvk (npub1qwk…8gvk)