W3C home > Mailing lists > Public > public-pfwg@w3.org > October 2014

CSS flexbox

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Tue, 7 Oct 2014 17:44:04 -0500
To: "Janina Sajka <janina@rednote.net(janina@rednote.net)" <janina@rednote.net>
Cc: cooper@w3.org, "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Message-ID: <OF69C076EF.7B8DAC7A-ON86257D6A.006FD330-86257D6A.007CE24D@us.ibm.com>


Janina,

We would benefit from a meeting with CSS at TPAC. These are the topic
areas:

1. The injection of content into HTML

We went a bit deeper into name computation pertaining to CSS in the ARIA
implementation meeting today.

The new content property injects content into a web page. ... Looking at
section 12.2 (http://www.w3.org/TR/CSS21/generate.html) you can use CSS to
inject a broad range of attributes that an accessibility test tool would
need to parse from computed style. That is a lot to ask of accessibility
test tools. Joseph, Cynthia, and I were not favor of CSS injecting all this
content but the cat is already out of the bag.

2. The impact of CSS Flexbox on navigation order. Flexbox changes the
visual order and should logical navigation order. So, if we follow tabindex
alone I think we are going to have a problem for authors. What would be
good would be to be able to direct navigation based on flow vs. the DOM
structure. Either this or we have to have browser implement some sort of
flowto into the a11y api mapping to enable ATs in screen navigation using a
logical order.

Rich

Rich Schwerdtfeger
Received on Tuesday, 7 October 2014 22:44:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:09 UTC