Re: For your perusal

Octavian Rasnita:

>The idea is that you shouldn't care about all the accessibility standard=
s
>because some of them have no sense.

I am trying to meet WAI 1.0 requirements with my web sites, but=20
sometimes I found W3C guidelines hard to follow or very unclear at=20
best.

First... this is a question I already posted on the techniques list=20
weeks ago, that had only one reply:

Usage of 'lang' and 'title' attributes:

<.a href=3D"http://www.w3.org/TR/REC-DOM-Level-1"
    title=3D"[LINK ESTERNO] Collegamento alla Raccomandazione
           W3D DOM Level 1">
    <.span lang=3D"en">
  =A0	<.acronym title=3D"Document Object Model">DOM</acronym> Level 1
    </span>
</a>

The language of 'DOM Level 1' is English, and DOM is an acronym; the=20
acronym element inherits the lang attribute from the outer span=20
element, so it gets English. Outside, the <.a> element keeps the=20
document language (italian) because its title attribute is expressed=20
into Italian.

Anyway, there are two 'conflicting' title attributes on the 'DOM'=20
text fragment; and obviously the inner one (acronym) takes=20
precedence. The browser shows 'DOM Level 1' but if you roll the mouse=20
cursor over the 'DOM' fragment, you activate the acronym element=20
title; if you go over the 'Level 1' part, you activate the a element=20
title.

I wonder if this is the correct way to conform to the WAI 1.0 Specs,=20
because the result could be confusing and misleading.

How will speech browsers render the title overlap? Is the quick=20
switch of the natural language (just for a single word in a span=20
element) compatible with current tools for people with disabilities?=20
Is it a good programming practice, apart from what specs recommend=20
(in abstract)?

>A design thing: Not to repeat the same links.

This is a problem I came across: I run a weblog (www.musimac.it -=20
another tableless site! :-P), and at the end of every news there's a=20
permanent link, i.e. an URL that stays valid even when the news goes=20
away from the home page and reaches the archive section. The text=20
link is always the same but the href value changes, because it is=20
generated dinamically:

<.a href=3D"<$PermaLink$>">Link</a>

WAI Guidelines say I should not use the same textual reference for=20
different URLs... but how can I accomplish this? Any advice?

>Not to use a meta refresh to the same page because the focus will move t=
o
>the top of the page and this problem can't be solved by most screen read=
ers.

If you can't use a meta refresh, what do you use instead?
--=20
Gabriele

HTML: hwg-business mailing list archives, maintained by Webmasters @ IWA