Settings and activity
37 results found
-
8 votes
Brennan Young
supported this idea
·
-
4 votesBrennan Young
supported this idea
·
-
2 votesBrennan Young
supported this idea
·
-
1 vote
An error occurred while saving the comment -
7 votes
An error occurred while saving the comment Brennan Young
commented
I don't think we can assume that H1 will be at the top, even if that might be true/preferred a lot of the time.
The "most correct" approach is to shift left, and make sure the document is authored with the correct structure and semantics (e.g. in inDesign, or Word or whatever). However, this is not always possible or practical.
I think that we need better tools to make these kinds of time-consuming repetitive changes over multiple pages/documents.
Scripting interface for Acrobat please! Then we can make our own tools, tailored to our own content.
-
10 votes
An error occurred while saving the comment Brennan Young
commented
Why is this tagged as an accessibility issue?
-
3 votesBrennan Young
shared this idea
·
-
14 votes
Hi,
Thanks for contacting us. Can you please provide some sample files with the PAC3 checker results so that we can check the difference and proceed accordingly.Thanks
RachitBrennan Young
supported this idea
·
-
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 Brennan Young
commented
These new bugs may put Adobe customers in legal difficulties, which in turn may become a serious legal problem for Adobe. It is especially bad that users can not downgrade to an earlier version which does not have these bugs. Drop everything and get this fixed ASAP, please.
Brennan Young
supported this idea
·
-
21 votes
Hi,
Thanks for connecting with us. I went though all the requests suggested by you. I would like to inform you that :
For #1, Shortcut keys exist for Pause, Play like Ctrl+Shift+Y/V/B.
For #2, the feature is supported. Click on any paragraph after enabling Read Out Loud and it will read the paragraph. For specific content read, we have informed the management and have been kept in radar for future improvements.
For #3, you can add the voices though system language setting and the voices will be visible in Acrobat if they exists on system.
For $4, we have informed the management and have been kept in radar for future improvements.Try the latest enhancements and features on the latest version of Acrobat Pro DC.
Thanks
RachitAn error occurred while saving the comment Brennan Young
commented
The correct thing to do is to ditch "Read Aloud" entirely, and instead support semantic tags so that the reader feeds an accessibility tree to the host system's accessibility API.
Then users can choose whatever assistive tech they prefer (or have to use, because of their particular disability).
I have made a feature request about this. Please vote for it.
-
16 votesBrennan Young
shared this idea
·
-
3 votesBrennan Young
supported this idea
·
-
5 votes
Hi,
I understand the issue faced by you. Read Out Loud is not a screen reader provided by Acrobat but a feature to read the pdf.
You can user VoiceOver on MacOS which is a Screen Reader supported by Apple. You can easily find the shortcuts at https://www.apple.com/voiceover/info/guide/_1131.htmlI hope this would help you in resolving the issue.
Thanks
RachitBrennan Young
supported this idea
·
-
9 votes
Hi
Thanks for your feature request. We have taken a note of your request and this will be prioritized based on other backlog items.
Thanks
TanviBrennan Young
supported this idea
·
-
5 votes
Hi
Can you share the steps by which do you want to create a PDF/UA file?
Acrobat already has an option to fix tagging issues in the PDF to make it PDF/UA compliant using Tools > Preflight.Thanks
TanviAn error occurred while saving the comment Brennan Young
commented
The problem is not 'broken tags' it's 'no tags at all'.
Adobe PDF Print simply does not generate PDF/UA files from the browser. (Browser may be failing to generate an accessibility tree, which is not Adobe's fault, but reflects badly on PDF as an accessible and portable format)
Semantics are entirely lost when you create a PDF using the Adobe PDF print gadget.
The use case is:
Make (or visit) a WCAG compliant HTML5 page in any browser that supports Adobe PDF print.
Print the page to PDF using Adobe PDF print.Expected Result - Semantics converted to corresponding PDF/UA tags in output
Actual Result - Non-tagged PDF is outputBrennan Young
shared this idea
·
-
45 votes
Hi Joel,
We are always working to make it a better of experience for our accessibility customers.
We’ll be adding the support of Undo/Redo in order panels and Reading Order Tool in our coming releases.
Can you please tell me why you need the Tags Panel and Reading Order to be merged.Thanks
Rachit.An error occurred while saving the comment Brennan Young
commented
"We are always working to make it a better of experience for our accessibility customers"
Does that include the Mac version? I can't get any PDF viewer on Mac to play properly with VoiceOver, expecially including Acrobat Reader.
As long as this goes unfixed, Adobe are choosing to make PDF unviable in various jurisdictions, including USA, Canada, EU, UK and others, because accessibility compliance is now mandatory in these regions, for the public sector at least, and there is legislation for the private sector on the road map too. Laws have already passed about accessible digital content in France for larger firms. Wake up Adobe!
-
1 vote
Hi,
Since I haven’t heard from you, I believe the issue is resolved.
Please feel free to contact us in case of any issue.Thanks
RachitAn error occurred while saving the comment Brennan Young
commented
How are you viewing the file? PDF viewers for Browsers and Acrobat on Mac do not expose any accessibility tree.
I downloaded it and opened it in Acrobat on Windows, and the reading order looked fine (for a RTL language like hebrew, at least), and the accessibility Full Check had only 2 minor issues calling for manual checks..
However, Acrobat complained about missing tags when I started up NVDA, which I find odd. The tags are definitely there.
.png){kind=link}
if only Acrobat had a scripting interface, like Photoshop and Illustrator