From: "Designer" <[EMAIL PROTECTED]>
I may be late to the party with this, but I think what they're
looking for would be:
<a href="LINK" title="Buy TITLE 1 now">Buy Now</a>
<a href="LINK" title="Buy TITLE 2 now">Buy Now</a>
<a href="LINK" title="Buy TITLE 3 now">Buy Now</a>
<a href="LINK" title="Buy TITLE 4 now">Buy Now</a>
<a href="LINK" title="Buy TITLE 5 now">Buy Now</a>
Andrew
Thanks Andrew - Simon put me on to this also, and it's EXACTLY what
the
validator is demanding.
There really is not an accessibility "validator" in the same sense as
there is an HTML or CSS validator. Accessibility is not black and
white. I believe your original code is fine:
<h1> EVERY STREET IN MANCHESTER </h1>
<a href="esim/btsa.html">About the book</a>
<a href="esim/btsa_pt2.html">What the critics say</a>
<h1> MANCHESTER KISS </h1>
<a href="mk/introduction.html">Introduction</a>
<a href="mk/introduction_pt2.html">What the author says</a>
<a href="mk/introduction_pt3.html">What the critics say</a>
An assistive reader, in the vast majority of cases, is not going to
machine-gun "What the critics say". It's going to read the headings,
then the content/links that come below.
This might be a case of overanalyzing things a bit. The goal is not to
satisfy a machine-based checker, but to provide a usable and
accessible page.
--
Al Sparber - PVII
http://www.projectseven.com
Extending Dreamweaver - Nav Systems | Galleries | Widgets
Authors: "42nd Street: Mastering the Art of CSS Design"
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
