Klaas
My feedback
127 results found
-
6 votes
An error occurred while saving the comment An error occurred while saving the comment Klaas
commented
It is never a good idea to put irony in a bug report (discussion). I saw enough things going wrong by misunderstandings…
An error occurred while saving the comment Klaas
commented
" I’m happy to understand that you now say: ‘use an Alt Text, that is read instead of Contents item"
I ask that you refrain from interpreting Frans' comments arbitrarily and instead stick to the facts.
I never said that alt text should be used. That is also completely incorrect from a technical standpoint.Regarding the bug report itself: I sincerely hope that the InDesign team will provide proper support for the PDF 1.7 standard, especially since my colleagues at Adobe share the point of view I have outlined.
If PDF 2.0 will be integrated in IInDesign, there will be indeed beter technical solutions.
An error occurred while saving the comment Klaas
commented
What should this link tell us or proof?
Indeed a good result of testing tools do not 100% proof its perfect conformance.
Running the mentioned ID2025 and ID 2026 tagging structure for link and figure in PAC, PDFix-veraPDF and Acrobat preflight both cases all get a green checkmark in all tools.But that is logical! As i said both ways of tagging are not violating the spec. But as said before, it is assumed that figures substructure will be ignored by AT.
An error occurred while saving the comment Klaas
commented
As written, <Link> inside <Figure> is not strictly forbidden in PDF. So a check will not fail.
But PDF as the PDF 1.7 spec was written a long time ago it is not perfect. As so, there a guidances like the Tagged PDF Best Practice Guide to give hint how to use Tagged PDF the best way.Hope Adobe will listen to the peoeple how wrote PDF/UA and to a opinion given by on person.
Thanks.
An error occurred while saving the comment Klaas
commented
1. As the image is linked, it is semantically appropriate the bring this relation into tagging structure
2. In PDF 1.7 it is not expected substructure of <Figure> to even be available to AT due to the Alt. It is not prohibited substructure for Figure; it is simply assumed that it would be ignored.
3. The was a discussion about this in technical working groups, we all agreed that in PDF 1.7 context the InDesign 2026 ist not correct / practically.And YES Frans, some AT might not give a good output. But InDesign should provide a correct tagging. I hope AT will handle this correctly in the future.
Klaas
shared this idea
·
-
6 votesKlaas
supported this idea
·
-
39 votesKlaas
supported this idea
·
-
8 votesKlaas
supported this idea
·
-
3 votes
Hi Todd,
Could you share more details about the PDF Preset? What were the Color Output settings that are no longer getting applied in 21.0.2, can you show us some screengrabs?
If possible, share the .joboptions file.
--
Adobe InDesign team
Klaas
supported this idea
·
An error occurred while saving the comment Klaas
commented
Indeed there seems to be something wrong.
My CMS settings define "PSO Coated v3".
A new document is set to "Coated FOGRA39".
That should not be FOGRA39, it should tolerate my CMS setting and set PSO Coated V3 as the profile.
If i change the profile, InDesign tells me, that FOGRA39 is my working color space – which is not true.During the export, the correct colour profile is used.
Test with a german InDesign 2026.0.2 on a german macOS 15.7.2.
-
4 votesKlaas
shared this idea
·
-
43 votes
The fix of the issue is now available in the latest InDesign 2026(v21.0.1.006). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application, click on the context menu on the top right, and click on Check for App Updates.
—
Adobe InDesign Team
Klaas
supported this idea
·
-
15 votes
Fixed in Prerelease build 21.1.0.54
--
Adobe InDesign team
Klaas
supported this idea
·
-
32 votes
The fix of the issue is now available in the latest InDesign 2025(v20.4.1.004). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.
—
Adobe InDesign Team
Klaas
supported this idea
·
-
16 votes
The fix of the issue is now available in the latest InDesign 2026(v21.0.0.192). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application, click on the context menu on the top right, and click on Check for App Updates.
—
Adobe InDesign Team
An error occurred while saving the comment Klaas
commented
With the European Accessibility Act coming up, the is now much more critical.
Many Publisher can't use InDesign anymore, as the bug can't be handled within InDesign ans manual fixing in the PDF takes hours.Klaas
supported this idea
·
-
4 votesKlaas
supported this idea
·
-
9 votesKlaas
supported this idea
·
-
13 votes
Hi,
Thank you for reporting the issue. We have been able to reproduce the issue and it is currently under investigation.
—
Adobe InDesign Team
An error occurred while saving the comment Klaas
commented
Any news on this?
I and colleagues need to spend a lot of time fixing this…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
·
-
16 votesKlaas
supported this idea
·
-
3 votesKlaas
supported this idea
·
-
111 votes
An error occurred while saving the comment Klaas
commented
Would be really helpful!
Klaas
supported this idea
·
-
148 votes
An error occurred while saving the comment Klaas
commented
@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.Klaas
supported this idea
·
-
5 votesKlaas
supported this idea
·
-
482 votes
Thanks for the suggestion. We have started to explore this feature. Will share more details soon
Thanks
AbhinavKlaas
supported this idea
·
-
788 votesKlaas
supported this idea
·
Strongly agreed Rainer!
All other tools (e.g. Word )generate an InDesign 2025 and before like structure.