Re: Web Rotor
Re: Web Rotor
- Subject: Re: Web Rotor
- From: Chris Fleizach <email@hidden>
- Date: Sat, 6 Aug 2011 22:16:29 -0700
What elements do you want to be navigable from the rotor?
I imagine Headings, but are there others...
THe only thing I can think of that might do this now without further API enhancements is to add a UIWebView with your HTML that has an alpha of .0001 or something small and the actual PDF view use isAccessiblityElement = NO
On Aug 6, 2011, at 10:03 PM, Steve H. wrote:
> Hi,
>
> I am currently trying to make my PDF reading/annotation app (iAnnotate PDF) accessible on the iPad.
>
> For tagged PDFs, I am able to get the document structure, and I would like to make this structure available to be navigated using the "Web Rotor" tool in much the same way you can navigate structured Web pages in Safari. However, I can't yet figure out how to do this.
>
> Even if I set my PDF view's accessibilityLabel to be marked-up HTML (constructed from the PDF's document structure), VoiceOver does not seem to treat this as something that Web Rotor can navigate. (Furthermore, it reads the HTML tags as if they were part of the text.)
>
> Does anyone here have any experience with this? Can what I'm trying to do even be done?
>
> Thanks for any pointers or advice you might give me.
>
> Steve _______________________________________________
> 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
| References: | |
| | >Web Rotor (From: "Steve H." <email@hidden>) |