E-mail List Archives
Thread: ARIA role=tree for mobile?
Number of posts in this thread: 3 (In chronological order)
From: Judith.A.Blankman
Date: Wed, Aug 12 2015 5:13PM
Subject: ARIA role=tree for mobile?
No previous message | Next message →
I'm specifying requirements for a mobile-only navigation that has more than one level. I know it should be coded as a nested unordered list. What I don't know if VoiceOver and TalkBack support aria role="tree" and role="treeitem."
On an iPhone5, I was trying out this example, linked from the WAI page http://oaa-accessibility.org/examplep/treeview1/
There was no indication of any structure or whether the tree was expanded or collapsed. Nor was there any indication when I was on the first or last item in a list, which I typically hear in an unordered list.
It seems like the ARIA in this case got in the way of the list structure. My gut is not to use it for a mobile-only implementation.
Would love thoughts from anyone who can chime in.
Best,
Judith Blankman
Accessibility Strategist
Customer Experience (CX)
WFVC Digital | 1 Front Street | San Francisco, CA 94111
Tel: 415-947-6583 | Cell: 415-601-1114
MAC: A0195-171
j<mailto: = EMAIL ADDRESS REMOVED = > = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
From: Patrick H. Lauke
Date: Wed, Aug 12 2015 6:30PM
Subject: Re: ARIA role=tree for mobile?
← Previous message | Next message →
On 13/08/2015 00:13, = EMAIL ADDRESS REMOVED = wrote:
> I'm specifying requirements for a mobile-only navigation that has
> more than one level. I know it should be coded as a nested unordered
> list. What I don't know if VoiceOver and TalkBack support aria
> role="tree" and role="treeitem."
>
> On an iPhone5, I was trying out this example, linked from the WAI
> page http://oaa-accessibility.org/examplep/treeview1/
>
> There was no indication of any structure or whether the tree was
> expanded or collapsed. Nor was there any indication when I was on the
> first or last item in a list, which I typically hear in an unordered
> list.
>
> It seems like the ARIA in this case got in the way of the list
> structure. My gut is not to use it for a mobile-only implementation.
>
> Would love thoughts from anyone who can chime in.
Once you move beyond basic ARIA, support is rather poor on in mobile
assistive technologies, and it's currently better to avoid most
composite widgets (and widgets whose role makes them components of these
composite widgets).
Beyond things not being announced, there are further issues with
following the (usually very keyboard-specific) design patterns for ARIA,
as they don't translate (badly or at all) to mobile assisitive
technologies using touchscreen gestures, and even paired keyboards. See
https://github.com/w3c/aria/issues/60, which led to me adding this note
http://w3c.github.io/aria-in-html/#aria-touch and the very rough and
ready google doc where some of us tried to document this
https://docs.google.com/spreadsheets/d/1gN9oRZPdrJxLDNtT6nVO4fn7E7sn1061L9Xl3__slZ4/edit#gid=0
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: Jonathan Avila
Date: Sun, Aug 16 2015 7:44PM
Subject: Re: ARIA role=tree for mobile?
← Previous message | No next message
> I'm specifying requirements for a mobile-only navigation that has more than one level. I know it should be coded as a nested unordered list. What I don't know if VoiceOver and TalkBack support aria role="tree" and role="treeitem."
I personally don't believe an ARIA tree structure is the right structure for navigation. The use of several ARIA roles should really be limited, menu, tree, page, etc. should really be limited to desktop equivalents and should be avoid in navigation situations.
Jonathan
--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
= EMAIL ADDRESS REMOVED =
703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter