E-mail List Archives
Thread: Forms mode and error messages
Number of posts in this thread: 4 (In chronological order)
From: Nancy Johnson
Date: Fri, Aug 12 2011 7:15AM
Subject: Forms mode and error messages
No previous message | Next message →
I have a question regarding forms mode and inline error messages. (I
am using NVDA)
We are using JSF framework for our form... The engineer set up the
<inputs using a grid panel which produces a table. Currently the
error messages are called from the server into a new table cell.
There is no ajax...
First test: I submitted the form so the form would produce all the
default error messages.. Turned on NVDA and listened without trying to
interact... All the error messages were readable and aligned
themselves with the correct control. No problem.
Second test: Tried to add incorrect data to the form so to force an
error message... In this case I had to tab from control to control...
the error message was not readable. Did not actually do anything to
turn on "forms" mode.
I am certainly not an expert with screen readers. Am I doing
something incorrect? Is it to do with tabbing from input to input?
What should I be doing so I can give an accurate report.
Thanks,
Nancy Johnson
From: Léonie Watson
Date: Sat, Aug 13 2011 6:51AM
Subject: Re: Forms mode and error messages
← Previous message | Next message →
Nancy Johnson wrote:
"Second test: Tried to add incorrect data to the form so to force an
error message... In this case I had to tab from control to control...
the error message was not readable. Did not actually do anything to
turn on "forms" mode."
Are the error messages being produced inside the form labels? Are
the labels properly associated with the corresponding form fields? The most
common cause of labels not being announced when tabbing through a form
(either in or out of forms mode), is that the labels aren't setup properly.
More on this here:
http://webaim.org/techniques/forms/controls
Léonie.
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Nancy Johnson
Sent: 12 August 2011 14:14
To: WebAIM Discussion List
Subject: [WebAIM] Forms mode and error messages
I have a question regarding forms mode and inline error messages. (I
am using NVDA)
We are using JSF framework for our form... The engineer set up the <inputs
using a grid panel which produces a table. Currently the error messages are
called from the server into a new table cell.
There is no ajax...
First test: I submitted the form so the form would produce all the
default error messages.. Turned on NVDA and listened without trying to
interact... All the error messages were readable and aligned
themselves with the correct control. No problem.
Second test: Tried to add incorrect data to the form so to force an
error message... In this case I had to tab from control to control...
the error message was not readable. Did not actually do anything to
turn on "forms" mode.
I am certainly not an expert with screen readers. Am I doing something
incorrect? Is it to do with tabbing from input to input?
What should I be doing so I can give an accurate report.
Thanks,
Nancy Johnson
From: Jeevan Reddy
Date: Tue, Aug 16 2011 2:45AM
Subject: Re: Forms mode and error messages
← Previous message | Next message →
Hello Nancy,
you are doing right way!
Generally screen reader users used to switch between focus mode& focus mode
to rectify the input errors.
if the input errors are in descriptive text format, then it won't be any
violation of any accessibility guidelines.
To make it more usable to AT users, you can use ARIA alerts by the
following way.
use ARIA alert role for each invalid field.
enable alert when the user get focus to teh corresponding invalid field
usingJ SF.
Make the Error descriptive.
On Fri, Aug 12, 2011 at 6:43 PM, Nancy Johnson < = EMAIL ADDRESS REMOVED = > wrote:
> I have a question regarding forms mode and inline error messages. (I
> am using NVDA)
>
> We are using JSF framework for our form... The engineer set up the
> <inputs using a grid panel which produces a table. Currently the
> error messages are called from the server into a new table cell.
>
> There is no ajax...
>
> First test: I submitted the form so the form would produce all the
> default error messages.. Turned on NVDA and listened without trying to
> interact... All the error messages were readable and aligned
> themselves with the correct control. No problem.
>
> Second test: Tried to add incorrect data to the form so to force an
> error message... In this case I had to tab from control to control...
> the error message was not readable. Did not actually do anything to
> turn on "forms" mode.
>
> I am certainly not an expert with screen readers. Am I doing
> something incorrect? Is it to do with tabbing from input to input?
> What should I be doing so I can give an accurate report.
>
> Thanks,
>
> Nancy Johnson
>
From: Nancy Johnson
Date: Wed, Aug 17 2011 6:51AM
Subject: Re: Forms mode and error messages
← Previous message | No next message
Thank you for your ideas. I was wondering if WAI-ARIA would help.
I have to look at WAI-ARIA roles more.. Is there a good tutorial that
is basic and to the point? I haven't found a good one easy to follow
for those of us working under stress yet.
Thanks Nancy
On Tue, Aug 16, 2011 at 4:46 AM, Jeevan Reddy
< = EMAIL ADDRESS REMOVED = > wrote:
> Hello Nancy,
> you are doing right way!
> Generally screen reader users used to switch between focus mode& focus mode
> to rectify the input errors.
> if the input errors are in descriptive text format, then it won't be any
> violation of any accessibility guidelines.
> To make it more usable to AT users, you can use ARIA alerts by the
> following way.
> use ARIA alert role for each invalid field.
> enable alert when the user get focus to teh corresponding invalid field
> usingJ SF.
> Make the Error descriptive.
>
> On Fri, Aug 12, 2011 at 6:43 PM, Nancy Johnson < = EMAIL ADDRESS REMOVED = > wrote:
>
>> I have a question regarding forms mode and inline error messages. (I
>> am using NVDA)
>>
>> We are using JSF framework for our form... The engineer set up the
>> <inputs using a grid panel which produces a table. Currently the
>> error messages are called from the server into a new table cell.
>>
>> There is no ajax...
>>
>> First test: I submitted the form so the form would produce all the
>> default error messages.. Turned on NVDA and listened without trying to
>> interact... All the error messages were readable and aligned
>> themselves with the correct control. No problem.
>>
>> Second test: Tried to add incorrect data to the form so to force an
>> error message... In this case I had to tab from control to control...
>> the error message was not readable. Did not actually do anything to
>> turn on "forms" mode.
>>
>> I am certainly not an expert with screen readers. Am I doing
>> something incorrect? Is it to do with tabbing from input to input?
>> What should I be doing so I can give an accurate report.
>>
>> Thanks,
>>
>> Nancy Johnson
>>