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

Re: Betr.: Re: Wireframe for Demo-Pages

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Tue, 11 Nov 2008 18:02:44 +0100
Message-ID: <4919BAB4.8050407@w3.org>
To: Michael Stenitzer <stenitzer@wienfluss.net>, Jan Sjoerd Poorta <js.poorta@bartimeus.nl>
CC: public-wai-eo-badtf@w3.org

This leads me to the idea of an annotate function rather than annotated 
pages: when you toggle the annotation mode the inaccessible pages show 
the barriers inline and the accessible pages show the solutions.

This is however more work. Do people think that it would be worth the 
effort? I personally think it would be a very useful function to meet 
the needs of many different audiences.

Best,
   Shadi


Michael Stenitzer wrote:
> 
> Jan Sjoerd Poorta wrote:
>> Yes, nice indeed. One question though: Assuming that the Annotated
>> Accessible Version corresponds to the in-between pages, I had
>> understood that the idea was that the basis for an in-between page
>> would be the before-page, i.e. the Inaccessible Version. Michael, do
>> you prefer to have in-between pages based on the accessible (after)
>> pages? 
> 
> i would prefer to have annotated solutions than annoted problem.
> i.e. a annoated accessible version.
> but maybe even both.
> 
> /michael
> 
> 
>> Jan-Sjoerd
>>
>>
>> Stichting Bartiméus Accessibility Expertisecentrum software- en
>> internettoegankelijkheid
>>
>> Oudenoord 325 3513 EP  Utrecht  (The Netherlands) Tel: +31 (0) 30 -
>> 239 8270  |  Fax: +31 (0) 30 -  239 8239 js.poorta@bartimeus.nl
>>
>> www.accessibility.nl
>>
>> Disclaimer: www.accessibility.nl/algemeen/disclaimer
>>>>> Shadi Abou-Zahra <shadi@w3.org> 11-11-08 9:37 >>>
>>
>> Really nice! Especially that it provides different ways of navigating
>>  the Demo and a more integrated approach to the "educational
>> aspects".
>>
>> Let's discuss tomorrow.
>>
>> Best, Shadi
>>
>>
>> Michael Stenitzer wrote:
>>> hi all,
>>>
>>> i've put together a simple wireframe how i would propose to embed
>>> the demopages in a navigable set of pages:
>>>
>>> http://www.wienfluss.net/BAD/BAD.png
>>>
>>> here the outline of my considerations in text (AKA longdesc):
>>>
>>> * use an easy to understand and non-technical, non-insider speak
>>> title and subtitle.
>>>
>>> * provide a clear representation of the three different flavours
>>> each page is available with a tab navigation: - inaccessible
>>> version, - annotated accessible version, - accessible version. 
>>> (implementation note: the tabs are normal links, no javascript, no
>>> ajax, no witch-art. Annotate the selected tab with some hidden
>>> text, we might use ARIA too).
>>>
>>> * provide a simple navigation between the demo-pages. this might be
>>> in the form of previous / next page links or by listing and linking
>>> all four demo pages.
>>>
>>> * meta-navigation: providing links to background information (about
>>>  demo, description of all barriers, evaluation report).
>>>
>>> * footer: leave more or less like it is now (not in the wireframe).
>>>
>>>
>>> any thoughts, ideas?
>>>
>>> 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 Tuesday, 11 November 2008 17:03:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 November 2008 17:03:20 GMT