- From: Alice <notifications@github.com>
- Date: Wed, 07 Jun 2023 06:28:37 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <WICG/webcomponents/issues/1014/1580825818@github.com>
Thanks for the summary, @bennypowers. Just to add some nuance, the experiment I ran was: - In a local build of Chromium, I commented out the check for an element with `aria-hidden=true` being focusable in order to include it in the accessibility, so that *all* elements with `aria-hidden=true` are hidden from the accessibility tree, undoing the fix which was added in order to prevent a poor experience from focusing on `aria-hidden` elements. - I then experimented with https://codepen.io/sundress/pen/dyQyqjd?editors=1011 (forked from an earlier demo by @bennypowers) in my local build, using VoiceOver. - I could verify that the `<input>` was hidden from the accessibility tree, and that, surprisingly, when keyboard focus was placed on the `<input>`, there was an announcement that VoiceOver was on an edit field. - However, that's about where the success of the experiment ended: I couldn't get any label association to work, and input into the text field wasn't announced the way it is with the plain `<input>`. I'm less than optimistic about this as a viable pathway even with this mild success; I think there will be a lot of details to figure out, and I would rather we spend that energy on one of the less hacky, longer-term, more general options. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/1014#issuecomment-1580825818 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/1014/1580825818@github.com>
Received on Wednesday, 7 June 2023 13:28:43 UTC