As mentioned Tables are the correct thing to use for tabular data (and forms)
this is not the argument.
However for Accessibility purposes
<div id="container">
<div id="header">Document header</div>
<div id="Nav">navigation system</div>
<div id="Content">document content, including tables etc</div>
</div>
is better than
<table>
<tr>
<td>Document header</td>
</tr>
<tr>
<td>Navigation system probably using a sub table</td>
<td>Document content, including tables etc</td>
</tr>
</table>
Why? Well nested tables can cause your website to load slower, Nested tables
can be as confusing as Div's/CSS anyway, Screen readers and some less widely
supported browsers do not handle tables for layout as gracefully as IE/Moz,
Tables tend to resize less gracefully than well written CSS. There are other
reasons but it is clear that the standards for accessibility are not the same
as the standards for XHTML
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Scott
Barnes
Sent: Friday, 13 May 2005 4:31 PM
To: CFAussie Mailing List
Subject: [cfaussie] Re: OT: [best practice or your practice] CSS vs.
Tables
without getting into a pi$$ing contest but..
> I'm not sure 'neglected' is the right word here. XHTML includes a
> tables module, this is true. It also specifies that the tables module
> provides elements for marking up tabular data (see eg.
> http://www.w3.org/TR/2004/WD-xhtml2-20040722/mod-tables.html). So no,
> you are definitely not breaking the rules by including a table in your
> document. By using that table for the layout of non-tabular data you
> most certainly are not complying with (at least) the spirit of the XHTML
> specification.
Well yes and no, lets take a step back and accept that if were were
going to use the DIV approach vs TABLE in regards to CSS Properties
your code would go from this:
<table>
<tr>
<td>data1</td>
</tr>
</table>
to
<div id="semanticallycorrect_wrapper_identification" class="tbl">
<div class="row">
<div class="cell">
</div>
</div>
-OR-
<employees>
<employee>
<name>data1</name>
</employee>
</employees>
The spirit of XHTML for me was to basically bring chaos to order in
terms of marking up HTML to something that is "semantically" correct
in its approach. Making machines understand a language instead of
taking queus from visual meanings (ie <b> vs <strong> debates etc).
> It's not Ford vs. Holden, it's Ford vs. Boeing. Which one provides the
> vehicle appropriate for the task at hand?
I fail to see that analogy ;) hehe.
--
Regards,
Scott Barnes
http://www.mossyblog.com
http://www.flexcoder.com (Coming Soon)
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
Please Note:
This communication has been sent on behalf of The Royal Automobile Club of
Queensland Limited (RACQ). The information contained in this communication
may be privileged and confidential. If you are not the intended recipient,
any use, disclosure or copying of this communication is expressly
prohibited. If you have received this communication in error, please delete
it immediately. RACQ and its associated entities do not warrant or
represent that this communication (including any enclosed files) is free
from electronic viruses, faults or defects.
If this is a commercial electronic message within the meaning of the Spam
Act(2003), you may indicate that you do not wish to receive any further
commercial electronic messages from RACQ by sending an e-mail to
[EMAIL PROTECTED] with your details or by contacting RACQ on 131905
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
