W3C home > Mailing lists > Public > public-wai-eo-badtf@w3.org > October 2009

Re: Summary from today's EOWG discussion

From: Thomas Jewett <jewett@csulb.edu>
Date: Sat, 03 Oct 2009 21:02:44 -0700
To: Eric Eggert <w3c@yatil.de>,BAD TF <public-wai-eo-badtf@w3.org>
Message-ID: <web-26977179@remus.csulb.edu>

I believe that Eric has raised some important issues.
We've all been placed in a very difficult position;
unfortunately, I can't think of any inventive ways to
resolve it.


On Fri, 2 Oct 2009 20:20:42 +0200
  Eric Eggert <w3c@yatil.de> wrote:
> Hi Shadi, Group.
>First: I really appreciate all feedback we get, and some 
>points are
> valid (as I will show below), but this group was 
>scheduled until
> December 2008 and is now in its second year. There are 
>people writing
> whole specs in that time.
> We archived a lot, and a lot more then we were asked to 
>do, and the
> group works great together, but most of those 
>suggestions shouldn’t be
> presented to us a month prior to finish but a month 
>after start.
>> # Page design and navigation
>>  - evaluation pages should be in the BAD design (not the 
>>WAI design)
> We don’t have something like that. I said that before. 
>When we
> developed the Navigation it was singled out. Everything 
>we do now with
> the overview pages will result in pages that will look 
>out of place
> anyway.
>>  - make a "show/hide report" button (like "show/hide 
> Totally wrong as the report will not be shown inline, so 
>it isn’t
> shown, it is just linked to. We discussed that already…
>>  - add W3C/WAI branding to all Demo pages (logos on 
>>top-left side)
> Which logos exactly. Why didn’t we know about that 
>requirement earlier?
>>  - reflect the current location in the <h1>
> This was planned anyway, if I recall directly
>> and in the page title [1]
> We do that.
>> # Evaluation report
>>  - for consideration/editors discretion:
>>  -- remove indentation (for SC and Techs) in the 
>>description column
>>  -- add indentation before the GL/SC numbers in the "#" 
> Would that really add any benefit? I don’t think it 
>>  -- n/a should be in lower case and grayed (to be easier 
>>to skim)
> “Easier to skim” is subjective, isn’t it? I don’t think 
> necessary, but it won’t hurt.
>>  -- use progressive color shading to better indicate the 
>>levels [2]
> Don’t think we need that. Colors are too bold in Liams 
>example for my taste…
>> [1] consider imitating a browser chrome in the Demo 
>>area, to show the "Page
>> Titled" accessibility requirement between before/after 
> No, we don’t need this. (I don’t think I have to say 
>that this will
> confuse people, then you get into the problem which 
>operating system
> to mimic. And it is a code demo, so we shouldn’t 
>introduce even more
> elements that have nothing to do with the demo all 
>together. Currently
> I’m even thinking we should remove everything that is 
>not the actual
> demo – heading, footers, annotations – as it really, 
>really seem to
> confuse people. We will not please everybody.)
> Regards,
> Eric
> -- 
> Eric Eggert
> Waldfischbacher Straße 20, 66978 Leimen/Pfalz, 
> Laudongasse 36/714, 1080 Wien, Österreich
> http://yatil.de/ | http://snookerblog.de/
Received on Sunday, 4 October 2009 04:03:13 UTC

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