Re: Web Rotor
Re: Web Rotor
- Subject: Re: Web Rotor
- From: "Steve H." <email@hidden>
- Date: Sun, 07 Aug 2011 01:56:01 -0400
Hi,
Thanks for responding.
The PDF standard specifies several standard block-level structure types that may be used, including headings (H1-H6) and paragraphs (P), list elements, and tables. There are also many inline structure types (such as span, quote, note, annotation, link, BibEntry, etc.) and grouping elements (such as document, part, div, section, block quote, caption, etc.).
Not all of these map directly into HTML, but for the most part, it is a fairly straightforward mapping. For iAnnotate, we don't need to support navigation using all of these either, but I was hoping to at least get the headings and paragraphs.
One issue with using a UIWebView facade is that for huge PDFs (we often deal with e-books in PDF format that have hundreds or even thousands of pages), it is probably not practical to create a single NSString or NSData to hold the entire document structure at once. (I guess this option could work though if there was a way to hack it to use an NSInputStream instead, or even simulate a server that serves the HTML to the UIWebView. But I'd obviously prefer not to hack so much if I don't have to!)
In my experimenting, I've noticed that VoiceOver's rotor tool is smart enough not to give the "lines" option if there are no newlines in the text of the accessibilityLabel field. So I was hoping that it did some sort of parsing on that field that might trigger it to give *more* structural options (perhaps when combined with the right settings for some traits). As I mentioned, I tried to do this by adding HTML tags (e.g., <html> and <body> wrappers), but I guess I'm probably not going to get lucky.
I guess maybe I'll want to put in a feature request for the accessibility APIs to be extended.
Thanks again for your response!
Steve
On 2011-08-07, at 1:16 AM, Chris Fleizach wrote:
> 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