WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: InfoPath


From: Egan, Bim
Date: Jul 29, 2010 8:30AM

One possible reason why JAWS has title attributes switched off by default, is that it seems to be at the cost of other more reliable attributes, such as the alt attribute, or perhaps to reduce the likelihood of unnecessary redundancy. One of the screen readers that I use reads title attributes without any option to turn them off, and the result is a massive overload of repeated information.

However, by default JAWS does normally read title attributes on form control elements. The only time I've come across it failing to do so is when there's also an explicit association to a label, in which case JAWS just reads the label.



-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of David Farough
Sent: 29 July 2010 14:52
Subject: Re: [WebAIM] InfoPath

I think that you need to modify the jaws verbosity settings so that Jaws will speak tooltips. This setting is turned off by default in all verbosity levels.

You can find these settings in the Jaws configuration manager. open the settings menu and select verbosity options.. Here you will see your current verbosity level. there is a button which allows you to specify the verbosity options for each of the available verbosity settings. The speak tooltips option is the last item in the list of options. Make sure that this is checked. Once you save the configuration, Jaws should speak the tooltips.

I don't know why this is disabled by default, but if you are going to rely on tooltips, your users will need to know how to set these options if they use Jaws.

David Farough
Application Accessibility Coordinator/coordonateur de l'accessibilité Information Technology Services Directorate / Direction des services d'information technologiques Public Service Commission / Commission de la fonction publique Email / Courriel: <EMAIL REMOVED>
Tel. / Tél: (613) 992-2779

>>> < <EMAIL REMOVED> > 04:53 PM Wednesday, July 28, 2010
Does anyone know how to create accessible forms using MS InfoPath. The InfoPath help system insists that you can label the forms through the properties dialog using the tooltip input. We have created forms in this manner but JFW 9 and 10 do not even recognize that any for fields are present and JFW 11 does not read the information from the tool tip but grabs the screen text apparently based upon proximity.

I am not sure if we are doing something wrong, which is entirely possible, if it is something in our deployment environment, MS SharePoint V7, or that InfoPath is just not compatible with JFW. It does appear to work with NVDA so I suspect that this may be a JFW issue but I am not willing to give up yet.

Mike Moore