[Zope3-dev] Re: Bug 358/359, 367 fixed

[Tonico Strasser]

Tonico wrote:
>>I'm rather optimistic that we can make one full featured skin that 
>>degrades in older browsers. The only things I can think of 
>>that wouldn't 
>>degrade are wild JavaScripts, but that wouldn't be WCAG level A[1] 
>>conform and difficult to support because we would need to account for 
>>more browser bugs additional to the rendering bugs. Some 
>>features like 
>>the XML HTTP request aren't even standardized.
>>
>>[1]http://www.w3.org/TR/WAI-WEBCONTENT/#Conformance

Roger Ineichen wrote:
> This sounds Ok for me. We can first make the CSS skin (zope.app.css)
> fit the standards. Later we can see if we should use this skin as the ZMI
> skin.
> 
> Let's use the 'WCAG level A[1]' as the standard in the 
> CSS skin '++skin++CSS' in the package zope.app.css.

Fine.

> We can use the cookie based tree in this skin and see if this
> tree fit's to the standards.
> 
> Any other parts we have to refactor where the Rotterdam skin doesn't fit? 

Don't know, we'll see.

There is an useful browser extension for accessibility evaluation (and 
more):
<http://checky.sourceforge.net/extension.html>

Tonico