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

A simple solution would be four versions for each page:

1. Inaccessible
2. Inaccessible with icons/markup
3. Accessible with icons/markup
4. Accessible

We could reuse the same code for the icons and markup but once we show 
the barriers and once the repairs. Much of this information is already 
in the evaluation report too.

The navigation could continue working with plain links (the "toggle" 
would actually be only a link) without any "javascript, ajax, or 
witch-art"... :)

Best,
   Shadi


Michael Stenitzer wrote:
> Shadi Abou-Zahra wrote:
>>
>> 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.
>>
> 
> i think this might be an interesting option. i considered it earlier but 
> it needs definitely a more advanced solution to make it accessible.
> 
> i try to think about requirements, constraints and solutions. hopefully 
> before tomorrows meeting.
> 
> cheers, michael
> 
>>
>> 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 21:34:16 UTC