- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Mon, 21 Jun 2021 14:03:23 +0100
- To: w3c-wai-ig@w3.org
On 21/06/2021 13:26, Pearson, Amy wrote: > Example page: https://www.apa.org/monitor/2021/04/ceo > <https://www.apa.org/monitor/2021/04/ceo> Interesting/odd behaviour here on the part of Chrome. It appears that (even on Windows) Chrome sees the contents of the <footer> as being the element that gives the <div id="maincontent" tabindex="-1"> its accessible name (you can verify in Chrome DevTools by choosing that element and checking the Accessibility tab. My guess would be that because of the tabindex, Chrome wants to make sure there's an accessible name, and (because of the internal structure of what is inside there, with the separate <main> etc) somehow falls back on using the footer content. Not quite sure why. A way to work around this odd behaviour would be to move the <footer> out of that <div> (so it's a sibling element, rather than a child). Definitely funky behaviour though... 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 Monday, 21 June 2021 13:04:18 UTC