- From: Doug Schepers <schepers@w3.org>
- Date: Fri, 17 Apr 2015 09:05:34 -0400
- To: Richard Schwerdtfeger <schwer@us.ibm.com>, public-svg-a11y@w3.org, Florian Rivoal <florian@rivoal.net>
Hi, Rich– Thanks for pulling this together. I had a short conversation with Florian Rivoal (CCed), the editor of the CSS-UI L4 spec, and we talked about focusability in CSS, including the notion of a 'focusable' property (to reflect the existing state in CSS), and about depth/nesting. He's agreed to join a future telcon with us to help coordinate. I propose that the implicit "semantic" mechanism for the focusability of an element be the following: * textual elements * links (<a>) * any element (including <g>) with a <title> or <desc> immediate child We can also allow explicit focusability, but the default should just fall out of the model. Regarding the depth/nesting proposal, I'm fine with what you've written. I do think we should emphasize that nested containers is the proper way to do that; this could be either container elements like <g> or <svg>, or some sort of virtual grouping that lets an author override/work around the tree structure. Again, this should be a consequence of the model. Regards– –Doug On 4/16/15 7:12 PM, Richard Schwerdtfeger wrote: > Here is a draft proposal on navigation that I discussed. Jason has not > modified it yet: > > https://www.w3.org/wiki/SVG_Accessibility/Navigation > > > Rich Schwerdtfeger >
Received on Friday, 17 April 2015 13:05:44 UTC