WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Issue with on-screen keypad in IOS


From: Cliff Tyllick
Date: Sep 18, 2015 3:52AM

Sorry... Let me finish. (My big fat fingers hit "Send" too soon.)

That's interesting, Sailesh. I had noticed that the iPhone lacks a key for dismissing the keyboard, but I had never thought about it in this context.

I'm not a developer, and I'm certainly not an iOS developer, but I see that there is a hotspot of sorts at the top center of the keyboard, just above and between the "T" and "Y" keys. For sighted users, a quick swipe down in that area will dismiss the keyboard. Because it is such a narrow band, it's hard to make that hotspot take and hold focus. I have to hold my finger on the screen just right to make that happen. Actually it happens any time I hover my finger anywhere right over that very narrow band all the way across the top of the keyboard.

If Apple could make that band take focus more easily and then act like a button when VoiceOver is on, that might be a way to provide that action.

In testing the behavior of that region of the screen, I notice that there's almost no way to access it by holding a finger down and dragging it over the keyboard. I have to catch the area just right on first touching the screen.

Anyway, maybe that's a handle whose action could be improved by Apple from a couple of different approaches with respect to accessibility.

Cliff Tyllick

Sent from my iPhone
Although its spellcheck often saves me, all goofs in sent messages are its fault.

> On Sep 17, 2015, at 4:00 PM, Sailesh Panchang < <EMAIL REMOVED> > wrote:
> Sure this is an issue while filling out any form on a mobile platform
> that I have always encountered as a screen reader user.
> I am referring to forms with multiple text boxes one after another
> including just a username and password field.
> When the form has two or more fields, the application cannot guess
> that one has finished entering data ... unless it is a standard
> phone# or date field and such.
> On an iPad one can dismiss the keyboard but not on an iPhone because
> there is no dismiss keyboard key.
> So when one dismisses the keyboard the focus should go back to the
> field that had focus or the next focusable element.
> Sailesh Panchang
>> On 9/17/15, Paul J. Adam < <EMAIL REMOVED> > wrote:
>> These are bugs with iOS VoiceOver. Please file a bug report with Apple. They
>> fixed a few of mine recently. I filed one not fixed related to <select>
>> controls not sending focus to the picker view whien you expand the select on
>> iPhone and when you close the picker the focus is not returned to the
>> triggering element instead the focus is lost to the top of the page and the
>> user would have to swipe all the way back to where they were.
>> On iPad when you expand a select control the focus is trapped in the pop
>> over view which is great, but the focus is still lost to the top of the page
>> after dismissing the pop over.
>> I've not looked into manually sending focus where you want it to go with
>> JavaScript.
>> Paul J. Adam
>> Accessibility Evangelist
>> www.deque.com
>>> On Sep 17, 2015, at 1:24 AM, Subhash Chhetri < <EMAIL REMOVED> >
>>> wrote:
>>> Hi Accessibility Experts,
>>> Today I'm stuck in one issue in IOS. - Actually I'm filling an html form
>>> in IOS with Voice over, and I'm using on-screen keypad not the physical
>>> one. So the problem I'm facing is that when I finish typing in any form
>>> field and pressing Hide keyboard button located at the right end of
>>> on-screen keypad, focus doesn't move directly to the edit field, it
>>> remains anywhere in application.
>>> This is so frustrating that I have to go back to the form fields either by
>>> flicking left/right on screen or by selecting forms via roter.
>>> Is there anything I'm missing? Or it's a behavior of IOS.
>>> Thanks
>>> Best Regards,
>>> Subhash Chhetri
>>> >>> >>> >>> >>
>> >> >> >> > > > >