Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
a_C_student
Engaged
a_C_student
Engaged
Activity
‎Feb 28, 2021
08:11 AM
Hi towcts, OCR won't work on a document that is already text. If it did somehow run, I'm afraid it would do nothing to solve the searching problem. Something is wrong either with the document or (more likely, I think) the user's workflow. I would try recreating the PDF from Word using the PDF Maker plugin, or if the plugin isn't available then Save As PDF. If the search still doesn't work, what exact steps is the user doing to perform the search?
... View more
‎Nov 13, 2020
11:47 AM
Usually the PDF generator works better for me, but not always. If I get screwy results I try "Save As". Also, sometimes converting w/o tags then auto-tagging in Acrobat works best. And, sometimes it is easier to hand-tag from scratch.
... View more
‎Nov 07, 2020
08:05 AM
It is really best if your tables are easily understandable without having to use a table summary. Consider simplifying the table structure. If a summary is needed, better to include it in the visual text of the document. Most AT ignores the table summary even if it is present.
... View more
‎Oct 31, 2020
10:14 AM
4 Upvotes
I've run into the Inconsistent Entry error a couple of times. After much trial and error, I think a found a fix - it is kinda goofy and I'm not sure it always works, but it worked for me both times. In the Page Thumbnails pane, select all the pages and Extract Pages as Seperate Files. Open the first page, then back in the Page Thumbnails pane, add all the other pages back in. Somehow deconstructing then reconstructing the PDF fixed the mystereous Inconsistent Entry error. Re. the "Entry for given MCID missing" error - I don't recall running into that one. Maybe cross your fingers and try this ... Tools - Print Production - Preflight. Make sure Acrobat Pro DC 2015 Profiles is selected in the Libraries window at the top Select the "Make individual corrections" tool (the wrench icon). Enter StructElem in the search field and carry out the correction "Insert missing Type entry in StructElem objects".
... View more
‎Jun 27, 2020
12:19 PM
1 Upvote
"Acrobat doesn’t actually test against WCAG 2.0, PDF/UA" . . . is this true? Yep. The accessibility checker built into Acrobat Pro is not very thorough. It checks against a subset of WCAG. The CommonLook PDF validator is much more thorough, tests against WCAG and/or PDF/UA, and is free. Unfortunately in my experience it gives too many false fails. Another choice is the PDF Accessibility Checker (PAC 3) from Access for All. It is free and very thorough in checking against PDF/UA. It does not claim to check against WCAG but as far as I know all WCAG criterea that can be auto-checked are also covered by PDF/UA. My preference is Acrobat for a first-check and PAC 3 for final check. Gotta remember though that many WCAG and PDF/UA criterea can not be auto-checked but rather require careful, knowledgeable human inspection. PAC 3 includes a logical structure view and screen reader emulator that facilitate human inspection. Re. tags changing on thier own - would need to know more specifics or to look at an example document. It may be that these problems go away as you gain experience, or your PDFs may be possessed by evil poltergeists (yep, it happens).
... View more
‎Jun 25, 2020
07:52 AM
Hi Jesper, I would try ... Use the Reading Order tool, select the misbehaving content element, and "Tag as background/artifact". Or, in the Content Pane, drag the content element out of whatever container it is in, if any, right-click it and "Create Artifact". Hope this helps. If not, please post.
... View more
‎Jun 19, 2020
11:30 AM
2 Upvotes
When this happens to me the vanished content is not actually gone, just hiding behind another content element. I open the Content pane and move the hidden content element to be after the hiding content element in the container structure.
... View more
‎Jun 17, 2020
06:03 AM
2 Upvotes
Hi reperella, the free NVDA screen reader and/or the screen-reader-emulator built into the free PAC 3 from Access for All are much better choices than Read Out Loud for acessibility testing. Regarding the use of imperfect PDF-maker tools - perfectly OK IMHO, just gotta be willing to do a bit of extra work after PDF conversion to get an accessible final document.
... View more
‎Jun 15, 2020
11:13 PM
OK, so next thing would be to extract the troublesome page from the document. Try tagging the page on its own then adding it back into the document. If that doesn't work (it usually does work, in my experience) - desperate measures may be needed. I would create a blank PDF page, use the Move or Make Changes to Object tool to copy all of the content from the troublesome page to the new page, then tag the new page.
... View more
‎Jun 14, 2020
12:43 PM
The first think I would try is ... In the Content pane, drag the content out of the container and delete the then-empty container. Then, use the Reading Order tool to re-tag the troublesome content. Hopefully (and usually, in my experience) a new tag and container will be created.
... View more
‎Jun 04, 2020
02:16 PM
I would look carefully through the tag tree (in the Tags pane) to check for <Figure> tags that are improperly nested under other <Figure> tags - and drag them to their proper place in the tag order. If the error persists I would do the same thing in the Content pane.
... View more
‎Jun 02, 2020
06:19 PM
Hi Laura, you might try testing with PAC3. In my experience it does a better - though not perfect - job of isolating these errors. It highlights the first character encoding culprit, so I can fix it (usually by deleting the faulty character unless it is needed in the reading order). I have to retest to find the next culprit, then the next, and so on. So - not perfect but for a short document or one with just a handful of these errors it works.
... View more
‎Jun 02, 2020
06:12 PM
"USA laws recommend WCAG 2.0/2.1". Yep. So, if you know that your users are all USA-based, and that you will only ever be held accountable to USA rules, you're good to go by conforming to WCAG. But the world does not end at USA borders. If your users might include some outside the USA, most will look to PDF/UA - the offcial world-wide standard for PDF universal accessiblity. And, really, there is no reason besides a bit of inconvenience not to conform to both WCAG and PDF/UA. Each includes a few good things that the other leaves out, and in no case do the two contradict. So - really no reason to chose between the two.
... View more
‎May 28, 2020
04:38 PM
Ditto Bernd Alheit, Unfortunately accessibility does not happen by magic. Full WCAG and/or PDF/UA conformance *always* requires some amount (sometimes a little, frequently a lot) of knowledgeable human inspection and remediation.
... View more
‎May 21, 2020
12:53 PM
1 Upvote
Bevi is dead on - as usual. Read Out Loud is not for accessibility testing (nor for anything else useful as far as I can tell). An alternative to JAWS or NVDA - which are great but have a learning curve - you may want to consider a screen-reader emulator like the one built into PAC 3 from Access for All - it is free and Google will easily find the download.
... View more
‎May 12, 2020
11:18 AM
Tools > Print Production > Preflight (make sure Acrobat Pro DC 2015 Profiles is selected at the top of the Preflight dialogue) > Select Profiles (the toolbox icon) > Under PDF Fixups, select Flatten annotations and form fields (just be aware this will flatten links as well as form fields).
... View more
‎Apr 30, 2020
12:04 PM
Some things to try (if you haven't already done so) ... Ensure your document has text, not a picture of text (e.g. scanned); Close and restart Acrobat; Ensure Acrobat is up to date; Restart PC. Once in a while Acrobat goes wonky on me and one these steps usually fixes things.
... View more
‎Apr 30, 2020
11:52 AM
2 Upvotes
This is a beautiful example of the need for Universal Accessibility, i.e. conformance to ISO 14289 PDF/UA. Only when *every* AT tool for *every* platform and *every* PDF document rigourously conforms to the same set of rules can we expect an accessible PDF to be always read properly. Acrobat Pro is capable of producing PDF/UA conforming documents, but it takes a considerable amount of human knowledge, skill, practice, and effort. Adobe could do much to make it easier/more practical. That said, if a document is fully conforming with PDF/UA and is not read properly be a specific tool, the tool, not the document, is broken, and the tool maker needs to fix it.
... View more
‎Apr 12, 2020
03:44 PM
Kinda depends on what you mean by "Excel style". You can create a fillable table - basically a table of form fields - with limited functionality. It would be extremely difficult or impossible to duplicate full Excel functionality in a PDF.
... View more
‎Apr 12, 2020
03:35 PM
Make sure the PDF conforms to WCAG 2.0 and preferably to ISO 14289. Text will scale just fine - provided it is real text, not an image of text. If you are working with an image of text, OCR it first.
... View more
‎Apr 12, 2020
03:30 PM
One trick for dealing with misbehaving tables is to create a seperate, temporary <Table> tag. Move each row, one at a time, under the temp <Table>, make sure that row is tagged exactly right - including any empty <TD>s, spanning, IDs, etc., then move on to the next row. You also might try downloading the free PAC 1.3 from Access for All (google should find it) - it is obsolete for automated testing (use PAC 3) for that, but has a superiour screen-reader-preview, especially for working with tables. You might also consider evaluating CommonLook. It has a reputation for being excellent at helping with PDF table accessiblity - it is expensive, by the way.
... View more
‎Feb 19, 2020
09:39 AM
1 Upvote
Without seeing the document I can't be sure, but those look like enumerated paragraphs, not list items. I would tag the paragraphs with <P>. Tagging enumerated paragraphs as a list will make the document more difficult for an AT user to navigate. Simple heading and paragraph tags are easier to navigate.
... View more
‎Feb 13, 2020
06:23 PM
2 Upvotes
Again, sorry. There must be something that I'm not getting. There is no password to change. You enter a password each and every time you protect a document. You are in no way stuck using a forgotten password - just set the password to whatever you want for each document that you protect. You can use freemypdf.com to try to unlock your previous protected PDFs, but it has nothing to do with your password going forward. Your password going forward is selected for each document and can be different for each document.
... View more
‎Feb 13, 2020
11:08 AM
Sorry for being dense, but I still may not understand. You want to restrict editing but not opening/viewing. The process is similar to the steps I mentioned before, File > Properties > Security > Set Security Method to Password Security, then ... Again, you can enter any password you like. Unlike protection from opening a document, protection from editing is not real encryption. It is notoriously weak and can be easily defeated using a free service like freemypdf.com (at least in my experience).
... View more
‎Feb 13, 2020
10:19 AM
I'm not sure I understand your question. In Acrobat, File > Properties > Security > Require a password to open the document > Document open password. Then, enter any password that you are certain to remember. I use an encrypted Word document to store my many passwords (or hints). That way I only have to be certain I remember the password to the Word document.
... View more
‎Feb 10, 2020
10:58 AM
This may help ... https://taggedpdf.com/508-pdf-help-center/link-annotation-is-not-nested-inside-a-link-structure-element/
... View more
‎Dec 02, 2019
01:01 PM
1 Upvote
Please do not use Read Out Load to check accessiblity. Use real assistive technology like NVDA or JAWS, or a real accessibility testing tool like PAC3.
... View more
‎Nov 09, 2019
12:39 PM
Please do not use Read Out Loud for accessibility testing. Use real assistive technology like NVDA (free) or JAWS (expensive), or a screen reader emulator like the one built into PAC3 (free).
... View more
‎Nov 08, 2019
02:36 PM
Have you checked to see that the document language property is set correctly, and not over-ridden in the tag structure? "however they read left-to-right" - read by what? Are you using real AT like NVDA or JAWS
... View more
‎Nov 05, 2019
02:38 PM
If I understand correctly what you are trying to do, here's a suggestion ... Type the text into Word or other editor. Save as PDF. In Acrobat Pro, make any needed corrections to ensure the text is tagged properly and the PDF is otherwise accessible. In the scanned PDF, mark all content as background artifacts. In the Page Thumbnails pane, insert the file containing the accessible text (right-click the first page > Insert Pages > From File. In the Content pane, ensure the accessible text is positioned before the scanned stuff in the content order. The idea is to hide the accessible text behind the scanned stuff. The visual representation will show just the scan, but AT will read the tagged text.
... View more
Copyright © 2025 Adobe. All rights reserved.
AdChoices