W3C home > Mailing lists > Public > public-wai-eo-badtf@w3.org > November 2008

Re: Cleaned up template

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Mon, 24 Nov 2008 22:20:55 +0100
Message-ID: <492B1AB7.10502@w3.org>
To: Eric Eggert <w3c@yatil.de>
CC: public-wai-eo-badtf@w3.org

Hi Eric,

Thank you for working on an improved CSS! Here some responses to your 
questions as background for any discussion:

1. sidebar images - the idea was to show different types of solutions 
for decorative images. We wanted to show that one of the solutions is 
that decorative images could be placed in the CSS. Having said that, we 
could continue to show this possibility on list items and bullets as we 
do on the "home page" but not for the sidebar images.

2. <a> with @name - note the </a>'s left over on lines 26 and 92.

3. access keys - we wanted to show that *if* you use access keys, then 
this could be considered best practice. It does somewhat make sense to 
use access keys on the demo as there is always a repetitive navigation 
block (and sometimes a warning) on each of the pages. We could consider 
reducing them though if people feel they are overboard.

4. separate CSS - I think this would very useful to do.


Thomas Jewett wrote:
> Thanks, Eric -- I feel better -- I didn't understand
> the sidebar, either. I agree that simpler is better.
> I'm one of those with a strong opinion about @accesskey:
> I've stopped using them, so that I won't make conflicts
> with anything the user has set up. I've also been hearing
> this from folks who are much better with voice readers
> than I am.
> Tom
> On Sun, 23 Nov 2008 22:23:07 +0100
>  Eric Eggert <w3c@yatil.de> wrote:
>> Hey there.
>> Here are my efforts for cleaning up the after HTML and CSS until now.
>> http://ericeggert.net/whosbad/template.html
>> http://ericeggert.net/whosbad/main.css
>> Some issues here which should be clarified before proceeding:
>> 1) The sidebar template is weird. I canít follow the decision to use  
>> background images there, this makes no sense at all to me and should  
>> probably be resolved in ordinary img elements.
>> 2) Iíve expelled all instances of a elements with @name and instead  
>> used @id.
>> 3) Do we really need the @accesskeys for the actual website template?  
>> I wouldnít use them, but I know there are some strong opinions about  
>> those so I left them in for now.
>> 4) I will apply a namespace to the meta navigation and copyright  
>> notice so that itís easier to distinguish between core template css  
>> and those meta information and get them into a separate stylesheet.
>> Comments?
>> Eric

Shadi Abou-Zahra - http://www.w3.org/People/shadi/ |
   WAI International Program Office Activity Lead   |
  W3C Evaluation & Repair Tools Working Group Chair |
Received on Monday, 24 November 2008 21:25:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:50 UTC