E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 5 (In chronological order)

From: Dylan Nicholson
Date: Tue, Oct 21 2014 6:46PM
Subject: http://webaim.org/techniques/ajax/ - WCAG 2.0 & JavaScript
No previous message | Next message →

"The Web Content Accessibility Guidelines<http://www.w3.org/TR/WCAG20/>; also require that web applications function when JavaScript is disabled or not supported"

I've looked through WCAG 2.0 pretty carefully and I can't see anywhere that says that a web application is required to "function" when JavaScript is not supported. Sure, you need a NOSCRIPT tag explaining that JavaScript is required, but to suggest a web application has to "function" in this case is surely unrealistic in this day and age. Is this just poor wording?

Thanks

Dylan

From: Detlev Fischer
Date: Sun, Oct 26 2014 11:08AM
Subject: Re: http://webaim.org/techniques/ajax/ - WCAG 2.0 & JavaScript
← Previous message | Next message →

Hi Dylan,

I think the quotation you provide is not included in the latest version of WCAG 2.0, at least not in the normative text that you link to. Can you check again and provide a pointer to the place where you found it?

The text you quote is also not to be found in the "Understanding WCAG 2.0" document
http://www.w3.org/TR/UNDERSTANDING-WCAG20/complete.html

There was checkpoint 6.3 in WCAG 1.0 ("Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported.") but this requirement was not kept in WCAG 2.0. I think you are right that it is unrealistic to expect web applications to function properly without JavaScript today.

Best,
Detlev


On 22 Oct 2014, at 02:46, Dylan Nicholson < = EMAIL ADDRESS REMOVED = > wrote:

> "The Web Content Accessibility Guidelines<http://www.w3.org/TR/WCAG20/>; also require that web applications function when JavaScript is disabled or not supported"
>
> I've looked through WCAG 2.0 pretty carefully and I can't see anywhere that says that a web application is required to "function" when JavaScript is not supported. Sure, you need a NOSCRIPT tag explaining that JavaScript is required, but to suggest a web application has to "function" in this case is surely unrealistic in this day and age. Is this just poor wording?
>
> Thanks
>
> Dylan
>
>
> > > --
Detlev Fischer
testkreis - das Accessibility-Team von feld.wald.wiese
c/o feld.wald.wiese
Thedestraße 2
22767 Hamburg

Tel +49 (0)40 439 10 68-3
Mobil +49 (0)1577 170 73 84
Fax +49 (0)40 439 10 68-5

http://www.testkreis.de
Beratung, Tests und Schulungen für barrierefreie Websites

From: Patrick H. Lauke
Date: Sun, Oct 26 2014 2:48PM
Subject: Re: http://webaim.org/techniques/ajax/ - WCAG 2.0 & JavaScript
← Previous message | Next message →

On 26/10/2014 17:08, Detlev Fischer wrote:
> Hi Dylan,
>
> I think the quotation you provide is not included in the latest version of WCAG 2.0,

The quote that Dylan provided is in the WebAim article mentioned in the
email subject http://webaim.org/techniques/ajax/

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Steve Faulkner
Date: Sun, Oct 26 2014 3:05PM
Subject: Re: http://webaim.org/techniques/ajax/ - WCAG 2.0 & JavaScript
← Previous message | Next message →

it is fairly obvious that the article in question is old and while the link
has been updated to point to wcag 2 the rest of the article is wcag 1 old
skool.

--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;

On 26 October 2014 20:48, Patrick H. Lauke < = EMAIL ADDRESS REMOVED = > wrote:

> On 26/10/2014 17:08, Detlev Fischer wrote:
>
>> Hi Dylan,
>>
>> I think the quotation you provide is not included in the latest version
>> of WCAG 2.0,
>>
>
> The quote that Dylan provided is in the WebAim article mentioned in the
> email subject http://webaim.org/techniques/ajax/
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
> > > >

From: Jared Smith
Date: Mon, Nov 03 2014 11:34AM
Subject: Re: http://webaim.org/techniques/ajax/ - WCAG 2.0 & JavaScript
← Previous message | No next message

I've updated the article (http://webaim.org/techniques/ajax/) to refer
to the correct WCAG 2.0 requirements and to make it more up-to-date.

Thanks,

Jared

On Sun, Oct 26, 2014 at 3:05 PM, Steve Faulkner
< = EMAIL ADDRESS REMOVED = > wrote:
> it is fairly obvious that the article in question is old and while the link
> has been updated to point to wcag 2 the rest of the article is wcag 1 old
> skool.
>
> --
>
> Regards
>
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;
>
> On 26 October 2014 20:48, Patrick H. Lauke < = EMAIL ADDRESS REMOVED = > wrote:
>
>> On 26/10/2014 17:08, Detlev Fischer wrote:
>>
>>> Hi Dylan,
>>>
>>> I think the quotation you provide is not included in the latest version
>>> of WCAG 2.0,
>>>
>>
>> The quote that Dylan provided is in the WebAim article mentioned in the
>> email subject http://webaim.org/techniques/ajax/
>>
>> P
>> --
>> Patrick H. Lauke
>>
>> www.splintered.co.uk | https://github.com/patrickhlauke
>> http://flickr.com/photos/redux/ | http://redux.deviantart.com
>> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>>
>> >> >> >>
> > >