W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2001

feedback sought:Fw: Accessibility and Lynx browser query

From: David Poehlman <poehlman1@home.com>
Date: Wed, 6 Jun 2001 09:15:31 -0400
Message-ID: <009401c0ee8a$c3875e20$2cf60141@mtgmry1.md.home.com>
To: "wai-ig list" <w3c-wai-ig@w3.org>
please either email the original sender directly or cc the sender on
From: Kath Moonan Kath.Moonan@poptel.net
Newsgroups: alt.comp.blind-users

Dear Newsgroup!

This is a query about accessibility and Lynx browsers, I would be
grateful anyone could give us any advice or opinions on any of the
problems we've encountered.

I work for a co-operative ISP and web design company, www.poptel.net we
been developing a number of sites that either conform to Priority 1 or
3 of
the WAI.

During discussions with the RNIB in the UK, they advised us that many
visually impaired users use Lynx, so we downloaded it to test our sites
As a result of this we have identified potential conflicts listed

Our opinion is that we should follow the W3C standards rather than
trying to
make the page display correctly in one particular platform or browser.

However our goal is to makeour pages accessible - we'd be really
grateful of
a second opinion on these issues as we feel apprehensive about the
we are using. In short is it more important that the site works in Lynx
it strictly follows the standards?

What is your opinion on the issues listed below, should we follow the
accessibility guidelines or design specifically to one browser or

Potential Conflicts between Lynx and WAI Priority 3 standards:

Access Keys
As Lynx already has access keys, will assigning access keys to a page
potential conflicts?

The title attribute of a href, for example, doesn't seem to do anything
Lynx? Is it required in Lynx - and which browsers is it recognised in?

We have been developing a method of working that included using
images as anchor links within the page so that visually impaired users
easily bypass navigation and go straight to the content of a page.

As the user can use built in keys in Lynx to move around the page we
again concerned about potential conflicts.

Spacer Images
We have been following the RNIBs advice on spacer images and using * as
alt tag. However it appears that the page is easier to read in Lynx if
alt tag is left blank for spacer images, which method should we use?

HTTPS and Secure Sockets
We have been developing a online donation product which we have
to make accessible to Priority 1. When we came to test the site we
that we couldn't open it in Lynx.

I'd be really grateful for any advice or opinions people have on these

Many Thanks in advance

Kath Moonan

Received on Wednesday, 6 June 2001 09:15:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:13 UTC