WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Meaningful Sequences for "Back" and "Continue" on Wizards

for

From: MEJ - Beth Sullivan
Date: Dec 15, 2014 11:45AM

Lynn and Jonathan,

Thank you for your responses. I can imagine how having the Continue button
be the first one would be faster for a screen reader user.

A questions for you Lynn, what do you expect when there is also a reset
button for a form. Do you expect something like "Continue" "Reset" "Back" ?

For low vision, cognitive and motor issues, what is the easiest flow and
how important is the "meaningful sequence" to people. A lot of responsive
design also requires weird ordering of elements when the page is stretched
out. How do people with different disabilities find those sites?

Thank you,

Beth


From: Lynn Holdsworth < <EMAIL REMOVED> >
To: WebAIM Discussion List < <EMAIL REMOVED> >
Cc:
Date: Tue, 9 Dec 2014 11:18:08 +0000
Subject: Re: [WebAIM] Meaningful Sequences for "Back" and "Continue" on
Wizards
I'm an impatient screenreader user. I rush through forms as fast as I
can, and assume the first button I come across is the submit button.
I've lost count of the number of times I've accidentally gone back a
step or cleared the form I've just filled in. So from a personal
perspective I'd love the Continue button to be the first one in the
source code.

Thanks, Lynn

On 08/12/2014, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> In my opinion this seems off, but most of the people that I talk to don't
>> see this as a big issue since the business wants the user to see the
>> "Continue" button as the default button.
>
> In my opinion these situations can be confusing but sometimes helpful. As
> long as they are consistent they wouldn't appear to be accessibility
> violations. A common example of reading order that doesn't match the
visual
> order is Wikipedia -- on that site the main content is first in the
reading
> order despite content to the left and above it. One additional group
that
> this is confusing for is people with low vision who may use text-to-speech
> but can see the page.
>
> Jonathan
>
>