- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Thu, 10 May 2012 10:43:12 +0100
- To: Phil Spencer <spencer_phil@hotmail.com>
- Cc: ax interest list <w3c-wai-ig@w3.org>
- Message-ID: <CA+ri+VngXpe9V0YA9+pu9ZUQK5AT414ovjZM48-nAqd9tnL9XA@mail.gmail.com>
Hi Phil you wrote: "My question is, is this sufficient to meet the various success criteria? I kind of assumed that it wouldn't be, but when I tested with IE9 and JAWS12 it seemed to work just the same as if the title attribute was directly on the form element." This method does not provide an accessible name for the input i.e. if you check the accessible name for the input using an inspect tool such as Aviewer [1] the input has no name property value in MSAA or IA2 accessibility APIs. checked NVDA with IE9 does not announce label. [1] http://www.paciellogroup.com/blog/2011/06/aviewer-beta-updated/ regards stevef On 10 May 2012 10:25, Phil Spencer <spencer_phil@hotmail.com> wrote: > Hi All, > > I have a question that I'm hoping someone may be able to help with > regarding technique H65: Using the title attribute to identify form > controls when the label element cannot be used. > > This technique is about using a title attribute to describe a form element > where a label element can't be used for whatever reason, and relates to > several success criteria as listed in the link below: > > http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/H65 > > I'm evaluating a web page where this technique has been used in a slightly > different way. The descriptive title attribute has been applied to a span > element that wraps the form element, rather than directly to the element > itself, simplified code snippet follows: > > <span title="description of form element"><input type="radio" /></span> > > My question is, is this sufficient to meet the various success criteria? I > kind of assumed that it wouldn't be, but when I tested with IE9 and JAWS12 > it seemed to work just the same as if the title attribute was directly on > the form element. > > Does anyone have any experience with this? Is the JAWS / IE behaviour > likely to be repeated with other browser / AT combinations? > > Many thanks in advance, > > Phil Spencer. > > > -- with regards Steve Faulkner Technical Director - TPG www.paciellogroup.com | www.HTML5accessibility.com | www.twitter.com/stevefaulkner HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/ Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Thursday, 10 May 2012 09:44:27 UTC