WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Aaron Cannon
Date: Jul 31, 2015 11:52AM

On my iPhone, the enter key is generally in the bottom right corner of
the keyboard.

Aaron Cannon

On 7/31/15, Birkir R. Gunnarsson < <EMAIL REMOVED> > wrote:
> Hi
>
> No, your average iPhone virtual keyboard does not have an enter key,
> that is what concerns me the most.
> Users of mobile devices running Voiceover will be very likely to view
> your webpage, how are they to activate the search?
> Maybe there is a mechanism already, but it is important to think of
> your mobile device users, disabled or otherwise.
> That´s why I would tentatively call a 2.1.1 issue on this, and say
> that for users of mobile devices there is no way to activate the
> search.
> If the responsive view of the page already takes care of this I think
> I could not call it a WCAG violation, though I would make a usability
> note.
> I, myself, get confused when I do not have a submit button for forms
> that I am filling in.
>
> Cheers
>
>
> On 7/31/15, Aaron Cannon < <EMAIL REMOVED> > wrote:
>> Don't most mobile keyboards, on-screen or otherwise, provide an enter key?
>>
>> Aaron Cannon
>>
>> On 7/31/15, Birkir R. Gunnarsson < <EMAIL REMOVED> > wrote:
>>> 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.
>>> >>> >>> >>> >>>
>> >> >> >> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > > >