Skip to content

Anonymous

My feedback

8 results found

  1. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Still the Links panel moves…!

  2. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Lets look at specifications and ISO:
    A Figure tag is a Block element
    A Link is an Inline (Child) element

    A Figure with nested Link will pass any machine checker (PAC, CL , VERA)

    Nest a Figure in a Link will make Link Block and Figure Inline.
    PAC will flag it as error.

    As there is nowhere it says that a Figure with nested Link is forbidden, there is nothing wrong with this, it will read correctly, it will pass the rules and will save time in remediation.

    Therefore the change in InDesign is a good change.

    But by all means, convince Axes that their pdf/ua check in PAC and AxesPDF is wrong.

    Contents item for Links is however defined. But is not read by any AT omitting information to the end user. Alt text, however, is read but it is not how it is specified.

    I know ‘someone’ wrote on LinkedIn you do not even have to test in AT, that I can not take very seriously as then you have no idea what in reality works for the end user we are all remediating for.

    An error occurred while saving the comment
    Anonymous commented  · 

    “ 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.”

    You really should learn to understand irony 🥴😆

    An error occurred while saving the comment
    Anonymous commented  · 

    “ But as said before, it is assumed that figures substructure will be ignored by AT.”

    What really IS ignored by AT (at present) is the Contents item on Links, I’m happy to understand that you now say: ‘use an Alt Text, that is read instead of Contents item, think about the end user.’ But then again, I’m sure you won’t…
    Anyway, my last reply here, I’m done with this discussion. Adobe, thanks for the change, most of use feel it is a oke change.
    Lets wait for support for PDF2 and pdf/ua2, seems a better idea.

    An error occurred while saving the comment
    Anonymous commented  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Klaas, it works, it is allowed and passes machine checks. It is fine, just give it a rest and focus more on actual user accessibility experience than technocratic rules (you won’t, I know).
    Please Adobe, keep this change as it is perfectly allowed this way.

    An error occurred while saving the comment
    Anonymous commented  · 

    This is NO bug but intended. Both are allowed and the change means Placement Block/Inline is now correct. A good change.

  3. 16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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
    Anonymous commented  · 

    Very, very, very bad. Only workaround for now: do not split...
    I logged this one today: submitted with bug ID: ID-4263992

    Anonymous supported this idea  · 
  4. 47 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    This option was updated in InDesign 20.0 version to match industry standards and stay consistent. We standardized this behavior to make workflows more predictable across products. 

    We know that changes can take some adjustment, and we appreciate the feedback we received. Over time, users have adapted to this new behavior, which helps us maintain consistency and avoid confusion in future workflows.

    We appreciate everyone’s input and your help in making InDesign better!

    —

    Adobe InDesign Team

    Anonymous supported this idea  · 
  5. 165 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We have made some Performance Improvements in the latest InDesign Release 2025 (Version 20.1), available via Creative Cloud Desktop application. This issue has also been fixed as part of performance improvements.

    Please let us know if you still face slowdown while doing basic operations in this latest InDesign release.

    --

    Adobe InDesign team

    Anonymous supported this idea  · 
  6. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Open the document only from the Book panel. If you simply open the document itself instead of the Book panel you will see this behaviour. It is expected behaviour.

  7. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Disable the app utility Magnet (app for Window snapping) it is determined to be the cause.

  8. Distorted Text and Graphics in high sierra

    221 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Closed: Fixed  ·  Sumit Garg responded

    This is a macOS10.13 issue, specific for some Intel GPU cards. Apple has fixed(partially) this issue inside macOS10.13.4 released build.

    Following are the workaround for resolving this issue.
    1) Update your mac machine to latest macOS10.13.4. Here, Apple has fixed this issue to some extent. You will face very less number of rendering issues.
    2) Disable GPU preview and set display performance as typical.

    Once you have updated to macOS10.13.4 .You might still face some rendering issues. Since, Apple has not fixed this issue completely.
    Please switch off GPU rendering for these cases and report a separate post for tracking.

    An error occurred while saving the comment
    Anonymous commented  · 

    Just turn off GPU rendering in the Preferences, no biggie. It makes no to very very small differences in screen speed redrawing or scrolling.

Feedback and Knowledge Base