WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Forms as lists

for

From: Kevin White
Date: Sep 2, 2010 1:20PM

That is pretty much the rationale that I adopt.

It is good to get the input of other screenreader users as I only really had the one sample to draw upon. He did say much the same as others here have.

I suppose I would question the inclusion of list items less if they were being visually represented as well, but they are not. The list bullet or list number is suppressed in all the examples I have seen of this. This suggests that these are not really lists, and the developers are not thinking of them as lists since they do not present them as lists. If screenreader users are saying that this simply adds clutter then drop them and use non-semantic elements such as div.

Thanks

Kevin

On 2 Sep 2010, at 13:13, Steve Green wrote:

> My rationale is F43: Failure of Success Criterion 1.3.1 due to using
> structural markup in a way that does not represent relationships in the
> content - http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/F43
>
> Unfortunately the WCAG focus almost entirely on the addition of appropriate
> structural markup. Apart from F43 very little is said about the prevention
> of superfluous or inappropriate structural markup. For instance we are
> starting to see nonsense such as breadcrumbs being marked up as definition
> lists or fieldsets around Submit buttons. F43 appears to be the only means
> we have of fighting back against these things.
>
> Regards,
> Steve
>
> Address list messages to <EMAIL REMOVED>