Settings and activity
2 results found
-
231 votes
Hi,
Thank you for raising these accessibility issues. The post mentions about the following six bugs being introduced with the update that went live on September 14, 2021
1: Alt-Text from MS Word is not converting into the PDF. Instead, it is dropped and gibberish code is inserted
2: Every cell border on every table cell is being tagged as <P>PathPathPathPath
3: The underline on Hyperlinks should be tagged as artifacts
4: Borders and background shadings on Text Boxes are being tagged as a combination of <Figure>s and PathPathPath
5: Paragraph borders and shadings: same deal as #4 above.Per the PDF/UA-1 standard, they are visually decorative and should be artifacted
6: Dragging and dropping elements in both the Tag and Order panels is now broken.Would like to mention that out of these, #1 and #6 were introduced with the Sep 14 update and remaining (#2, #3, #4 & #5)…
An error occurred while saving the comment An error occurred while saving the comment 
Mary Spikowski
commented
@Tanvi Rastogi Thanks for your response. I figured out what was causing the problem and the difference between the two documents. The Word document that was causing problems had tracked changes turned on and tracking was locked using a password. When I unlocked tracked changes using the password and turned off tracked changes before creating the PDF, the PathPathPathPath tags were no longer present. While I'm not sure why tracked changes would matter, I am now able to avoid having to manually delete each PathPathPathPath tag in the PDF file so I am happy! Thank you.
An error occurred while saving the comment Mary Spikowski
commented
Here is an example file to show the issue I am experiencing. In File A.docx, you can verify that all four tables (Tables 1-4) have the first row marked "Repeat as header row at the top of each page". However, in File A.pdf, you can see that the accessibility check flags "Tables > Headers - Failed" for Tables 1 and 2, but the accessibility check passes this check for Tables 3 and 4. Why do they appear to be formatted similarly yet produce different outcomes?
An error occurred while saving the comment Mary Spikowski
commented
In order to meet contract requirements at work, I need to convert Word documents into section 508-compliant PDFs on a regular basis. On some of my PDFs, when I run the accessibility check, I am having issues with Tables > Headers - Failed. In my example document, there are 56 tables. Of these tables, 29 are flagged as Tables > Headers - Failed. I can correct this in Adobe Acrobat by doing the following: showing the Tags Panel, opening the first <TR> tag of each problematic table, and changing each tag under that from <TD> to <TH>. However, this is tedious and I would like to make the corrections in Word rather than in Acrobat. Also, I have to regenerate the PDF multiple times as we work with the document so I would prefer to avoid the rework of having to change the <TD>s to <TH>s every time.
Everything I have read tells me I need to go into the Word document, right-click on the table, select Table Properties, click the Row tab, and select "Repeat as header row at the top of each page". Theoretically, after I do that for all of the problematic tables, I won't have this Tables > Headers - Failed issue and all tags for the top row of cells in the table will be <TH>. However, after I completed this for each problematic table in the Word document, the PDF I create is exactly the same and still contains the same 29 problematic tables. Is there something else that needs to be corrected in the Word document to make the Tables > Headers accessibility check pass in Adobe Acrobat?
If this is helpful, the versions I am running are:
Word: Version 2202 (Build 14931.20132)
Adobe Acrobat Pro DC: Version 2022.001.20085An error occurred while saving the comment Mary Spikowski
commented
I recently updated to version 2022.001.20085 in the sincere hope that issue #2 from Bevi Chagnon's original post (Every cell border on every table cell is being tagged as: <P>PathPathPathPath) would go away for me. I was initially excited to see that the PathPathPathPath tags were not added to the first document that I tried. (0/24 tables in the document contained the PathPathPathPath tags.) Excellent! Then I created a PDF of a different document following the exact same process, and unfortunately all 56/56 tables in the document contained the PathPathPathPath tags. Is there any reason why two different documents would do the exact opposite with regards to this particular issue in version 2022.001.20085? Do I need to modify something about the Word document?
Mary Spikowski
supported this idea
·
-
2 votesMary Spikowski
shared this idea
·
I have found a solution to this issue and I wanted to document it here in order to help anyone else who runs across this issue in the future.
https://support.microsoft.com/en-us/office/improve-accessibility-with-the-accessibility-checker-a16f6de0-2f39-4a2b-8bd8-5ad801426c7f#PickTab=Windows
I opened the problematic file in Word, went to the Review tab on the ribbon, and clicked the Accessibility Checker button. The Accessibility Checker identified 29 instances of the "No header row" error. Next to each Table under “No header row” I clicked the Recommended Action “Use first row as header.” After doing this for all 29 instances it identified, when I created the PDF all of the tables passed the Headers check. I have no idea what was different about those 29 tables compared to the other tables in the report, but this appears to be a good way to fix the TH/TD issue in the Word document rather than having to fix it in the PDF. It seems faster to me than the typing required to correct it in Adobe Acrobat.