WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Forms, forms mode and static text interaction with Jaws.

for

From: Ramya Sethuraman
Date: Oct 8, 2012 9:43PM

Hey Tim

Thanks for the suggestions. An example of what I am talking about can be
seen when we try to create a Google account for Google adsense, the page
starts off with the text below which is followed by text input fields for
email address and password that the user has to fill. This is followed by a
few lines of text and then a text input field to fill in the captcha
information. I guess what I need to understand better is what is the most
likely way a screen reader user will navigate a dialog which has a few form
fields with text below like I have shown. If they are navigating using
regular down arrow in virtual pc cursor mode, it is less of a concern. But,
if typically they would tab from one field to another when they hear Jaws
switch to forms mode, then this text might be lost. There are some good
suggestions in this thread however to try to prevent that: visual design
change to have a checkbox to ensure users have read the text, hidden text
for screen reader users informing them about the static text, marking the
text as a complementary landmark etc...

Google AdSense: Create a Google AccountTo use Google AdSense with a new
Google Account, please start by filling out the form below. With your email
address and chosen password, you can access Google AdSense and many other
Google services. Learn More <http://www.google.com/help/faq_accounts.html>;

*Do you already use Gmail, , Web History, , or Product Search?*
If so, you already have a Google Account. Sign in with your existing
account<https://accounts.google.com/Login?continue=https%3A%2F%2Fwww.google.com%2Fadsense%2Fv3%2Fascheck%3Fhl%3Den%26sourceid%3Daso%26subid%3Dus-en-et-nelson_adshp_bt%26utm_content%3Dnsufv1%26gsessionid%3DWgXTfyfyS2wj3IXg2473-Q%26pli%3D1%26auth%3DDQAAAHoAAAC2jaG4td1LeRWCW9_s47m8g1AEXYppGaas_eiwtYLOz1DPa7cwBw9-Z5xK_5nH1aGVmkLGpOSzkqVlWDwQX9czqa2VXTJCP7MIbYpaLQkcwePd0NW2MrCYoYvFmPdHQbWSEKlnQMqxKOpzH4-XaW6BK_tMXNPzWxdM__rGF16x7Q&hl=en_US&service­sense&skipvpage=true>
to
use Google AdSense.

----form fields show up here-----

Thanks,
Ramya


On Mon, Oct 8, 2012 at 9:50 PM, Tim Harshbarger <
<EMAIL REMOVED> > wrote:

> This discussion seems to be focusing on how to ensure someone using a
> screen reader reads extraneous text that isn't part of a form field when
> the text is displayed as part of a form.
>
> It occurs to me that there really isn't a way to ensure someone who can
> read the page will read that text either. You can do things to try to draw
> attention to the text, but you can't ensure the user reads it. The screen
> reader problem you are trying to solve may be a lot easier to solve if you
> make it parallel the visual issue--which really is "How do you increase the
> likelihood that the person will read the advertisement or extraneous text?"
>
> I think someone mentioned using a complementary role to the text. A
> header may also be a way to draw attention to the text. It is a solution
> with its own drawbacks, but if your intention is to draw the user's focus
> to that text, you basically need to add something that is likely to catch
> the attention of someone using a screen reader. If you want to reduce
> confusion about whether or not the text relates to the form, you will
> probably need to add some things to ensure the user knows this is an
> advertisement.
>
> But all the above are just thoughts off the top of my head and are totally
> unedited.
>
> Thanks,
> Tim
>
>