[Accessibility_sig] placement of audio captcha in a form

[Squeek]

At 04:39 PM 5/7/2007, you wrote:
>content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>        boundary="----_=_NextPart_001_01C790F0.3726AF28"
>
>Have you tested this with JAWS to ensure that the info in the popup window is available? I have found that sometimes JAWS will only read parts of a popup window, and the default appears to be "Cancel."
> 

Yes, I did, and it does read the entire message.  On WinXP, the default was "Cancel".  On win2k, the default was "Save".  Whether it plays right there in your browser or not, or even prompts you, is a matter of individual browser settings, and mime type settings.

I'm a beginner with jaws, so bear with me.  When jaws reads the entire page to you, it reads the labels in the order they are on the page, which includes "graphic image", and the link to the audio, and it's announced as a link, but you're not in forms mode.

When you move through the form using the tab key (I clicked in there...don't know how to get into forms mode with jaws keystrokes yet), after "Comments: edit" it reads "link listen to the characters being spoken", then after the next tab, it reads "Enter the characters you see in the image above into the textbox below.  If you cannot see the image, listen to the characters being spoken. " and doesn't announce the link as a link.  Not very helpful.

I don't know how a jaws user would read the page, straight through, with arrow keys, or the tab key or some other way.  With the tab key, it seems I should at least put in more information about the fact that there is a graphic and audio captcha there.

I know captchas are a real pita, but unfortunately, they have their place.  I was hoping to get feedback from actual jaws users on how to construct the form so it reads as clearly as possible.  

One bad example:  https://www.kiwibank.co.nz/banking/login.asp where they use "here" for the link.  

A better example is at http://www.standards-schmandards.com/exhibits/captcha/ where there is plenty of explanation, although I can't figure out the letters in THAT image!

Should I put a verbose explanation at the top of the form like standards-schmandards?  Should I hide it with styles, so as not to distract sighted users?  Some of them might actually want to see it.  Should I add title text to the link to explain its usage more thoroughly?


CU at AccessU tomorrow.



Bill Woodland, Austin, Tx <squeek at austin.rr.com>
Somebody should shoot the guy who invented HTML Email.
http://squeekasp.com