E-mail List Archives
Re: evaluating accessibility with WCAG 2.0
From: John Hicks
Date: Apr 7, 2011 4:27AM
- Next message: Patrick Dunphy: "Re: evaluating accessibility with WCAG 2.0"
- Previous message: Jason Kiss: "Re: evaluating accessibility with WCAG 2.0"
- Next message in Thread: Patrick Dunphy: "Re: evaluating accessibility with WCAG 2.0"
- Previous message in Thread: Jason Kiss: "Re: evaluating accessibility with WCAG 2.0"
- View all messages in this Thread
I agree with Jason; this clearly this is a violation.
Remember that one of the principles behind all "rules" for accessibility
is the separation of content and form.
Although seemingly innocent... the use of the pipe to separate the
elements points directly to a hard-coding of layout.
Using a correctly styled list would avoid this.
good day to all,
John
Le 07/04/2011 09:19, Jason Kiss a écrit :
> Whether or not it's a full-on violation is, like many things to do with
> semantic markup, open to interpretation. But should one want to take a
> strict approach, I could see calling it a failure of WCAG 2.0 SC 1.3.1
> since the content is fairly clearly, I would argue, a list of links, and
> so should be marked up as a list, as you describe.
>
> Making it a list would also provide assistive technology users with
> information about the number of links in the list. Such an approach is
> supported by Sufficient Technique H48: Using ol, ul and dl for lists or
> groups of links (http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/H48).
>
> Cheers,
>
> Jason
- Next message: Patrick Dunphy: "Re: evaluating accessibility with WCAG 2.0"
- Previous message: Jason Kiss: "Re: evaluating accessibility with WCAG 2.0"
- Next message in Thread: Patrick Dunphy: "Re: evaluating accessibility with WCAG 2.0"
- Previous message in Thread: Jason Kiss: "Re: evaluating accessibility with WCAG 2.0"
- View all messages in this Thread