BLIND-DEV Archives

Development of Adaptive Hardware & Software for the Blind/VI

BLIND-DEV@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Kelly Ford <[log in to unmask]>
Reply To:
BLIND-DEV: Development of Adaptive Hardware & Software for the Blind/VI" <[log in to unmask]>
Date:
Wed, 18 Jun 1997 16:59:46 -0700
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (27 lines)
Greetings,


On Wed, 18 Jun 1997, Al Gilman wrote:

> The example that Daniel was locked up on is the "no two links on
> one line" rule because this is a problem for people using Lynx
> and a DOS screenreader, but not for people using pwWebSpeak.

Roughly 75 percent of my browsing time is spent with Lynx and a DOS screen
reader.  I've never found multiple links on a single line to be a problem.
I think this is especially true given the fact that Lynx can number all
linkss.

> On Lynx-dev a while back while discussion how to represent images
> for which the page author has not provided a fluent ALT text, a
> good point was made by one site author that he uses ALT=""
> carefully to hide the presence of images that can be skipped
> without breaking the message.  Dragging the audio user through
> all of these is not necessarily a service.

This might be another suggestion to include and seems like a good idea.
But I'd still rather know about a link be default.  I'd assume, as
dangerous as it might be, that a page designer careful enough to tag
unimportant images with alt="" would do a good job of making a page
accessible.

ATOM RSS1 RSS2