W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2015

Re: SC 1.3.1 and virtual columns

From: Phill Jenkins <pjenkins@us.ibm.com>
Date: Tue, 8 Dec 2015 17:47:17 -0600
To: w3c-wai-ig@w3.org
Message-ID: <OFF63F79BE.DA1F0ED3-ON86257F15.00802AED-86257F15.0082ADF7@us.ibm.com>
Your code does fail 1.3.2 - Meaningful Sequence
Examples of Success Criterion 1.3.2
Example 1: In a multi-column document, the linear presentation of the 
content flows from the top of a column to the bottom of the column, then 
to the top of the next column.

Regarding your question about applicability of SC 1.3.1 - Info and 
Relationships: Information, structure, and relationships conveyed through 
presentation can be programmatically determined or are available in text 

I do not think SC 1.3.1 always applies in your example description.  It 
would if there were headings at the top of each colum that were not marked 
as headings, or regions (landmarks) if the purpose of each column was 
conveyed some other way.  However, SC 1.3.1 would apply if the information 
in the column is referred to in the text by its column position 
(realtionship to the other columns) - for example, if someone had to do 
something with xyz in column 3, how would the AT user be able to determine 
that without sight? The AT would only know there are DIV's, not columns. 
There would have to be a heading or label or something like that  that is 
redundant with the visual positioning.  E.g. "do something with xyz in the 
Highlights section in column 3... If the information is not referred to by 
it relationship (e.g.column 3), then SC 1.3.1 is not applicable in my 

Another example is where a 3 column layout transfroms to a single column 
layout when going from desktop view to smartphone view and there is no 
loss in information relationship needed to use the app.
Phill Jenkins, 
IBM Accessibility

From:   Oscar Cao <oscar.cao@live.com>
To:     <w3c-wai-ig@w3.org>
Date:   12/08/2015 03:53 PM
Subject:        SC 1.3.1 and virtual columns

Hello fellow interest group members.
I would like to know what the interest group?s views/opinions are in 
regards to SC 1.3.1 and the following scenario.
The page has a three column layout (not created using tables). There?s a 
?box container of information?, it has been positioned via CSS to appear 
in the virtual third column. However, in the source code, it sits at the 
very start of the content section, see code below:
<div class=?box?>
<!-- box container of information -->
<div class=?column?>
<!-- column one -->
<div class=?column?>
<!-- column two -->
<div class=?column?>
<!-- column three -->
The box container information is self-contained and will make sense 
wherever you place it. Thus, I didn?t bring up SC 1.3.2 (that talks about 
sequence). However, I am unsure if the positioning of the box information 
breaks SC 1.3.1. in regards to not being able to programmatically 
determine the visual position/location of the box container. Sighted users 
see it in column three, while AT users see it as the first thing.
Received on Tuesday, 8 December 2015 23:48:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 8 December 2015 23:48:08 UTC