WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: definition list or data table

for

From: Ryan E. Benson
Date: Dec 14, 2012 3:54PM


I would roughly write a narrative with the code following. Depending on the
audience, I would maybe think about combining the blocks when appropriate.
Ex:

The basics of a tweet are the unique ID that it gets, text of the tweet,
which are tied to variables id, text, and created_at, respectfully.
{Code here}

If the tweet is a reply to another, variables {here} are assigned values,
otherwise their value is nil.

etc

--
Ryan E. Benson



On Fri, Dec 14, 2012 at 4:53 PM, Catherine Roy < <EMAIL REMOVED> >wrote:

> Hi,
>
> A friend of mine wants to describe an image that explains the anatomy of
> a tweet (similar to this one) :
>
> <http://i.i.com.com/cnwk.1d/i/tim//2010/04/20/30146338-map-of-a-tweet.png>;
>
> He will be using a separate page for the description though I am not
> sure yet whether he will be using longdesc or just adding a visible link
> on the main page but regardless, the question is how to best
> structurally represent this compex image, especially for screen reader
> users, wherein we have code examples and explanations tied to the code
> examples.
>
> My first instinct would be to use a data table but thinking further on
> it, I am not sure. Perhaps a definition list ? Or something else
> altogether ?
>
> Thanks,
>
>
> Catherine
>
>
> --
> Catherine Roy
> http://www.catherine-roy.net
>
> > > >