RE: type attribute (Re: Site Maps and nested navigation)

Many thanks for the replies everyone. It looks like navigation continues to be a difficult issue. It seems to me that the long term issue lies with the middleware producers recognising how lists are being used in navigation. In the meantime it would seem best to avoid dropdowns, nested navigation etc. where possible because of the user burden. 

Moving on a little - whats the beef with XHTML? I thought it was recommended?

Cheers

Stu

-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf Of Elizabeth J. Pyatt
Sent: 07 December 2005 14:31
To: David Dorward
Cc: w3c-wai-ig@w3.org
Subject: Re: type attribute (Re: Site Maps and nested navigation)


Sorry for misusing the word "tag", but I trust most knew which attribute I was referring to. ;)

Elizabeth

>On Wed, Dec 07, 2005 at 08:53:05AM -0500, Elizabeth J. Pyatt wrote:
>
>>  As far as using lists go, I actually use HTML (vs. XHTML) because I  
>> feel  that when XHTML  got rid of the TYPE= tag, it opened up the  
>> door for potential accessibility issue.
>
>Not that I want to encourage the use of XHTML, but the type 
>attribute[1], was deprecated and relegated to the Transitional Doctypes 
>in HTML 4, and remained in the Transitional doctype of XHTML 1.0 (which 
>is a silly language to use on the WWW), and lets not bother talking 
>about XHTML 1.1 (which is an insane language to use on the WWW).
>
>
>[1] Not a tag. Its an attribute.
>
>--
>David Dorward                                      http://dorward.me.uk


--
=-=-=-=-=-=-=-=-=-=-=-=-=
Elizabeth J. Pyatt, Ph.D.
Instructional Designer
Education Technology Services, TLT/ITS
Penn State University
ejp10@psu.edu, (814) 865-0805 or (814) 865-2030 (Main Office)

210 Rider Building II
227 W. Beaver Avenue
State College, PA   16801-4819
http://www.personal.psu.edu/ejp10/psu
http://tlt.psu.edu

Received on Wednesday, 7 December 2005 15:21:07 UTC