Re: Accessibility - Standards was Re: Usage of 'lang' and 'title' attributes

Content Speech and braille readers have tables of words that if proceeded
by tag symbols ignore the word.  One of the reasons for CSS is to cut down
on the code in the tags.  That is why all my CSS is done in external style
sheets.  Then the tag usually doesn't contain much more than <.tag
class="xxx">  Easy and fast for the readers to ignore and produce readable
text.

I use a Mac, it has the innate ability to read any open page of text or
code built into the OS.  You ought to hear it read a page of HTML since it
does not have the exclusion tables that reader software has.

I had one site fully certified by Bobby for readers before CSS really
started up and the readers would read the code at the top of the page and
speak "For large text, braille and speech push S."  The page would switch
to a no graphic version of large text and simple link tags to cut the
clutter.  That was the first line on the top of my page under body.

As for multiple titles, Arghh.  Multiple language versions with a
javascript that reads the browsers language and switches the page would be
a sweet solution.

At 4:52 PM +0100 8/7/02, Nigel Peck wrote:
>I see :), I would "guess" (capital G on guess) that speach based
>browsers will read the titles as they get to each element, as for the
>language, I don't know how advanced the development of speach browsers
>is in that respect.
>
>I'm sure I've seen somewhere that you should not have two titles for
>one element in this way.
>
>Could be wrong though.
>
>Anyone else got any suggestions, perhaps someone with more knowledge in
>this field?
>
>HTH
>Nigel
>
>>>> Gabriele Caniglia <gabriele(at)sideralia.it> 08/07/02 03:22pm >>>
>On 7-08-2002 we were talking about "Usage of 'lang' and 'title'
>attributes".
>This is what Nigel Peck wrote:
>
>>I think it may be me that's missing something, but it sounds like
>it's
>>doing what you want, displaying the acronym title when over the
>acronym
>>(ignoring the outer title) and displaying the outer title when over
>>"level 1" which has no other title.
>
>Well, I wonder if this is the correct way to conform to the WAI 1.0
>Specs, because the result could be confusing and misleading...
>
>How will speech browsers render the title overlap? Is the quick
>switch of the natural language (just for a single word in a span
>element) compatible with current tools for people with disabilities?
>Is it a good programming practice, apart from what specs recommend
>(in abstract)?
>
>These were the questions behind my post, sorry if I didn't explain
>myself better before. :-)
>--
>Gabriele
>
>
>ITM Business Solutions
>Unit 4
>Nine Trees Trading Estate
>Morthen Road
>Rotherham
>S66 9JG
>
>Reception
>Tel: 01709 703288
>Fax: 01709 701549
>
>Help Desk
>Tel:01709 530424
>Fax: 01709 702159
>
>CONFIDENTIALITY NOTICE: This message is intended only for the use of
>the individual or entity to which it is addressed, and may contain
>information that is privileged, confidential and exempt from disclosure
>under applicable law.

-- 
Sincerely,
Kid Stevens

"Communication in one direction is just a lecture,  a telling of words,
a one way street, true communication is a two way street with
a speaker and a respondent at each end"
-Kid Stevens

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA