- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Thu, 03 Sep 2009 14:05:54 +0200
- To: BAD TF <public-wai-eo-badtf@w3.org>
-------- Original Message -------- Subject: Betr.: Another Idea of presenting the report Date: Thu, 03 Sep 2009 13:41:33 +0200 From: Wilco Fiers <wfiers@bartimeus.nl> To: <public-wai-eo-badtf@w3.org>, <shadi@w3.org> Hi Eric We've had the discussion both on the use of color, the positioning of navigation controls and the seperation of tables before. I was under the impression that these issues had been decided on, so I am somewhat surprised you want to reopen them. I like the neutral approach you've taken in your example. It's reduces the amount of information the eye would need to process. However I feel that your design is a bit short on visual cues. The only way to tell the different levels appart here is either by indentation or by actually starting to read (which makes scanning difficult). And the indentation here works alright, however the WAI site this is going to be published on is rather narrow so you might even be forced to reduce that. The font you've chosen for this table is very easy to read. I've not gotten around to that myself yet so I'll have to see if it works as well for the final design. I take it you designed this as an example? I would like to add that jQuery relies rather heavilly on innerHTML, which does not work well with screenreaders and isn't permitted in WCAG 2. So I do not think we should be using it. Adding multiple tables to display the same set of data is in my oppinion not a good idea. It makes navigating through the report easier if you are looking for a specific result but if your goal is to get an overview of the evaluation this is probably more difficult. Thanks for the example though. I will have a new version of the table ready by next week. Wilco >>> Eric Eggert <w3c@yatil.de> 02-09-09 17:08 >>> Dear BAD Taskforce, as I mentioned in previous phone calls, the report format were currently discussing is too colourful to me, additionally i found it quite hard to read (although this might be resolved in future updates). To add some constructive criticism to my argument, Ive created the following mockup: http://bad.ericeggert.net/report/ What did I do? - Rather than trying to tie all four principles into one table, Ive reduced complexity and split them up into four (actually Im only displaying one of the four tables). - I use clear and distinct headings for the Principles. This should allow for better scanning and should help screen readers also as we cannot indicate hierarchy in table rows semantically (only visually and in descriptive text. - I moved the show contents control to the left and used the metaphor Im used to from mac os, which feels okay for me although the sub points feel a little bit flat. this could be improved visually. - I did leave out icons for a reason: they are often unclear and dont add anything to the already color coded table cells. - I merged the cell for the guideline number and title to show their close relationship. So, what do you think? Regards, Eric (Actually that should have been sent out a week ago, but I used the wrong email. Sorry!) -- Eric Eggert Waldfischbacher Straße 20, 66978 Leimen/Pfalz, Deutschland Laudongasse 36/714, 1080 Wien, Österreich http://yatil.de/ | http://snookerblog.de/ -- Shadi Abou-Zahra - http://www.w3.org/People/shadi/ | WAI International Program Office Activity Lead | W3C Evaluation & Repair Tools Working Group Chair |
Received on Thursday, 3 September 2009 12:06:29 UTC