WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screenreader Forms Mode as Only Interaction Method?

for

From: Andrews, David B (DEED)
Date: Mar 6, 2017 1:32PM

I use a combination of Forms Mode, and browsing. I find it easier, and more reliable to go in and out of forms mode so I don't miss something.

However, I don't think I am a typical user, but there may not be such a thing, so asking here probably won't get you a definitive answer.

Dave



From: WebAIM-Forum [ <EMAIL REMOVED> ] on behalf of Dan Holbrook [ <EMAIL REMOVED> ]
Sent: Thursday, March 02, 2017 12:36 PM
To: <EMAIL REMOVED>
Subject: [WebAIM] Screenreader Forms Mode as Only Interaction Method?

This was touched upon in the previous thread "Forms, forms mode and static
text interaction with Jaws" but forms mode requires extra care to be taken
in order to make sure certain information (e.g. disabled fields with data,
field instructions, legal disclaimers) is read.

In our testing of forms right now (NVDA and JAWS) we browse to the form,
enter data in the first field, then tab through the form, which requires
developers to attempt to make forms fully accessible to users who use
tabbing alone for form navigation.

I have talked to a few people who use browse mode to go through the form
and used forms mode only for entry, which would make this extra work
unnecessary. I'd like to see if there is a consensus or trend around how
screen reader users navigate forms: do you tab through fields once in a
form (remaining in forms mode) or do you navigate forms with a combination
of forms mode and browsing?