Re: [csswg-drafts] For the Accessibility API visibility:visible within visibility:hidden is problematic (#6123)

> At least for Firefox (speaking as the tech lead for Firefox a11y), any of these solutions is a massive undertaking and involves significant risk of potentially catastrophic regressions.

I do not doubt you. 

On the other hand, I would guess that most pages that use `visibility: hidden`, or responsive tables with display values that change for narrow layouts and hide the `theads` (none of which should change the semantics), and a lot of other things are just plain broken for a11y when (most) web authors don't take enough special care to try to work around some of the surprising things CSS can do to a11y. I don't mean to disparage your work, but it seems like there is a lot of opportunity to improvement for how CSS and a11y interact and intersect, and perhaps some of it could be done incrementally. 

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


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

Received on Wednesday, 15 September 2021 06:13:32 UTC