E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 2 (In chronological order)

From: Detlev Fischer
Date: Fri, Mar 31 2023 4:28AM
Subject: iOS keyboard accessibility, focus order, and testing
No previous message | Next message →

I am currently testing the keyboard accessibility of a native iOS app
using an iPad pro 12'' with magic keyboard under iPad OS 16.3.1. iOS
keyboard accessibility has improved since the days where it needed
VCoiceOver switched on (and possibly muted) but it is still a mixed bag.
More on that below.

In testing, I turn on the setting Accessibility > Keyboards > Full
Keyboard Access, and test with VoiceOver off.

The situation is many cases is that a large area of a view receives tab
focus. Interactive elements within that area may then be focusable via
arrow keys, but not necessarily in a linear fashion in the same way as
with tab (where you'd expect to reach every interactive element of the
view when traversing the entire focus ring). Instead, reaching elements
may require using both up and down as well as left / right arrow keys in
what I would, for want of a better name, label "matrix navigation" (you
have to see where the element is to use the appropriate arrow key to
focus it). At the same time, swipe navigation with VoiceOver turned on
seems to follow the visual arrengement and reaches all elements.

As to conformance, it appears that such content would pass 2.1.1
Keyboard since there is no normative constraint on what keys must be
used to reach and activate content.

However, I tend to fail such content against 2.4.3 Focus Order since
there is no linear way to reach all elements via one pair of arrow keys
(left to right, or top to bottom).

Just for reference, there is a somewhat related question from Josh from
2018 about iOS keyboard access
https://webaim.org/discussion/mail_thread?thread‡43

I wonder how other people tackle such iOS keyboard issues, and what
recommendations or pointers they are likely to give developers to
improve matters.

Best, Detlev

--
Detlev Fischer
DIAS GmbH
(Testkreis is now part of DIAS GmbH)

Mobil +49 (0)157 57 57 57 45

http://www.dias.de
Beratung, Tests und Schulungen für barrierefreie Websites

From: glen walker
Date: Fri, Mar 31 2023 10:46AM
Subject: Re: iOS keyboard accessibility, focus order, and testing
← Previous message | No next message

Not sure if this helps but the accessibilityElements property is an array
that is used to control the VoiceOver focus order. It should be a generic
property not specific to VoiceOver but rather as an aid to all assistive
technology, including a keyboard, but I can't say for sure if
accessibilityElements affects the keyboard order, and even if it did, does
it only control the TAB order or can it affect the arrow key order. If I
had a Mac, I'd play with xcode to see how it works.

https://developer.apple.com/documentation/objectivec/nsobject/1615147-accessibilityelements