Re: What is the expected behavior of scrollable divs within touch screen devices, and does ARIA apply?

Happy to report that this works great in Firefox for Android on a Nexus
7. The tree items on the left are spoken as well as the content in the
region on the right. Switching to different scenes on the left scrolls
the right so the heading for that scene is at the top of the currently
visible/touchable content. Scrolling that with two fingers up and down
does also work. So does simply swiping through the content or letting
TalkBack read from the current position to the end.

Marco

Am 26.04.2014 05:31, schrieb Bryan Garaventa:
> Alright, how about this one?
> http://whatsock.com/tsg/Coding%20Arena/ARIA%20Trees/Tree%20(External%20XML)/
> demo2.htm
> Imagine an e-book reader, where, on the left, you have a scrollable index of
> the chapters that you can scroll through and activate, and to the right of
> that, you have a viewer pane where you can read specific chapters or
> articles.
>
> E.G The above demo uses an ARIA Tree construct as the index mechanism, and a
> keyboard accessible scrollable div pane on the right for readers to view the
> desired scene from Hamlet.
>
> The ARIA Tree is surrounded by a scrollable div that includes role="region"
> and aria-label="Hamlet, by William Shakespeare - Index", and the scrollable
> reader pane on the right includes role="region" and aria-label="Viewer".
>
> So, in theory, it should be possible to view this using a mobile device like
> the iPhone/iPad in landscape mode, tap the Scene that you want to load after
> expanding the desired Act, then move focus into the scrollable "Viewer" pane
> on the right, and swipe up and down to review all of the content displayed
> there from top to bottom.
>
> With regard to VoiceOver, this appears to expose several bugs, the first
> with ARIA Trees, where the expanded/collapsed state via aria-expanded within
> branch nodes is not conveyed, nor is the level information declared via
> aria-level, nor is the positioning information via
> aria-setsize/aria-posinset.
>
> Additionally, none of the region information is conveyed, such as the
> explicit label for each region via role="region" + aria-label to convey its
> purpose and where the boundaries are, nor is it possible to swipe up and
> down to scroll the viewer content using VoiceOver, at least this isn't
> working for me using the iPhone with iOS7.
>
> If anybody would like to try this using an Android with TalkBack to confirm
> functionality there too, that would be great.
>
> All the best,
> Bryan
>
> -----Original Message-----
> From: James Craig [mailto:jcraig@apple.com] 
> Sent: Thursday, April 24, 2014 11:35 PM
> To: Bryan Garaventa
> Cc: W3C WAI Protocols & Formats
> Subject: Re: What is the expected behavior of scrollable divs within touch
> screen devices, and does ARIA apply?
>
> On Apr 24, 2014, at 10:33 PM, Bryan Garaventa
> <bryan.garaventa@ssbbartgroup.com> wrote:
>
>> I'm not really sure where this would be handled though, would it be with
> the spec, or some spec, identifying a way for browsers to convey a textual
> representation exposed by scrollable regions that can be used by ATs, or is
> it simply a best practice for labeling and defining a region, and is it then
> up to the AT to ensure support for this even though it's not specified
> anywhere?
>
> You could try coming up with an real world example where this is
> necessary-make sure you don't make it an contrived test case-and submitting
> it as a bug report to the various AT vendors. Like all software companies,
> AT vendors have a long list of work they intend to complete, and the more
> *real* you can make the example, the more likely it is to get a higher
> priority fix order. 
>
> James
>
>
>

Received on Saturday, 26 April 2014 09:53:25 UTC