Several major bugs have been documented by users in the Adobe Community Forums since Acrobat and PDF Maker were updated on September 14, 2021.

They are:

1: Alt-Text from MS Word is not converting into the PDF. Instead, it is dropped and gibberish code is inserted. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017 This violates the PDF/UA-1 standard which requires that every graphic have alt-text that verbally describes the graphic.

THIS IS A HUGE BUG. You essentially have made Acrobat unusable for those who are required by their country's laws to make fully accessible PDFs.

2: Every cell border on every table cell is being tagged as:
<P>PathPathPathPath. This violates PDF/UA-1 because unnecessary visual formatting is not being tagged at Artifacts.
See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

3: The underline on Hyperlinks should be tagged as artifacts. Right not, it appears as one or more "PathPathPath" which is announced by different assistive technologies. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

4: Borders and background shadings on Text Boxes are being tagged as a combination of <Figure>s and PathPathPath. This too is a violation of PDF/UA-1. https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

5: Paragraph borders and shadings: same deal as #4 above.Per the PDF/UA-1 standard, they are visually decorative and should be artifacted. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

NOTE: To be correctly tagged per PDF/UA-1, the borders/shading content should:
— Not appear anywhere in the Tag tree, either as <Figure> or as "Path" in a yellow content container box.
— Not appear in the Order panel.
— Should appear as Artifact in the Content panel.

6: Dragging and dropping elements in both the Tag and Order panels is now broken.

The text cursor doesn't show anymore, and the little black line doesn't show anymore and instead appears several inches away from where it really is. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017 and also https://community.adobe.com/t5/acrobat-discussions/acrobat-pro-reading-order-box-and-tag-dragging-no-longer-visible/m-p/12395226#M329877

And finally...
7: Once this update is installed, users can't revert back to a previous version of PDF Maker because Adobe doesn't allow that in Acrobat like it does with other Creative Suite applications.

So once the update is completed, it makes PDF Maker completely unusable for tagged accessible PDFs.

This affects millions of your government customers world wide, as well as millions of government contractors and millions of academic customers...all of whom are required by their country's laws to make accessible PDFs.

2 sets of sample Word and Matching PDF files are submitted as demonstrations of the problems in the exported PDFs via PDF Maker.

The Cash App payment pending screenshot scam is an easy-to-understand scam that targets unsuspecting users. A scammer poses as a celebrity or sugar daddy and posts a bogus post on social media offering free money. The innocent consumer replies to the post and shares their details, and the scammer then creates a fake screenshot that asks them to send money to confirm the payment. As a result, the scammer receives money from the real victim's credit card.

One of the easiest ways to spot a scammer is to use free online tools that can verify the screenshot. There are also reputable payment services, such as PayPal, which can detect a fake screenshot. You can also compare the screenshot to your bank statement to ensure it's authentic.

How to avoid fake Cash App payment screenshot scams?
Beware of the scammers who use fake Cash App payment screenshot generators and may ask for your money through fake screenshots. These scams are commonly known as "Virtual Credit Cards" and are used by criminals worldwide. These scams usually request money in the form of iTunes gift cards or prepaid debit cards. This is a common way for scammers to obtain your personal information, such as your full name and account balance. The easiest way to avoid this scam is to prevent contacting these scammers and buying any codes they may sell from black markets. You should also check their profiles to make sure they are authentic.

Another common scam involving fake Cash App balance screenshots is fake Cash App pending payment screenshots. The scammer will present this fake screenshot and ask for money to "confirm" the payment. Many victims will send the scammer their Cash App account details. If you think the screenshot is legitimate, double-check to make sure you made the payment.

https://appsmentorship.com/fake-cash-app-screenshot/

When creating a PDF via the "Create PDF" button in the Adobe Ribbon in MS Word, I have noticed that sometimes the hyperlinks are not clickable in the PDF and sometimes they are. I found the pattern and I think it's a bug.

1) If a hyperlink in the DOCX contains an anchor (e.g. www.myfile.com#page=32), then all the linked text after that one in the PDF are not clickable. The anchor in the DOCX also causes the bookmarks in the PDF to render incorrectly from that point on.

2) If a hyperlink in the DOCX is internal, then it disables all links in the PDF. For example, if a sentence says, "For more information, read Appendix B," and you link internally to Appendix B in the same DOCX, then the resulting PDF has zero clickable links. They're all disabled.

If neither of the scenarios above exists, that is, all the links are external and have no anchors, then the resulting links in the PDF are just fine. No problems.

When creating a PDF via the "Create PDF" button in the Adobe Ribbon in MS Word, I have noticed that sometimes the hyperlinks are not clickable in the PDF and sometimes they are. I found the pattern and I think it's a bug.

1) If a hyperlink in the DOCX contains an anchor (e.g. www.myfile.com#page=32), then all the linked text after that one in the PDF are not clickable. The anchor in the DOCX also causes the bookmarks in the PDF to render incorrectly from that point on.

2) If a hyperlink in the DOCX is internal, then it disables all links in the PDF. For example, if a sentence says, "For more information, read Appendix B," and you link internally to Appendix B in the same DOCX, then the resulting PDF has zero clickable links. They're all disabled.

If neither of the scenarios above exists, that is, all the links are external and have no anchors, then the resulting links in the PDF are just fine. No problems.

To ensure that assistive technologies can parse tables, headers that are repeated across pages should be marked as artifacts. This is recommended by the PDF Association's Tagged PDF Best Practice Guide: Syntax: https://www.pdfa.org/wp-content/uploads/2019/06/TaggedPDFBestPracticeGuideSyntax.pdf . However, this structure is not followed by PDFMaker when converting from Word to PDF.

Steps to reproduce the issue
1. Open the attached Word document.
2. Go to Acrobat > Create PDF.
3. Press Save.
4. Open the resulting PDF (also attached).
5. Open the Tags panel (View > Show/Hide > Navigation Panes > Tags).
6. Expand the <Table> tag.

Environment (OS, other related application versions, etc.)
- OS: Windows 10 Enterprise, 21H2
- Acrobat version: Continuous Release 2022.001.20117 64-bit
- Word version: 2204 (Build 15128.20178 Click-to-Run)

Expected result
- The repeated table headers on the second page should not be contained in a tag. They should be marked as artifacts.

Observed result
- The repeated table headers on the second page are contained in <P> tags inside <TH> tags inside a <TR> tag.

A new bug in Adobe.

When combining Word docs (and I believe it may affect other file types), the file name cannot be very long. Not sure how many characters but not very many. This is causing inefficiencies in my work where I publish research articles and the file name contains important information to identify each article. Having to shorten the file name wastes time. If this is an unintentional bug, please fix it!

The error received is "No PDF file was created because Adobe Acrobat encountered an unidentified error". Less than helpful generic message leading me to believe this might be an unintentional bug due to coding changes??

When PowerPoint files are converted to PDF, all shapes containing embedded text that were excluded from reading order in PowerPoint are being tagged inappropriately during the conversion to be read by assistive technology anyway. Tagging and reading order as specified in PowerPoint should be carried over to Adobe PDF, and if text is marked to be excluded from reading order because it is actually decorative, this should be honored in the conversion process. For example, we use callout markers that consist of a solid circle with a number embedded in it (1, 2, 3, etc.). The numbered circles are excluded from reading order in PowerPoint because the screenshot they are marking is already described in brief text on the slide, and the numbers in the circles, by themselves, are meaningless when read by a screen reader. However, when I convert the file to PDF, the numbers in the circles are tagged as readable text for assistive technology.

Yes, Adobe Acrobat Pro supplies ways to manually fix accessibility issues, but we shouldn't have to use it to fix accessibility issues caused by Adobe during the conversion process when the source file was set up correctly for accessibility in PowerPoint, Word, etc.

When PowerPoint files are converted to PDF, slide titles should be converted to H1 because PowerPoint currently does not establish a hierarchy of headings. However, when I test the PDF output with a screen reader, I discover that they are all converted to H2, and there is no H1 anywhere in the file. Adobe Acrobat Pro is flagging this as a heading issue in accessibility checker, but the slides are properly set up with title placeholders on the master layouts, so Adobe is improperly applying H2 to slide titles when no H1 is present. See these WCAG accessibility standards and techniques:

• https://www.w3.org/WAI/WCAG21/quickref/#section-headings
• https://www.w3.org/WAI/WCAG21/Techniques/pdf/PDF9.html

This issue applies to MS Word 365 with Acrobat DC Pro Add-in.
Word version: Microsoft® Word for Microsoft 365 MSO (Version 2201 Build 16.0.14827.20158) 64-bit
Adobe Acrobat DC version: 2022.001.20117
Background story:
When the MS Word 365 Acrobat add-in is used to create a PDF (with create from headings selected in the Adobe preferences), bookmarks are created in the PDF output navigation panel as expected (refer to fig 3), but some of the headings do not link to their correct page when you click on them (they all default to page 1, top of the document). The affected styles are not MS Word headings as such but custom styles with MS Word paragraph Outline Level set to Level 1.
In contrast, if I use the MS Word Save as PDF, the custom outline level 1 styles again appear in the PDF output navigation bookmarks and they all link to their correct pages in the PDF output document.
Three support screen shot files are attached to aid this post as follows:
Fig 1. word-custom template-outline-structure.jpg (this shows the basic structure of the source MS Word document).
Fig 2. word-acrobat-addin-preferences-set.jpg (this shows the Acrobat addin prefrences set to headings).
Fig 3. pdf-output-from-word-acrobat-addin-save-as-pdf.jpg (this shows the pdf output created from the source MS Word document. The Outline 1 style are all those above ‘List of Acronyms’.
This triggers the question, how does Acrobat DC Pro recognize a MS Word 365 style as a heading and what determines how it automatically maps to the correct page. Is this a bug or a feature?