W3C home > Mailing lists > Public > www-style@w3.org > August 2012

[css3-flexbox] PF Comments on Flexbox

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 08 Aug 2012 13:19:25 -0700
Message-ID: <5022C9CD.9030400@inkedblade.net>
To: chairs@w3.org, "www-style@w3.org" <www-style@w3.org>, W3C WAI Protocols & Formats <w3c-wai-pf@w3.org>
Responding to Janina's message forwarding the WAI-PF WG's comments on
the CSSWG's CR transition request for CSS Flexible Box Layout:
   https://lists.w3.org/Archives/Member/chairs/2012JulSep/0049.html
Threading is broken because I'm not a member of chairs@ :)

Hi Janina, WAI-PF,
Daniel Glazman forwarded your comments to us, and I have attempted
to address them as you requested.

With regards to the note about accessibility impact:

   I've added a note to the top of the Ordering and Orientation section,
   as you suggested. I also added an authoring conformance requirement
   that the reordering capabilities of Flexbox not be used as a substitute
   for correct source ordering. You can find the text in the editor's draft,
   here:
     http://dev.w3.org/csswg/css3-flexbox/#ordering-and-orientation

   There is also some relevant prose and conformance requirements in the
   section defining 'order', for which we have recently added a heading
   and an anchor:
     http://dev.w3.org/csswg/css3-flexbox/#order-accessibility

With regards to tab navigation:

   We discussed this issue back in June:
     http://lists.w3.org/Archives/Public/www-style/2012Jun/0478.html
   with the participation of John Foliot:
     http://lists.w3.org/Archives/Public/www-style/2012Jun/0481.html

   The conclusion was that following the source order and following
   the visual order both have use cases. We resolved that by default,
   the tab order should follow the source order. This keeps it
   consistent with the speech order and with other layout models,
   in which there is not such an obvious concept of "flow" as there
   is in Flexbox. We added advice to authors that the source order
   should remain logical for this and other reasons.

   We will, however, investigate providing some kind of switch in the
   future. The CSS Working Group agrees this is an area that needs
   further development, and there are other issues with tab navigation
   that also need work. We expect to take these up together the next
   time we visit tab navigation, in the UI module.
     http://wiki.csswg.org/ideas/nav-index

Please let us know if this addresses your concerns.

~fantasai
Received on Wednesday, 8 August 2012 20:19:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:58 GMT