Eugene Tyson
My feedback
35 results found
-
9 votes
-
2 votes
-
611 votes
We have added this feature in our backlog for future release
An error occurred while saving the comment -
27 votes
Generative Alt Text is an opt-out experience and is turned ON by default. The first time an image is placed, InDesign informs you that it could be turned off with a clear CTA.
Closing this as As Designed.
--
Adobe InDesign team
An error occurred while saving the comment This is still marked as "Resolved for User", but the original request has not been resolved.
The core request was never about improving the quality of the generated descriptions. It was about default behaviour, consent, review, and workflow control.
Looking at the 21.4 documentation, the feature remains enabled by default for eligible users:
"This feature is automatically turned on for users with unlimited credits."
Alt text is still automatically generated when images are placed, credits are still consumed automatically, and AI-generated content is still being inserted into documents before the user has chosen to generate it.
The improvements in 21.4 appear to focus on accuracy, regeneration, enterprise controls, and administration. Those are welcome improvements, but they do not address the original request:
Turn the feature off by default.
Allow users to opt in.
Allow generation for selected images or all images.
Require review before generated content becomes part of the document.
Provide straightforward auditing and management of generated descriptions.A feature can be improved without the original concern being resolved.
The request was not "make the generated text better."
The request was "stop automatically generating AI content in production documents unless the user explicitly chooses to do so."
Based on the current 21.4 documentation, that behaviour remains unchanged.
An error occurred while saving the comment Thanks Sunny, appreciate the clarification and the more detailed response.
However, I still think the central concern remains unresolved.
Even if alt text is only generated when an image is placed or replaced, the issue is still that AI-generated text is being added to production documents by default. That is the part many of us are objecting to.
Improving the quality is welcome, but quality improvement does not solve the consent/workflow problem. A better guess is still a guess. In professional workflows, alt text is not harmless background metadata. It is document content. It can be exported, read by assistive technology, reviewed by clients, included in accessibility audits, translated, archived, and carried through regulated or approval-sensitive workflows.
That means it needs the same level of user control as any other content placed into a document.
I also want to push back slightly on the idea that improved handling of icons and graphics “directly addresses” the inaccurate descriptions reported. It may help, but it does not eliminate the risk. We have already seen examples where a keyline/technical element was described as something like a tall blue building, and other users have reported wildly inappropriate or NSFW-style descriptions for graphics. That is not accessibility. That is inaccurate content being inserted under the banner of accessibility.
Making documents more accessible is a good goal. Nobody is arguing against that. But making documents appear accessible by automatically inserting unreliable descriptions is not the same thing. In fact, it can make things worse, because users may believe the accessibility work has been handled when the descriptions are actually wrong, misleading, irrelevant, or inappropriate.
The enterprise admin control is useful, but it does not address individual users, freelancers, small studios, education users, charities, smaller publishers, or corporate users without centralised admin control. Regulated and approval-sensitive work does not only happen inside large enterprise deployments.
The safer design is still:
Gen Alt Text off by default.
Offer to generate alt text when needed.
Allow generation for selected images or all images.
Require user review/approval before generated descriptions become part of the file.
Provide a reliable way to find, audit, edit, or remove generated alt text already added.
I appreciate that 21.4 improves the feature, but this UserVoice request was not only about accuracy. It was about default behaviour, consent, review, reversibility, and trust.
Until AI-generated content is opt-in and reviewable before insertion, I do not think this should be considered resolved.
Related thread:
https://community.adobe.com/questions-671/indesign-generative-ai-options-on-by-default-1561085?tid=1561085&postid=7672456#post7672456An error occurred while saving the comment Another aspect being overlooked here is document integrity.
Traditionally, opening an InDesign file should not materially alter its content unless the user intentionally edits something. With this feature enabled by default, simply opening legacy documents can now result in machine-generated text being added into production assets.
That changes the relationship users have with the software itself.
For regulated or archived workflows, “opening a document” and “modifying a document” are very different things.
An error occurred while saving the comment This is not resolved.
An error occurred while saving the comment That’s a tone deaf reply. The issue isn’t whether there was a checkbox or a CTA once during onboarding. The issue is that AI-generated content is being automatically injected into professional production documents by default — including regulated, government, accessibility, legal, and corporate workflows — and it has already been shown generating NSFW and wildly inaccurate descriptions.
“Users were informed once” is not really an adequate defence when the feature can create reputational or compliance risks months later inside files people may never manually review line by line.
AI alt text as an assistive starting point? Fine. AI silently writing production content by default? That’s the part people are objecting to.
-
3 votes
-
6 votes
-
2 votes
An error occurred while saving the comment I've also tested this and it does provide the results, there's lots of info the thread about it so I won't repeat it here, but seems like a bug to us.
-
3 votes
-
8 votes
-
231 votes
-
296 votes
-
300 votes
Hi everyone,
InDesign provides an option to export and import User Settings, providing users with a smooth and enhanced experience to restore their custom settings if needed. The feature is now available in the latest InDesign 2024(v19.3.0.058)
Helpx article - https://helpx.adobe.com/in/indesign/using/export-import-user-settings-indesign.html
Please let us know your feedback in the comments.
—
Sanyam Talwar(he/him)
-
366 votes
History panel has been added to the latest version 19.5 of InDesign 2024. Please update your copy of InDesign from CCD app to this latest version to start using this new feature.
--
Adobe InDesign team
-
364 votes
Hi,
The ability to add suffix to JPEG/PNG is now available in InDesign’s latest release 19.0. Please let us know your feedback in comments.
—
Sanyam Talwar (he/him)
-
496 votes
Thanks for the suggestion. We have started to explore this feature. Will share more details soon
Thanks
Abhinav -
522 votes
GPU Acceleration on Windows is available with the latest InDesign 2025(v20.4.0.052). Please update to the latest InDesign via the CCD app to get this feature.
The minimum system requirements for using GPU Acceleration on
- Windows are: Monitor with a display resolution greater than 2K
- GPU card with at least 1GB vRAM.
Note on GPU Acceleration: High-resolution monitors are becoming the standard. With the high monitor resolutions, it is getting difficult for the CPU to handle the rendering. This is where the GPU comes into play. Rendering on high-density displays is best handled by the GPU. GPU acceleration makes the rendering of the documents faster while zooming, scrolling, and panning. The enhanced performance from using the GPU in InDesign powers features like Animated Zoom, which make zoom actions smooth and animated.
Based on our internal tests, we found that GPU acceleration provides better performance when the monitor's display resolution is…
-
639 votes
Convert PDF to InDesign (beta) feature is available in InDesign 20.3 Release in English (North America) and English (International) languages.
More details on this feature are available at https://helpx.adobe.com/indesign/using/convert-pdf-to-indesign-file.html
When a PDF is opened in this release of InDesign, an option to submit your feedback on the conversion is shown. Please let us know your feedback.
---
Adobe InDesign team
-
794 votes
-
2 votes
-
23 votes
19 years and 2 months ago it was requested. On Sept 11, 2017 it was put into a future release/backlog production line - 8 years, 9 months, and 2 days... and this is still not implemented.