- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sun, 22 Sep 2019 00:11:00 +0000
- To: public-svg-issues@w3.org
AmeliaBR has just labeled an issue for https://github.com/w3c/svgwg as "HTML Consistency": == Compatibility of focusability with HTML & platform conventions == From @litherum / @rniwa https://svgwg.org/svg2-draft/single-page.html#interact-Focus mentions how any element that generates a scrollable region should be treated as if tabindex=0 is set. This is a weird “should” statement given HTML doesn’t do this. It’s also problematic because it would mean that we can’t decide whether an element is focusable or not without layout information The section also mentions “focusable” content attribute. But it doesn’t really specify what happens when its value is set to “auto” or whether it supersedes tabindex=-1 or not: https://www.w3.org/TR/SVGTiny12/interact.html#focusable-attr For example, this SVG tutorial asserts that “focusable” would override tabindex: https://allyjs.io/tutorials/focusing-in-svg.html#making-svg-elements-focusable Given Firefox nor Chrome seems to implement this content attribute, it’s hard to tell what the right behavior is. See https://github.com/w3c/svgwg/issues/736
Received on Sunday, 22 September 2019 00:11:01 UTC