RE: Fw: Disturbing trend in tables

I think we have gotten off track a bit.  Whether it is smart, correct,
appropriate, or whatever to place P tags in a TD is moot isn't it?

What I'm seeing is people saying Jaws needs to modify their program to
accommodate this code.  That is called passing the buck.  As developers, we
must work within the boundaries set by Jaws and other tools like them since
it is our product that must be accessible.  Theirs is the working end of it
all.  If Jaws cannot read P tags in TD's then we are compelled to not place
P tags in TD's.  We should never knowingly write our code to a point where
we know Jaws will fail.  It is up to us to write accessible documents and we
should not lose focus of that.  If and when Jaws interprets P's inside of
TD's correctly, then we can begin doing that.  But, until then it is a known
issue and we avoid using them.

Jim Fitzgerald

-----Original Message-----
From: Frank Tobin []
Sent: Wednesday, January 10, 2001 12:49 PM
To: Tina Marie Holmboe
Cc: wai-ig list
Subject: Re: Fw: Disturbing trend in tables

Tina Marie Holmboe, at 16:10 +0100 on Wed, 10 Jan 2001, wrote:

    I believe you are seeing the results of - yet another - hack to
    achieve a visual layout. From the above I would make a guess that
    they are trying to get extra space on top of the cell, and - as we
    all know - a <P> 'makes' extra space.

Personally, I don't quite see what the problem is.  First, it's perfectly
valid xhtml to have paragraphs inside of a td.  Second, what if there are
semantically two paragraphs in side the td?  How would you propose
distuinguishing them if without <p>?

Frank Tobin

Received on Wednesday, 10 January 2001 13:04:05 UTC