W3C home > Mailing lists > Public > wai-eo-editors@w3.org > October 2010

Re: Use of progressive disclosure in "How People with Disabilities Use the Web"

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Fri, 29 Oct 2010 09:04:03 +0200
Message-ID: <4CCA71E3.6060806@w3.org>
To: Michael Stenitzer <stenitzer@wienfluss.net>
CC: wai-eo-editors@w3.org
Hi Michael,

Thank you for your feedback!

As discussed, we will be looking at the implementation and the use of 
the expand/collapse functionality more closely.

The print comment is particularly useful at this stage since we will 
discuss ideas for WAI website redesign during the upcoming f2f.

PS: sorry to hear about your colleague leave and good luck to him.


On 28.10.2010 23:32, Michael Stenitzer wrote:
> Dear editors,
> As discussed earlier with Shadi i submit my comments / thoughts on the
> use of progressive disclosure on pages like "How People with
> Disabilities Use the Web".
> Generally I think progressive disclosure (PD) is a very valuable
> technique to make pages and applications more usable and scanable.
> People can focus on the parts or tasks they are interested in.
> But I'm not sure if we could improve the PWD-Use-Web-pages ...
> Will our readers be interested more in certain sections or in reading
> the core-content of a page in general? I think - compared to the
> WCAG-guidelines where one is probably more often than not interested in
> just a certain piece of information - people might want to read through
> those pages, at least to get a general impression of the topic.
> Generally I think the initially visible content should be a balanced and
> informative document, not just one sentence of introduction and a number
> of headlines.
> But PD might of course be of value on these pages as well.
> eg:
> http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/scenarios
> Here I would collapse just the further-reading sections (Related
> sections within this resource)
> http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/disabilities
> On this page it might be sensible to collapse the sections
> - Examples of * disabilities
> - Examples of web accessibility barriers
> - Related sections within this resource
> By collapsing those parts we have left an initially opened content which
> gives us a very informative and well readable article.
> http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/provisions
> Again i would just collapse those further reading sections:
> - Related technical specifications
> - Related sections within this resource
> http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/browsing
> On this page one can argue about collapsing or expanding the examples.
> Definitly i would collapse "Related sections within this resource".
> If we keep the current form of presentation with a collapsing of nearly
> all content we should discuss the behaviour of printing. In this case I
> think it would be more appropriate to print the whole page. Or we
> provide printing links: [print visible] | [print all]
> Finally a note for Shadi: unfortunatly our javascript wiz will not be
> able to help you because he will leave us and move to Berlin as he told
> me today ;(
> If you want to discuss those comments feel free to contact me.
> Regards, michael

Shadi Abou-Zahra - http://www.w3.org/People/shadi/ |
   WAI International Program Office Activity Lead   |
  W3C Evaluation & Repair Tools Working Group Chair |
Received on Friday, 29 October 2010 07:04:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:25:21 UTC