Look at a simpler case: the number of otherwise fairly up-to-speed designers who come here absolutely baffled as to why their PDF isn't working, and all but clueless on the "all PDF readers are not the same" issue. Mostly above my pay grade, but good arguments. I hope I've conveyed how critical this problem is for a many millions of our citizens, worldwide, not just here in the US. 508, ADA, IDEA, and several Titles in our equal access to education laws).Īll the browser manufacturers have to do is just respect the user's peference settings. So this issue of browsers hijacking the user's default preference settings is likely to become a lawsuit because this is a form of civil rights discrimination defined by various US laws (Sec.
#XOJO WEB FILE OPEN SOFTWARE#
But instead, Google Chrome, Microsoft Edge, FireFox, and the other browsers override the user's settings and hijack the PDF into their software browser. If a computer user has set their computer to always open PDFs in Adobe Reader, for example, then that should be the end of the story. Imagine this: close your eyes, click on a link to read your bank statement, and.nothing. All they get is silence and are left lost in cyberspace. It's pure silence with no announcement by any of their technologies that a PDF opened in MS Edge and is not accessible to their screen reader. When a PDF opens in a browser, they don't even know what happened. Another side of my family has the gene for macular degeneration and eventually becomes fully blind between their 30s and 70s. His screen reading software can't read a PDF when it opens in a browser. He has 20/20 vision and severe dyslexia, and he's not counted in the estimate of those with disabilities. He has always had difficulty reading, and even more so now that so much is read on screens.
#XOJO WEB FILE OPEN FULL#
And that's an educated estimate I expect is actually lower because many people don't identify as having a full disability. So lets adjust the number to 80% of the population can successfully read a PDF when it opens in a browser. By 20% of the population has difficulty reading a PDF in a browser because they have a disabililty (vision, low vision, cognitive, etc.) and must use their assistive technology to read content on computer screens.Īssistive technologies can read webpages in a browser, but not a PDf that is opened in a browser. Many people are just fine with opening PDFs in a browser and to be honest, there's really nothing wrong with that for 99% of the population. Again not too much of an option in my case. The only solution that worked for me, was to add an action in Acrobat ("jump to page view") that let me scroll to the requested page and define it as destination. I tried ".pdf#page=3" like I would do with hyperlinks on the web, but that doesn't work.
I'm failing in specifying the jump page in the referenced pdf file. In Acrobat I could specify another action "Open file" which would open the file as requested in Acrobat, but I can't find that in ID to do that trick.Ĭhanging all links in Acrobat is not an option as I would have to do it, after every export of the document. When checking the link in Acrobat, it reads as action "open web link" (in my case in german "Webverknüpfung öffnen"). I'm able to define hyperlinks in ID to the referenced files, but they keep opening in the default web browser. After publishing it (pdf) I would like to be able to directly click on the link to open the referenced file in Acrobat.Īt best, I can even specify the page where to jump to. I have an ID-document with about 100 references to pdf-files. I already watched several youtube-clips and read quite some forum posts, but wasn't able to find a sound solution to my issue. I'm having some difficulties creating hyperlinks in my document.
0 kommentar(er)
