Klaas
My feedback
114 results found
-
133 votes
An error occurred while saving the comment Klaas
supported this idea
·
-
4 votesKlaas
supported this idea
·
-
5 votesKlaas
supported this idea
·
-
441 votes
Thanks for the suggestion. We have started to explore this feature. Will share more details soon
Thanks
AbhinavKlaas
supported this idea
·
-
710 votesKlaas
supported this idea
·
-
890 votesKlaas
supported this idea
·
-
9 votesKlaas
supported this idea
·
-
16 votesKlaas
supported this idea
·
-
177 votes
Dear All,
Now you can set fonts/typeface directly in InDesign while creating PDF forms. This feature is now available in latest InDesign CC version. Please upgrade to the latest release.
Thanks
Abhinav AgarwalKlaas
supported this idea
·
-
14 votesKlaas
supported this idea
·
-
87 votes
Thanks for reporting. We will review the issue shortly
-InDesign Team
An error occurred while saving the comment Klaas
commented
Hi Adobe.
Any News on this?
The bug report ist quite old and there is no real workaround for this bug.Best, Klaas
Klaas
supported this idea
·
-
12 votes
An error occurred while saving the comment Klaas
commented
@Chad und Adobe: As <Note> can contain a lot of different content, the content inside a note must be tagged appropriate – this can be as <P>, but <L>, <Figure>, even <Table> can be the right choice, too. This is critical and not optional (see ISO 32000 & 14289).
Yes e.g. PAC ist making a <P> inside a <Note> a warning, but we should never build PDFs for having good results in special software.Best, Klaas (PDF/UA TWG Chair)
Klaas
shared this idea
·
-
132 votes
This issue has got fixed in the recently released versions of InDesign, starting with InDesign 2022.
--
Adobe InDesign team
Klaas
supported this idea
·
-
66 votesKlaas
supported this idea
·
-
57 votesKlaas
supported this idea
·
-
110 votesKlaas
supported this idea
·
-
62 votesKlaas
supported this idea
·
-
175 votesKlaas
supported this idea
·
-
6 votes
An error occurred while saving the comment Klaas
commented
Its is a bug, yes. Would be great if fixed.
Workaround: Instead of defining it as artifact in InDesign you can use a preflight correction in Acrobat to artifact al untagged objects. This is much faster.
Klaas
Klaas
supported this idea
·
-
6 votes
Thanks for reporting this issue.
We’ll review this shortly.—
InDesign teamKlaas
supported this idea
·
![*Collective Articles.indd @ 100% [GPU Preview] 2018-09-19 14-46-40.png 210 KB](/assets/203886109/*Collective%20Articles.indd%20@%20100%25%20%5BGPU%20Preview%5D%202018-09-19%2014-46-40.png){kind=link}
@Brennan Wilson
1. Yes, more accessibility issues should be addressed in InDesign
2. MS Words Checker i a help, but not a great one, so i would no use this as a refernece.
3. There are possibility to check, even not from Adobe itself, see e.g. Keith Gilberts "Check document for accessibility" (https://www.gilbertconsulting.com/scripts).
4. Acrobats reading order (or Z-Ordern) is NOT an accessibility requirement in ANY law, guidance. Even if Adobe (e.g. help pages) claims this different. Tags are the only things that matter.
Acrobat should use Tags as basedes for roflow, but thats nothing for the InDeisgn tesm.