Apart from Sierra users who have experienced problems with PDFs, most users will be best served by delaying updates. #1627: iPhone 14 lineup, Apple Watch SE/Series 8/Ultra, new AirPods Pro, iOS 16 and watchOS 9 released, Steve Jobs ArchiveĪpple has released small updates for all of its operating systems to address bugs and security concerns.#1628: iPhone 14 impressions, Dark Sky end-of-life, tales from Rogue Amoeba.#1629: iOS 16.0.2, customizing the iOS 16 Lock Screen, iPhone wallet cases, meditate for free with Oak.#1630: Apple Books changes in iOS 16, simplified USB branding, recovering a lost Google Workspace account.#1631: iOS 16.0.3 and watchOS 9.0.2, roller coasters trigger Crash Detection, Medications in iOS 16, watchOS 9 Low Power Mode.WebView.loadHTMLString(htmlString, baseURL: nil) Let webView: WKWebView = WKWebView(frame: CGRect(x: 0, y: 0, width: 595.0, height: 842.0), configuration: WKWebViewConfiguration()) Please note this project is specifically written for macOS and I cannot use the iOS libraries for PDF generation. I had programmed and used a software for a year without problems but after updating to Monterey and updating XCode, the following, simplified Playground example of the process always fails and I cannot figure out why. Regarding the accessibility of the output, is there any difference between "Save as PDF", "Export PDF" and "Print to PDF" in Apple's software? I assume this means some conformance with the PDF/UA 1.7 spec? Are there any omissions in support for the PDF/UA standard by this route? What are those omissions? I understand that Pages, Numbers and Keynote all produce tagged PDF. How might HTML semantics be mapped onto PDF/UA output, when saving a web page as PDF from Safari, given that there is not 100% parity between the two semantic systems?Ĭan I browse PDF/UA files in Acrobat Reader with VoiceOver? If not, why aren't Apple and Adobe taking steps to fix this situation? a "tagged PDF" file with the PDF/UA flag)? If I save a PDF from Safari or Preview, do I get a well-formed 'accessible PDF' (i.e. 'next heading' keyboard shortcut, or using the rotor). How does this work? Did Apple invent new names for these features, or is it simply unsupported?Ĭan I use VoiceOver to browse a well-formed tagged PDF/UA file 'semantically' in Safari? (E.g. I've studied the latest documentation for PDFKit and can find no mention of semantic tagging, read order or the PDF/UA format in general. Lawyers with an interest in accessibility suits should take note. Legally speaking, this information should be absolutely clear in the VPAT for Mac OS. Basically it's not enough that a file format (such as PDF) or an app (such as Safari) is hypothetically accessible, if I can't actually browse my PDF in Safari using Voiceover. This term has a formal definition in the WCAG spec. I will mention some important jargon used in the accessibility community: "Accessibility supported". browsing a PDF with VoiceOver in Preview), but I've started to get some acceptable, but patchy results.Īpparently things have changed under the hood since the extensive outcry at High Sierra's implementation of PDFKit but what exactly has changed? Is there a change log anywhere? Did any of the notorious PDFKit bugs from 2017 get fixed? For a long time it seemed that nothing worked (e.g. I'm finding it extremely difficult to find accurate and up-to-date information about support for accessibility with PDF on Apple's platforms, in particular Safari and Preview on iOS and Mac.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |