[WSG] jQuery accessibility

2011-10-09 Thread Grant Bailey

Hello everyone,

Could someone please clarify whether a site built with jQuery is 
consistent with web standards and accessibility, assuming that the 
jQuery components: (i) degrade gracefully; and (ii) are not necessary 
for essential functions (such as navigation).


I would be grateful for responses as I am confused about screen reading 
software: I thought these ignored Javascript but apparently, some are 
Javascript-capable. Moreover, as Filament Group point out (in this 
article 
http://filamentgroup.com/lab/expand_and_collapse_content_accessibly_with_progressive_enhancement_jquery/ 
about collapsible panels), many blind users expect a fully-functioning 
website.


Is accessibility normally built in to jQuery or must we add it ourselves 
(as Filament Group did)?


I would be grateful for any responses.

Thank you and kind regards,

Grant Bailey


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: [WSG] jQuery accessibility

2011-10-09 Thread Karl Lurman
Use of any framework does not automatically make your website
accessible. JQuery only attempts to make the development of JavaScript
more consistent across the various browsers (and, as you so rightly
point out, some screen readers as well). You must still provide your
own 'accessibility'. Firstly, by adhering to standards compliant
mark-up with a focus on the various accessibility guidelines. And
secondly, by taking into account JavaScripts operation (or lack
thereof) within screen readers. Although this stuff is not rocket
science, it's not trivial either, and most importantly, there
definitely isn't a magic bullet...

Karl

On Mon, Oct 10, 2011 at 2:02 PM, Grant Bailey
grant_malcolm_bai...@westnet.com.au wrote:
 Hello everyone,

 Could someone please clarify whether a site built with jQuery is consistent
 with web standards and accessibility, assuming that the jQuery components:
 (i) degrade gracefully; and (ii) are not necessary for essential functions
 (such as navigation).

 I would be grateful for responses as I am confused about screen reading
 software: I thought these ignored Javascript but apparently, some are
 Javascript-capable. Moreover, as Filament Group point out (in this article
 about collapsible panels), many blind users expect a fully-functioning
 website.

 Is accessibility normally built in to jQuery or must we add it ourselves (as
 Filament Group did)?

 I would be grateful for any responses.

 Thank you and kind regards,

 Grant Bailey

 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] jQuery accessibility

2011-10-09 Thread Chad Kelly

On 10/10/2011 2:02 PM, Grant Bailey wrote:

Hello everyone,

Could someone please clarify whether a site built with jQuery is 
consistent with web standards and accessibility, assuming that the 
jQuery components: (i) degrade gracefully; and (ii) are not necessary 
for essential functions (such as navigation).


I would be grateful for responses as I am confused about screen 
reading software: I thought these ignored Javascript but apparently, 
some are Javascript-capable. Moreover, as Filament Group point out (in 
this article 
http://filamentgroup.com/lab/expand_and_collapse_content_accessibly_with_progressive_enhancement_jquery/ 
about collapsible panels), many blind users expect a fully-functioning 
website.


Is accessibility normally built in to jQuery or must we add it 
ourselves (as Filament Group did)?


I would be grateful for any responses.

Hi Grant.
Generally no you need to add the extra functionality to make the website 
accessible as Jquery takes the focus from the main content of the 
website and hides it so the Jquery content is in focus, so you need to 
make sure all your on focus content has keyboard functions built into it.





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

RE: [WSG] jQuery accessibility

2011-10-09 Thread Sam Dwyer
Hi,
jQuery is a framework for building components and for easily manipulating the 
DOM of a web page, by itself it doesn't have anything to say about specific 
accessibility concerns.
Plugins and third party components that have be built on top of jquery may or 
may not implement suitable accessibility depending on how much effort the 
developer put into it.
Components that are part of the http://jqueryui.com/ are increasingly becoming 
more accessible with the intent that all component will have wai-aria support 
added by the release of jquery ui 2.0. Several existing UI components such as 
progress bar and accordions have WAI-ARIA functionality built into them - you 
just have to explore the code a bit when you use them and see which components 
have been done and which are still in development in terms of accessibility.

To see some test cases on how certain javascript interactions that have been 
coded for accessibility may look and function you can take a look at this page 
here:
http://codetalks.org/wiki/index.php/Set_of_ARIA_Test_Cases

Hope that helps a bit.
Cheers,
Sam



From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Chad Kelly
Sent: Monday, 10 October 2011 3:05 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] jQuery accessibility

On 10/10/2011 2:02 PM, Grant Bailey wrote:
Hello everyone,

Could someone please clarify whether a site built with jQuery is consistent 
with web standards and accessibility, assuming that the jQuery components: (i) 
degrade gracefully; and (ii) are not necessary for essential functions (such as 
navigation).

I would be grateful for responses as I am confused about screen reading 
software: I thought these ignored Javascript but apparently, some are 
Javascript-capable. Moreover, as Filament Group point out (in this 
articlehttp://filamentgroup.com/lab/expand_and_collapse_content_accessibly_with_progressive_enhancement_jquery/
 about collapsible panels), many blind users expect a fully-functioning website.

Is accessibility normally built in to jQuery or must we add it ourselves (as 
Filament Group did)?

I would be grateful for any responses.
Hi Grant.
Generally no you need to add the extra functionality to make the website 
accessible as Jquery takes the focus from the main content of the website 
and hides it so the Jquery content is in focus, so you need to make sure all 
your on focus content has keyboard functions built into it.


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
--

Please consider the environment before printing this e-mail.

The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***