- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 16 Jul 2020 11:41:53 +0100
- To: w3c-wai-gl@w3.org
On 16/07/2020 10:07, Wilco Fiers wrote: > The only way to make an iframe completely hidden in Chrome, Firefox and > Safari is if it has tabindex="-1" and if it has nothing in the > accessibility tree. Otherwise, if the iframe doesn't have tabindex="-1" > it creates a tab stop where nothing is announced in Firefox. If the > iframe isn't empty, VoiceOver in Safari will let you interact with the > frame. So this again leads to the core question of "does it need an accname when it's meant to be 'transparently' part of the host document" and "is there a way of making it 'transparent'. It may well be that currently, browsers are too idiosyncratic/buggy in how they handle iframes (forcing tab stops in a well-meaning attempt, but not allowing devs that intend to use them transparently to suppress that)...but in those cases (where it's already annoying that there's an extra tab stop that's unnecessary) is it then also a failure not to have an accname? Or is that "two wrongs don't make a right". Again, thinking about this burden of over-verbose output in the end unless you hack around it https://github.com/mdo/github-buttons/pull/148 P -- Patrick H. Lauke https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 16 July 2020 10:42:08 UTC