Re: Web accessibility enhancement scripts

Hi, 

I'm still a little unclear.  

Is it not the case that by using what the W3C term "accessibility-supported technologies" (like JavaScript) [WCAG 2.0 Understanding Conformance document http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance] a legitimate conformance claim could be made via a technique such as G136: Providing a link at the beginning of a nonconforming Web page that points to a conforming alternate version http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/G136.html.

Best regards

Alistair  

On 21 Nov 2011, at 17:07, Samuel Sirois wrote:

> Hi,
> 
> In my opinion, both basic and enhanced experiences should be accessible.
> 
> A basic experience should be offered in order to make sure that if a
> user agent does not support (or has deactivate) JavaScript or
> style-sheets, the user is still able to access the published
> information.
> 
> An enhanced version of the same data should also be accessible to
> everyone, but should provide a more usable (regarding widgets an
> asynchronous data load) experience. Enhancing is not a question of
> accessibility, it's a question of technology support by the user-agent.
> 
> I do not believe in having a link that provide a copy of the information
> for a particular subset of users. We all know that the copy of the data
> may not be updated as often as the "mainstream" data.
> 
> Because I believe in inclusion and universal accessibility, I would
> evaluate the basic experience as the enhanced experience in order to
> make sure that if one or the other is loaded for a user, the user is
> still in front of an accessible page.
> 
> Regards,
> 
> Sam
> 
> On Mon, 2011-11-21 at 15:51 +0100, Alistair Garrison wrote:
>> Hi Denis, 
>> 
>> I agree... I would, however, ask for your judgement in terms of the "screen-reader users, click here to turn off google instant" found at the top of Google’s search page - would you evaluate the page before the script is executed by a user or after the script is executed by a user?
>> 
>> All the best
>> 
>> Alistair    
>> 
>> On 21 Nov 2011, at 14:41, Denis Boudreau wrote:
>> 
>>> Hello Alistair,
>>> 
>>> If you're talking about any type of AJAX enhancement scripts added to a page, I don't think there's any need to be evaluation work done _before_ the scripts are loaded.
>>> 
>>> As long as the scripts in question work / are compatible with assistive technologies and are keyboard user friendly, they shouldn't be a concern when we're assessing with WCAG 2.0.
>>> 
>>> Best practices would encourage the use of progressive enhancement techniques where we would make sure that the basic functionalities are provided before they get enhanced, but as this is outside the cope of we accessibility and therefore, this taskforce, this is not something I feel we should be concerned about.
>>> 
>>> Best regards,
>>> 
>>> -- 
>>> Denis Boudreau, président
>>> Coopérative AccessibilitéWeb 
>>> 
>>> 1751 rue Richardson, bureau 6111 
>>> Montréal (Qc), Canada H3K 1G6 
>>> Téléphone : +1 877.315.5550 
>>> Courriel : dboudreau@accessibiliteweb.com
>>> Web : www.accessibiliteweb.com
>>> 
>>> 
>>> 
>>> 
>>> On 2011-11-21, at 5:24 AM, Vivienne CONWAY wrote:
>>> 
>>>> Hi Alistair
>>>> 
>>>> I have to say I've never encountered one of  those scripts. Can you provide an example and I'll have a try?
>>>> 
>>>> 
>>>> Regards
>>>> 
>>>> Vivienne L. Conway, B.IT(Hons)
>>>> PhD Candidate & Sessional Lecturer, Edith Cowan University, Perth, W.A.
>>>> Director, Web Key IT Pty Ltd.
>>>> v.conway@ecu.edu.au
>>>> v.conway@webkeyit.com
>>>> Mob: 0415 383 673
>>>> 
>>>> This email is confidential and intended only for the use of the individual or entity named above. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify me immediately by return email or telephone and destroy the original message.
>>>> ________________________________________
>>>> From: Alistair Garrison [alistair.j.garrison@gmail.com]
>>>> Sent: Monday, 21 November 2011 6:34 PM
>>>> To: Eval TF
>>>> Subject: Web accessibility enhancement scripts
>>>> 
>>>> Dear All,
>>>> 
>>>> How do we handle pages which contain (what I term) "web accessibility enhancement scripts" - scripts used to alter / augment aspects of the loaded user interface in order to try and provide a better user experience for people with disabilities usually executed by the "screen-reader users, click here to" type link e.g. the "screen-reader users, click here to turn off google instant" found at the top of Google’s search page.
>>>> 
>>>> Should a page be assessed before "web accessibility enhancement scripts" are run, after they are run, or both? Are they even to be mentioned (section 7???) or encouraged at all?
>>>> 
>>>> Seeking thoughts / comments...
>>>> 
>>>> Very best regards
>>>> 
>>>> Alistair Garrison
>>>> 
>>>> This e-mail is confidential. If you are not the intended recipient you must not disclose or use the information contained within. If you have received it in error please return it to the sender via reply e-mail and delete any record of it from your system. The information contained within is not the opinion of Edith Cowan University in general and the University accepts no liability for the accuracy of the information provided.
>>>> 
>>>> CRICOS IPC 00279B
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 
> 

Received on Monday, 21 November 2011 18:00:21 UTC