WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: evaluating accessibility with WCAG 2.0 (Angela French)

for

From: Andrew Kirkpatrick
Date: Apr 8, 2011 3:03PM

I do agree that this is a best practice, but I don't believe that this rises to the level where it would be required by WCAG 2.0. It is pretty easy to start seeing lists everywhere, but should any time that there is more than one link in a row a ul element be used?

My gut is that, for example, with a list of links at the bottom of a page that there is more benefit from the use of a list for the developer implementing consistent styling than for a user with a disability. I don't know of any study that digs into whether there is a difference for end users but it would be interesting to see.

If people feel that not using a UL element constitutes a failure, please submit it to the WCAG working group and we can debate it and produce an official failure technique if the consensus is that it should be a failure.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe Systems

<EMAIL REMOVED>
http://twitter.com/awkawk
http://blogs.adobe.com/accessibility


-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Karen Sorensen
Sent: Friday, April 08, 2011 2:30 PM
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] evaluating accessibility with WCAG 2.0 (Angela French)

Good reminder John Hicks. The separation of content from design/layout/format with CSS is critical. If the pipes are used to separate a list, but the list isn't HTML coded as a list, that would be interpreted incorrectly by a screen reader.

Karen Sorensen
PCC Instructional Technology Specialist
Coordinating ADA Compliance of Instructional Media
971-722-4720