W3C home > Mailing lists > Public > public-wai-eo-site@w3.org > July 2005

[update on open issue] Re: WAI Site Redesign Prototype

From: Shawn Henry <shawn@w3.org>
Date: Mon, 04 Jul 2005 21:53:17 +0100
Message-ID: <42C9A1BD.20108@w3.org>
To: Vicente Luque Centeno <vlc@it.uc3m.es>
Cc: team-site-design@w3.org, WSTF <public-wai-eo-site@w3.org>

Dear Vicente,

Thank you again for your feedback! I still have your very helpful previous message on our open issues list.

A quick explanation: As you see, we don't use the list type visually at all - we hide them with the CSS. We use the different list types in order to help screen reader users to differentiate the list levels. If we put the list types in the CSS and a screen reader user interacts with the page without CSS, then they would not benefit from the different list types. That is the reason we have not yet moved the type attribute to CSS. However, we haven't yet addressed this issue fully. Hopefully we can come up with an acceptable solution.

Warm regards,
~ Shawn


Vicente Luque Centeno wrote:
> 
> Dear Shawn,
> 
> You are only one error left from becoming your page XHMTL 1.1 compliant. 
> Just moving the type attribute from list to CSS would do the trick.
> 
> Acording to:
> 
> http://validator.w3.org/check?uri=http%3A%2F%2Fwww.w3.org%2FWAI%2Fut3%2F&charset=%28detect+automatically%29&doctype=XHTML+1.1&verbose=1 
> 
> 
> <blockquote>
> Line 55, column 21: there is no attribute "type"
> 
> <ol id="nav1" type="A">
> 
> You have used the attribute named above in your document, but the 
> document type you are using does not support that attribute for this 
> element. This error is often caused by incorrect use of the "Strict" 
> document type with a document that uses frames (e.g. you must use the 
> "Transitional" document type to get the "target" attribute), or by using 
> vendor proprietary extensions such as "marginheight" (this is usually 
> fixed by using CSS to achieve the desired effect instead).
> 
> This error may also result if the element itself is not supported in the 
> document type you are using, as an undefined element will have no 
> supported attributes; in this case, see the element-undefined error 
> message for further information.
> 
> How to fix: check the spelling and case of the element and attribute, 
> (Remember XHTML is all lower-case) and/or check that they are both 
> allowed in the chosen document type, and/or use CSS instead of this 
> attribute.
> </blockquote>
> 
> You are also two more errors left from also becoming XHTML Basic, but I 
> am afraid they are not so easy and I also disagree with them to be 
> repaired.
> 
> Best regards.
> 
> Vicente Luque Centeno
> Dep. Ingeniería Telemática
> Universidad Carlos III de Madrid
> http://www.it.uc3m.es/vlc
Received on Monday, 4 July 2005 20:53:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:20 GMT