W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2000

RE: wording of Checkpoint 7.5

From: Gregory J. Rosmaita <unagi69@concentric.net>
Date: Fri, 07 Jan 2000 13:55:51 -0500
Message-Id: <4.1.20000107115322.00b21c60@pop3.concentric.net>
To: "Denis Anson" <danson@miseri.edu>
Cc: User Agent Guidelines Emailing List <w3c-wai-ua@w3.org>
aloha, denis!

i think that this question has already been at least partially addressed...

one of my configuration checkpoints for link rendering slash exposition,
originally contained in the post archived at:

and contained in the current Techniques document -- under the Techniques listed
for checkpoint 8.3 (which i _still_ think is accorded far too low a priority),
and more fully under Accessibility Topic 3.3 "Link Techniques"
includes the option to list (or render) links by "title" (if present)

but i, unlike jon and dick, would strongly advocate that such an option be
available via the search feature of quote mainstream unquote UAs, especially if
users are to escape the quote click here unquote trap...

why?  many sighted colleagues, upon viewing JFW's list of links feature working
in MSIE have turned audibly green with envy when they see how well JFW handles
the list of links it generates, compared with the list of links that is
available from MS as a PowerTweak slash PowerToy -- quote i wish i could get as
robust a navigational mechanism as that, 'cause there are way too many links on
this page to eyeball efficiently unquote is something i often hear when working
with a sighted colleague...

the only thing missing from the JFW list of links feature is the ability to
toggle between "display links using hyperlink text" and "display links using
TITLE (if present)"

actually, by default, when reading the contents of a document from beginning to
end (or when moving from link to link) JFW speaks the TITLE, if present, which
can be quite disconcerting when listening to a page in toto...


At 09:25 AM 1/7/00 -0500, you wrote:
>I'd like to see the wording expanded to include things like the title
>attribute and summary attribute for tables, which are not, in fact, rendered
>under "normal" situations.  Titles can be rendered when they are pointed to,
>and summaries are not rendered at all, but I sure would want to be able to
>search on them!
>How would you find information stored in a title if you can't search on it?
>Just point to everything on the page, and hope it pops up some where?
>-----Original Message-----
>From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org]On
>Behalf Of Gregory J. Rosmaita
>Sent: Thursday, January 06, 2000 5:48 PM
>To: Jon Gunderson
>Cc: User Agent Guidelines Emailing List
>Subject: Re: wording of Checkpoint 7.5
>jon suggested:
>Checkpoint 7.5 Allow the user to search for rendered text content, including
>text equivalents rendered in place of or simultaneously with the primary
>hmm...  short, concise, and to the point...  i like it...
>and, as ian suggested, if the verbiage contained in my proposed note isn't
>already in the techniques document, it should be added to the techniques and
>not the UAGL itself...

He that lives on Hope, dies farting
     -- Benjamin Franklin, Poor Richard's Almanack, 1763
Gregory J. Rosmaita <unagi69@concentric.net>
   WebMaster and Minister of Propaganda, VICUG NYC
Received on Friday, 7 January 2000 13:47:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:25 UTC