Re: otherwise accessible objects not in proper order
Re: otherwise accessible objects not in proper order
- Subject: Re: otherwise accessible objects not in proper order
- From: Chris Fleizach <email@hidden>
- Date: Fri, 15 Jun 2012 17:49:40 -0700
It's hard to say what's happening. I'd suggest filing a bug and including your sample if possible.
If that's not possible, perhaps sending a screenshot.
On Jun 15, 2012, at 11:16 AM, Scott McCormack wrote:
> Hi all,
>
> I have created a view that uses a UIScrollView to present data in a
> mix of UILabels, UITextBoxes and UIWebViews. The views are being
> resized and moved at runtime to fit the content being displayed, the
> UIWebViews and UITextViews are expanded to the needed size and have
> their own scrolling abilities disabled so the user only has to scroll
> the main UIScrollView. I also have 3 UIViews I've pressed into service
> as accessible containers for a collection of information.
>
> Everything works as expected but I've got an odd accessibility problem
> that I've seen in other applications where some objects either do not
> appear in the left/right swipe order or appear out of sequence. Here's
> the layout of this screen:
>
> Navigation Bar
> <Scroll view start>
> UILabel1
> UIWebView1
> UIView1 UIView2 UIView3
> UILabel2
> UITextView1
> UILabel3
> UITextView2
> UILabel4
> UIWebview2
> <scroll view end>
> tab bar
>
> When the view is initially displayed the object order most of the time
> goes like this:
> UILabel1, UIWebView1, UIView1, UIView2, UIView3, UILabel2,
> UITextView2, UILabel3, UITextView2, UILabel4, tab bar
> - in this case everything is fine except the last UIWebView is skipped entirely.
> - In some cases the 2 UITextViews were also skipped but this seems to
> have stopped after I disabled scrolling for these controls
> - If you manually focus UIWebView2 with VO it will read just fine but
> it will replace UIWebView1 in the the navigation order so now it goes
> UILabel1, UIWebView2, UIView1... and this persists until you focus
> UIWebView1 or use the status bar to scroll the UIScrollView back to
> the top.
>
> Any thoughts on this? I see embedded UIWebViews all the time and they
> seem to mess up accessibility order a lot.
>
> The second part of my question relates to this screen on the iPad. On
> the iPad the layout is mostly the same except for the 2 textviews and
> their labels which on the iPad look like this:
>
> UILabel2 UIlabel3
> UItextView1 UITextView2
>
> When navigating with next/previous swipe it reads UILabel2, UILabel3,
> UITextView1, UITextView2 where I'd rather it read UILabel2,
> UITextView1, UILabel3, UITextView2. Now I already know I could put the
> label and textviews inside a view and make the view the accessible
> object (I'm already doing this with the three UIViews) but I don't
> want to do this with this control as it contains a lot of text and I
> don't want to add the label text on top.
>
> --
> Scott McCormack
> Senior Accessibility Consultant
> SSB BART Group
> email@hidden
> (415)624-2712 (o)
> (415)624-2708 (f)
> www.ssbbartgroup.com
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Accessibility-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden