Settings and activity
3 results found
-
230 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 -
23 votes
Hi,
I have escalated the request to the higher management and we have kept it in our radar. You may see it in our near releases.Thanks
RachitAn error occurred while saving the comment 
Mike Craghead
commented
Sorry folks, I didn't see the two posts below from Terri (https://acrobat.uservoice.com/users/773823130-terri) before I added mine, but they're asking for the same thing I am (albeit with a few other items mixed in):
Mike Craghead
supported this idea
·
An error occurred while saving the comment Mike Craghead
commented
At the moment, all remediation of list problems can only happen in the tags panel, which can be tedious.
Couldn't list tools be added to the RO popup? Currently in the GUI it seems to only be able to display lists as <P>, even if they are already marked with <L> in the tags panel.
Ideally we' be able to drag a rectangle around the whole list to make the <L> tag happen, then (if it can't be done automatically) we could drag around list items to make the <LI> (and <LBody).
It would also be nice if the actual structure of the list were visible in the RO panel GUI, so we could catch common nesting errors and correct them there, rather than relying on the tags panel. Even a clumsy AI that plopped <LI> and <LBody> tags under the list would save time, because in the tags panel we could drag pieces around until the list was right, instead of several iterations of "Right-click > New tag > List Item..." which gets pretty old pretty quickly.
Thank you!
-
38 votes
Hi,
I have escalated the issue to the Engineering Team and will get back to you once I get an update on this.Thanks
RachitMike Craghead
supported this idea
·
Re: Bug #2: "<P>PathPathPath..."
Here is a super dumb way past this bug:
In Word, do NOT use File >Save As PDF. Instead,
Go to File > Save As > [choose PDF from the file type droplist] > press Save.
No more PathPathPath!
It's objectively silly that File > Save As PDF should give you different results than choosing the file type manually. It doesn't create an accessibility nightmare like printing to PDF does, but those PathPathPath errors can really add up!
Anyway, I was happy to find this fix, hope you all have similar success with it. But Adobe: do please fix this. Microsoft could help by tweaking their GUI to steer users more intuitively to the right path, but we mustn't count on that!
Couldn't a function be added to Acrobat that seeks out every "<P> PathPathPath..." and kills it with fire? There is no circumstance in which that tag with those contents would be useful. And isn't it all just plain text XML if you're deep enough under the hood, addressable with a little basic find-and-replace logic? I don't know much so I'm just speculating, but it sure looks plausible through my ignorance-colored glasses.
Cheers!
Mike