- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Wed, 21 Mar 2012 09:35:58 -0400
- To: "Homme, James" <james.homme@highmark.com>, w3c-wai-ig@w3.org
Jim, This is creating a 'custom link' apparently. Imagine an anchor tag like <a name="content" id="content" tabindex="-1"></a> This could be the target of a skip link but this anchor tag is not exposed as a link by assistive technology. It also has no text within.. Now the example you give is perhaps styled to look as a link, contains anchor text but has no href attributes or a role that conveys that the element is a link. So it fails SC 4.1.2 (A) and maybe SC 2.1.1 (A). Hope this helps. Sailesh Panchang Deque Systems www.deque.com On 3/21/12, Homme, James <james.homme@highmark.com> wrote: > Hi, > 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: > class=sitemapPageName > > Tag A has 4 parameters: > class=sitemapPageLink > jquery1332334255145=40 > nodeurl=Pega_Color_Scheme.html > shape= > > > 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 13:36:26 UTC