- From: JAWS-test via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Sep 2021 05:09:47 +0000
- To: public-css-archive@w3.org
@fantasai > Note: Currently, many user agents and/or accessibility tools don't correctly implement the accessibility implications of visible elements with semantic relationships to invisible elements, ... I do not think this phrasing is correct. If I had thought that the CSS specification was correct and only the browsers or the screen readers were doing it wrong, I would have posted a ticket for the browsers or the screen readers. However, I think the problem is in the CSS specification and that's why I opened the ticket here. How should the browsers and screen readers correctly handle visible content within invisible content? There is no good solution for this and that's why I would actually be in favor of abolishing the possibility of nesting visible content within invisible content. However, this is probably not possible and therefore there should be an appropriate warning, but not blaming the browsers or screen readers. -- GitHub Notification of comment by JAWS-test Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6123#issuecomment-913344797 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 September 2021 05:09:48 UTC