Re: error technique - possibly for G2.5 L2 SC2

Hi Andi,

I like starting simple :-).
I have been thinking about a more complex form with multiple errors as the next step. I included the question about possibly providing a way back in the breakdown of steps. My ideas in this regard all have implementation problems from my knowledge of HTML, screen readers and my experience of how screen readers are used. 

HTML techniques I thought about:
1) implementing an accesskey at the list of errors to provide an easy way back to the list. But use of accesskeys have usability and accessibility problems.
2) adding a "skip to next error" link at the end of each field in error. But I don't think this is appropriate to include as part of the 'label', but unless it is included in the 'label' a screen reader user may not know it's there. Also, unless scripting is employed this would assume the user corrects the errors in the order presented in the list of errors.

Any ideas?

Sofia



Andi wrote:
I like this as a simple example. But what if the form is more complex and
the user made multiple errors? I assume that each error would be listed at
the top with a link to the field in error. When the user selects a link to
navigate to the field and correct the error, he or she will then want to
return to the list of errors to proceed to the next one. Would we just
depend on the "Back" button for this or should we provide a more obvious
way to return to the list of errors?