WebAIM - Web Accessibility In Mind

E-mail List Archives

1.3.2 meaningful sequence

for

From: adam solomon
Date: Jan 27, 2011 8:09AM

An example:
Html consists of two lists of names with corresponding checkboxes - the
first list consists of potential people who can be added to the second list.
The second list are the people who have already been added. The two lists
come one after another in the DOM, yet they are visually presented
side-by-side by css float. In between the two lists, both in the DOM and
visually are two buttons - one button adds an entry from the first list to
the second list, while the other button causes an entry already added to the
second list to be removed from it and placed back in the first list. I was
concerned about the fact that the remove button, which would need to be
clicked after choosing from the second list, comes before that list in the
DOM. In order to clarify things, we added a short explanation of how the
whole thing works. Technically, the DOM sequence matches the visual
sequence, yet visually it is easier to pick up on the fact that the buttons
"drag" names from one list to the other. The client is unwilling to change
the position of the buttons. Are we in violation of WCAG here, specifically
1.3.2<http://www.w3.org/TR/2010/NOTE-UNDERSTANDING-WCAG20-20101014/content-structure-separation-sequence.html>;,
or any other criterion> more importantly, does a screen reader user stand a
reasonable chance to understand how to operate the lists?

Thanks in advance for any feedback.

--
adam solomon
linkedin <http://il.linkedin.com/pub/adam-solomon/24/449/a4>;
blogix <http://adam.blogix.co.il/>;