Hi James,
As the page http://www.organicexpo.com.au/exhibitors/index.php validates as
XHTML 1.0 Strict, this may not mean anything but I have had errors or
warnings from validators about white space in html comments in the past.
<!--comment--> wasn't acceptable as there needed to be a space either inside
the delimiters (--) as in
<!-- comment -->. Seems this has been changed in the specs, or at least the
validators. I would still suggest doing it that way anyway. This also means
that ColdFusion comments <!--- comment ---> should not really be used on
pages that are not parsed by ColdFusion (removing them from the source).
The links without hrefs in the footer are inaccessible.
<a onclick="javascript:newWindow('../articles/terms.php')">terms and
conditions</a>
Without JavaScript (many smartphones etc. simply don't have it), this won't
work and they can't read your terms. A potential legal issue. The code we
use (in HTML and only when we really need to) is:
<a href="page.htm" target="targetname" onClick="window.open('',
'targetname','toolbar=0,location=0,directories=0,status=0,menubar=0,scrollba
rs=auto,resizable=0,width=310,height=300')" title="Link text (opens in a new
window)">Link text</a>
This is very stable code that works everywhere.
So, either don't use XHTML if you want accessible links to popup windows
(due to the lack of the target attribute) or don't use popup windows at all,
loading the terms and conditions and privacy policy in the full window. The
latter is obviously preferable as people using screen readers without the
aid of vision may not know the new window has opened and get completely lost
on a page with no navigation aids.
Just my thoughts...
P
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
