W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2012

RE: Advice About JQuery Accessibility

From: Gavin Thomas <Gavin.Thomas@uwe.ac.uk>
Date: Wed, 21 Mar 2012 14:17:52 +0000
To: "Homme, James" <james.homme@highmark.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <A169BAD2C2DC6D418270CDC03DF5CDF44046CAF2D8@EGEN-MBX02.campus.ads.uwe.ac.uk>
Maybe not the same function but I've had our developers avoid using the jquery hide function as it uses display:none which hides content to screenreaders.

From: Homme, James [mailto:james.homme@highmark.com]
Sent: 21 March 2012 13:00
To: w3c-wai-ig@w3.org
Subject: Advice About JQuery Accessibility

I'm running into instances where I'm seeing legitimate JQuery things like hyperlinks, and other items that you'd normally be able to activate and hear what's going on, but JAWS isn't saying the word link or communicating the word clickable, and for good reason: The code behind these items is calling JQuery functions, rather than doing the usual HTML thing. In this particular instance, I can't do anything about it, but if I get the chance to, what's the correct accessibility advice to give about this. Here's the information JAWS gives about one of the hyperlinks.

Element Information:

Tag SPAN has 1 parameters:

Tag A has 4 parameters:

Jim Homme,
Usability Services,
Phone: 412-544-1810.


This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates.
Received on Wednesday, 21 March 2012 14:18:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:39 UTC