- From: Joshue O Connor <joshue.oconnor@cfit.ie>
- Date: Fri, 02 May 2014 13:26:01 +0100
- To: Cynthia Shelly <cyns@microsoft.com>
- CC: W3C WAI Protocols & Formats <public-pfwg@w3.org>
Cynthia Shelly wrote: > For the most part, I'm happy with flexbox. It will be much easier to work with than absolute positioning and floats. [...] > Another option that wouldn't introduce a normative requirement would be to create a WCAG failure for this and link to it. [aside: I remember a WCAG failure for absolute positioning, but I don't see it now.] I would like to see such a WCAG failure regardless of any changes in this spec, and a couple of techniques on how to use it accessibly. I have some samples that avoid order and *-reverse. We would also need one each using nav-index and tabindex. We may find that tabindex is a bad idea, since it's markup and flexbox is css. That sounds to me like you are volunteering! Sold! :-) Your input into our Technique development crew would be very welcome. Josh
Received on Friday, 2 May 2014 12:26:35 UTC