|
|
Posted by kchayka on 08/17/05 18:38
Greg N. wrote:
> Safalra wrote:
>
>> http://www.w3.org/TR/WCAG10-TECHS/#tech-divide-links
>>
>> Specifically: "Until user agents (including assistive technologies)
>> render adjacent links distinctly, include non-link, printable
>> characters (surrounded by spaces) between adjacent links."
>
> I have now implemented what my initial intention was, namely, to use the
> same list markup but different CSS
>
> Now, I have read the atricle about the adjacent links problem, but I am
> still wondering if I really should take the trouble to deal with it.
IMO, you have already dealt with "the adjacent links problem" by using
list markup. The list marker can provide the non-link, printable
character, even if you hide it via CSS. Using good, semantic markup is
better for creating accessible pages than adding kludges like
superfluous content just to satisfy some old, maybe obsolete, guideline.
Note that the W3C mentions "Until user agents [do such-and-such]..." and
that those guidelines are more than 6 years old. User agents have come a
long way since then, especially those in the assitive technology (AT)
category.
> Do you know which UAs have the problem, so I can have a look at my logs
> and try to find out what the magnitude of the problem is?
Even if 50% of your visitors use some sort of AT, you may find no record
of it in your logs. The most-used screen readers use IE as a rendering
engine, and just identify themselves as IE.
--
Reply email address is a bottomless spam bucket.
Please reply to the group so everyone can share.
Navigation:
[Reply to this message]
|