E-mail List Archives

Search E-mail List Archives for

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

From: Gian Wild
Date: Wed, Aug 27 2014 8:15PM
Subject: JavaScript and WCAG 2.0
No previous message | Next message →

You might also want to read our JavaScript Accessibility Factsheet
<http://wiki.accessibilityoz.com.au/doku.php/checklists/javascript/start>; (
http://wiki.accessibilityoz.com.au/doku.php/checklists/javascript/start) -
written by James Edwards (brothercake). It has some useful demos

Cheers,
Gian

*Gian Wild, Director*
*AccessibilityOz*

*Email.* = EMAIL ADDRESS REMOVED =
*Web. *www.accessibilityoz.com.au
*Phone:*
Canberra: (02) 6108 3689
Melbourne: (03) 8677 0828
Brisbane: (07) 3041 4011





On 16 July 2014 23:41, Patrick H. Lauke < = EMAIL ADDRESS REMOVED = > wrote:

> On 16/07/2014 14:30, Liko, Todd wrote:
>
>> I guess I lean more to the aggressive side. I do understand what you are
>> saying and it does make sense to me when interpreting WCAG 2.0 in that way.
>> I also understand that there will always be barriers for some users, but I
>> do not think we should be creating those barriers. I am not comfortable
>> with telling a user that because they are using a browser or assistive
>> technology that does not support JavaScript, for example, that they cannot
>> obtain the information.
>>
>
> Then of course you're free to make your website/app work perfectly fine
> without JavaScript. Realistically, though, a large number of sites that are
> more complex than simple static pieces of information of workflows that can
> be broken into a few simple server-side forms will struggle to meet (or
> simply ignore) guidelines that require a no-scripting version to be present
> (see for instance WCAG 1.0).
>
>
> I use the example of someone using a public computer at a public library
>> and the computer has JavaScript disabled or outdated browsers and/or
>> assistive technologies. The user may not be able to access the information.
>>
>
> Arguably, that's then a failing of the public library to have an adequate
> provision for users with disabilities. And the way the majority of
> mainstream websites are built nowadays, having browsers with JS turned off
> will make these computers practically unusable for even the most basic and
> common sites (social media, news, etc).
>
> IMHO, of course :)
>
> 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: Olaf Drümmer
Date: Thu, Aug 28 2014 2:15AM
Subject: Re: JavaScript and WCAG 2.0
← Previous message | No next message

A very useful link!

It has one shortcoming though - it focuses on keyboard based access. What about keyboard-less devices, like mobile phones and tablets?

Olaf


On 28 Aug 2014, at 04:15, Gian Wild < = EMAIL ADDRESS REMOVED = > wrote:

> You might also want to read our JavaScript Accessibility Factsheet
> <http://wiki.accessibilityoz.com.au/doku.php/checklists/javascript/start>; (
> http://wiki.accessibilityoz.com.au/doku.php/checklists/javascript/start) -
> written by James Edwards (brothercake). It has some useful demos