public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "A. R. Vener" <salt@aero-vision.com>
To: blinux-list@redhat.com
Subject: Re: What's Wrong With This Page?
Date: Tue, 1 Oct 2002 09:55:05 -0400	[thread overview]
Message-ID: <20021001095505.A15048@cougar.aero-vision.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210010816240.15711-100000@Jumbo>; from director@chpi.org on Tue, Oct 01, 2002 at 08:22:44AM -0500

Nothing is wrong with the page. In lynx i followd
the Introduction link  and was taken to  the introduction page. However it is
also true that lynx placed my cursor on the post  link you mentioned and
my screen reader read that link.  I had to refresh the screen
to hear the text of the introduction.

rudy

On Tue, Oct 01, 2002 at 08:22:44AM -0500, John J. Boyer wrote:
> Hello,
> One of the pages on my Web site works with EI but not with Lynx. Please 
> tell me what the problem is with http://www.chpi.org/gbuserref.html . The 
> first link on the page skips the table of contents and goes to the 
> Introduction on the same page. Or rather, that's what it's supposed to do. 
> Instead, it skips to "post to gnomebrl". I've tried putting the target 
> link inside the header, including the header after the URL, etc. Lynx 
> always behaves the same. I've used Lynx or other pages with a similar 
> arrangement, and it works. What's wrong with this one?
> John
>  
> 
> -- 
> Computers to Help People, Inc.
> http://www.chpi.org
> 825 East Johnson; Madison, WI 53703
> 
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list




  parent reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John J. Boyer
 ` Cheryl Homiak
   ` Cheryl Homiak
 ` Dave Mielke
 ` Mario Lang
   ` John J. Boyer
 ` A. R. Vener [this message]
 ` Lyta Alexander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021001095505.A15048@cougar.aero-vision.com \
    --to=salt@aero-vision.com \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).