- From: Lisa Herrod <lisaherrod@gmail.com>
- Date: Mon, 7 May 2012 07:05:04 +1000
- To: Sharron Rush <srush@knowbility.org>
- Cc: "public-wai-engage@w3.org" <public-wai-engage@w3.org>
- Message-Id: <EE503065-0CA4-46F7-B622-76C566179C2A@gmail.com>
Hi All, In addition to my previous email, I don't think either of the suggested examples are ideal. I'd like to suggest the 'Analysis' layout, however, categorised by conformance level rather than POUR. In practice, web practitioners want to know: A: which guidelines apply to my work; and B: which guidelines do I need to satisfy to meet A or AA etc. In my experience, web practitioners aren't really thinking about POUR on a day to day basis. Regards Lisa On 06/05/2012, at 11:23 PM, Sharron Rush <srush@knowbility.org> wrote: > Greetings all, > > We at Knowbility have volunteered to help Denis reorganize the tables within the Accessibility Responsibility Breakdown (ARB) project that he is contributing to the WAI-Engage wiki. Denis has gotten feedback to use the POUR principles as the organizing theme rather that the conformance Levels. As we rebuild the tables, the question has arisen of how much information to put in the sections. > > Please compare the two tables: > > Analysis http://www.w3.org/community/wai-engage/wiki/Accessibility_Responsibility_Breakdown#Analysis > and > Architecture http://www.w3.org/community/wai-engage/wiki/Accessibility_Responsibility_Breakdown#Architecture > > Then answer the question of which presentation is preferable. Is it useful to use the short descriptions of each guideline as a contextual reference as in the Analysis table > -OR - > or does it just add visual clutter and is it sufficient to link from the number and allow context when users follow the link? > > My opinion is that the tables will be very helpful and we would like to make them as usable as possible, so you input is much appreciated. Thanks for your ideas. > > Best, > Sharron
Received on Monday, 7 May 2012 12:29:51 UTC