WebAIM - Web Accessibility In Mind

E-mail List Archives

Form Submit or Button versus link (href) with action

for

From: Susan Grossman
Date: Nov 5, 2010 12:33PM

This may be a bit of a "no-brainer", but I wanted to make sure. When using
Ajax I do cartwheels trying to break the code before calling it accessible,
and send it back to development a lot!

FYI - JavaScript is required to use this application, for other product
related reasons (this is a service backing up a product).

Were working on an application that we're trying to meet WCAG 2.0. One
little issue is the need for a submit button on a form. We're using a table
with accessible Ajax that on a link (tab/enter or click), changes a text
field to an input.

On this change the focus is moved to the input, which is labeled and
announces itself correctly, both the label and the current content are read
out.

After changing this text (it's a rename) the next item tabbed to is a "save"
link that (tab/enter or click) saves the changed text without refreshing the
page. There is a message that it has been saved and focus is moved to the
link that now says "rename" instead of "Save" (the readers speak this) and
you can continue tabbing to the next table row from there. Focus is not
locked, and everything is tab-able.

I've tested in JAWS and NVDA (I know the basic keys/shortcuts, though I'm
not a "real user") and tested with just keyboard. I believe this meets the
needs, but of course the validators tell me I still need a submit. I'm
aware that a validator isn't the "end all" but a guide, but wanted to make
sure I didn't miss something before calling this accessible.

Any comments would be helpful or pointers to how others handle the balance
between Ajax and accessibility

Thanks -

--
*Susan R. Grossman*
<EMAIL REMOVED>