Settings and activity
37 results found
-
2 votes
An error occurred while saving the comment Brennan Young supported this idea · -
3 votesBrennan Young supported this idea ·
-
2 votes
An error occurred while saving the comment Brennan Young commentedThe host system accessibility APIs of Windows, Mac, iOS and Android are right there.
If only Acrobat would actually use them, users would be able to select the assistive technologies they prefer.Brennan Young supported this idea · -
2 votes
An error occurred while saving the comment Brennan Young commentedSome kind of automated PDF/UA compliance checking should be possible. It's crazy that so many manual steps are needed. Some of us have hundreds or thousands of documents to go through.
I have heard the excuses: "Some accessibility issues can't be checked automatically, so we're going to force you to go through manual steps every time".Yes. We are painfully aware of this.
And it's equally true that many *can* be checked automatically, not to mention the tedious effort of manually running the built in "automatic" checks on a per-document basis in Acrobat.
Batch accessibility check feature please.
Brennan Young supported this idea · -
2 votes
An error occurred while saving the comment Brennan Young commentedBetter still, open up Acrobat fully to third party assistive technologies, via the host-system accessibility APIs (available in Windows, Mac, iOS, Android) so users can choose the exact text-to-voice (or text-to-braille, or whatever) presentation they prefer.
Brennan Young supported this idea · -
3 votesBrennan Young supported this idea ·
-
7 votesBrennan Young supported this idea ·
-
3 votesBrennan Young supported this idea ·
-
2 votesBrennan Young supported this idea ·
-
8 votesBrennan Young supported this idea ·
-
3 votesBrennan Young supported this idea ·
-
2 votesBrennan Young supported this idea ·
-
58 votesBrennan Young supported this idea ·
-
17 votesBrennan Young supported this idea ·
-
3 votes
Hi,
Thanks for reporting this. We would recommend you to keep the Acrobat on latest version to experience the new features.
Thanks
Rachit
Brennan Young supported this idea · -
2 votesBrennan Young supported this idea ·
-
3 votes
Hi,
Thanks for reporting the issue. This is fixed in the latest update of Acrobat Pro DC. Please update to the latest version and check.
Incase you face any issue, please connect with us.
Thanks
Rachit
Brennan Young supported this idea · -
819 votesBrennan Young supported this idea ·
-
2 votes
An error occurred while saving the comment Brennan Young commentedI've been around the houses, including PAC, and all the docs on pdfa.org. I am fully aware that Acrobat checker does not check for everything that makes a PDF accessible, and that there's more to PDF UA than what the Accessibility Checker checks for. Yes indeed.
This is all fine.
But is this a rationale for making it difficult (occult, even) to add the PDF/UA tag? It's not impossible, it's just hard. Why?
Is this a rationale for failing to documenting the feature adequately?
If I put a DOCTYPE declaration at the top of HTML, it doesn't mean the code is valid!
Similarly, a PDF/UA tag may be added to *any* PDF file, regardless of the true accessibility conformance level. Why pretend otherwise? I see these flags as a commitment: - "judge the document against this standard" rather than "this document is 100% conformant".
Again, I raise the use case of adding the PDF/UA flag to multiple documents which have already been checked "upstream" - i.e. the files are generated by a process whose output has already been constrained to produce well-formed PDF/UA content. This can indeed be formally checked, e.g. if the "upstream" code includes appropriate tests.
And I raise the use case of files that have already been checked/tweaked manually with Acrobat, saved with the PDF/UA flag, closed and then reopened.
If the flag truly indicated conformance, Acrobat would not "reset" the accessibility checks of those documents. It would just read the flag and say "passed".
It can't be both ways. Either the flag is some kind of guarantee of conformance (in which case Acrobat should respect that when opening the file), or it's a promise to follow a standard, in which case Acrobat should just add the flag on saving in the relevant format(s).
Brennan Young supported this idea · -
8 votes
Hi,
Please share a pdf file so that we can check the issue and resolve it for you.Thanks
RachitBrennan Young supported this idea ·
This problem would disappear completely if Adobe would only use the host system accessibility APIs to handle text-to-speech. Why reinvent the wheel?