WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG2: does a search form without a submit button fail?

for

From: Birkir R. Gunnarsson
Date: Jul 31, 2015 5:44AM

How would users of a mobile device submit the form?

On 7/31/15, _mallory < <EMAIL REMOVED> > wrote:
> Hi,
> what happens if I entered searchy text and hit tabr+enter? if I didn't
> see there wasn't a button, I may overshoot the form.
>
> Unless it fails Understandable, which it well might, this may be more
> the realm of so-so usability rather than a direct WCAG violation.
>
> Whether it's expected behaviour is pretty much set by your userbase.
>
> In a not-very-relevant aside, I still use Opera 12 for various keyboardy
> reasons. Some sites, like community.sitepoint.com (which does have a
> separate submit) give me a CSRF error if I hit enter rather than first
> focussing on the submit. I suspect this is due to the hidden input not
> being sent along with the login/pass on enter (form submit) which some
> browsers have been known to have issue with, while *everything* is sent
> on the submit-button-click+submit event.
>
> This might not be an issue with users of non-ancient browsers though.
>
> _mallory
>
>
> On Fri, Jul 31, 2015 at 10:11:28AM +0100, Lynn Holdsworth wrote:
>> Hi all,
>>
>> I have a search form that's submitted when a user presses Enter in the
>> textbox. It doesn't include a submit button.
>>
>> Does this fail WCAG2 anywhere, or does this fall into the realms of
>> expected behaviour?
>>
>> Thanks as always, Lynn
>> >> >> >> > > > > >


--
Work hard. Have fun. Make history.