94 results found

1. Multi-level lists

   1. VERSION: 19.4

   2. ISSUE: If you create a multi-level list (1, 1.1, 1.2.3, etc) and export as an accessible PDF the list structure is not correct and presents the incorrect "List level" to the reader when using any assistive technology.

   EXPECTED RESULTS: When a new level of a list is created the sublist's <L> goes INSIDE the <LBody> tag to properly indicate the list is sublevel.

   ACTUAL RESULTS: In the most recent build of InDesign, the <L> is just a sibling of the <LBody>. This is not only incorrect an a violation of PDF/UA-1, it also requires fixing EVERY TIME you use this feature in InDesign because it voices the incorrect level to the user when listening using assistive technology.

   Please FIX!!!!

   1 First level
   1.1 sub level
   1.2 sub level

   Should be:

   <L>
   -- <LI>
   --- <Lbl>
   --- <LBody>
   ---- <L> Child of the LBody

   =========

   NOT

   <L>
   -- <LI>
   --- <Lbl>
   --- <LBody>
   --- <L> Sibling of the LBody

   1. VERSION: 19.4

   2. ISSUE: If you create a multi-level list (1, 1.1, 1.2.3, etc) and export as an accessible PDF the list structure is not correct and presents the incorrect "List level" to the reader when using any assistive technology.

   EXPECTED RESULTS: When a new level of a list is created the sublist's <L> goes INSIDE the <LBody> tag to properly indicate the list is sublevel.

   ACTUAL RESULTS: In the most recent build of InDesign, the <L> is just a sibling of the <LBody>. This is not only incorrect an a violation of PDF/UA-1, it also requires fixing EVERY TIME you… more

   •  

   •  

   • 

   28 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Accessibility  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Accessible alt text for hyperlinks needs to be supported by scripting

   With InDesign scripting, it's possible to search for "searchTerms" from one column of a tab-delimited file, then set corresponding hyperlinks from another column. This means I can set hundreds of hyperlinks in just a few minutes. However, it remains impossible to set the hyperlink's alt text with a script — that function isn't scriptable. So either I ignore this important accessibility requirement (not an option), or I still have to manually edit each hyperlink, one at a time, wasting many hours and introducing the possibility of errors on each one.

   For example, a document contains hundreds of product numbers or reference numbers, and each one needs to link to a URL. The numbers themselves aren't sufficient to describe what the links lead to; they need alt text. I have a spreadsheet that lists these numbers, their corresponding URLs and their alt text descriptions. I can set the hyperlinks using a script and the spreadsheet, but I can't set the alt text.

   With InDesign scripting, it's possible to search for "searchTerms" from one column of a tab-delimited file, then set corresponding hyperlinks from another column. This means I can set hundreds of hyperlinks in just a few minutes. However, it remains impossible to set the hyperlink's alt text with a script — that function isn't scriptable. So either I ignore this important accessibility requirement (not an option), or I still have to manually edit each hyperlink, one at a time, wasting many hours and introducing the possibility of errors on each one.

   For example, a document contains hundreds of product numbers or… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. '단락'의 '보조 메뉴' 일부가 나오지 않음.

   '단락'의 '보조 메뉴'의 반(半) 정도가 나오지 않습니다. 아래 반만 나옵니다. 'Adobe World-ready 싱글라인 컴포저' 이하 메뉴만 나옵니다. 구체적으로 '격자 정렬' 기능을 기준에 따라 수행할 수 없습니다. 끝.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Alt-text and field descriptions/tooltips do not export correctly

   When updating Alt-text on images or the form field descriptions in InDesign 2025 20.0.1 on Mac and exporting to PDF, the Alt-text/descriptions do not reflect the updated text. This requires manual updating of every single image or form field in the PDF or saving as IDML, opening in 2024 and exporting.

   •  

   •  

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Accessibility  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Adobe Fonts not accessible in interactive PDFs

   Bug: Adobe Fonts are corrupting when using the Acrobat accessibility tools.

   I am making interactive PDFs from an InDesign document and Adobe Fonts corrupt upon opening in Acrobat, but just for the accessible features. (e.g., screeenreaders). I have tried clearing the cache, re-installing apps, Adobe customer support reps, etc and no one can fix the issue. I suspect it is due to licensing restrictions on editing font files - something is sending the signal that the Adobe Font is being edited when Accessibility Tools are used in Acrobat, but this should be allowed when the intention is to make the document accessible.

   1. Adobe InDesign 19.5.4 (also tried previous versions such as 20.4.1)
   2. Use Acumin Variable Pro font from Adobe in InDesign, make the document interactive (basic text form fields suffice to replicate the error), export as interactive PDF, open in Acrobat, open a screenreader and hear the corruption or open Accessibility Tools and tag the text (on a non-interactive part) and then see the text is missing letters and there are periods where spaces should be. Also, Acrobat crashes half the time during this process.
   3. Expected result - that Adobe Fonts work as other fonts in this scenario and that exports PDFs using Adobe Fonts can be edited for accessibility without issue.
   4. Crashed app, incomplete work, and failed accessible document.
   5. Can provide test file if you contact me privately (adobe).

   Bug: Adobe Fonts are corrupting when using the Acrobat accessibility tools.

   I am making interactive PDFs from an InDesign document and Adobe Fonts corrupt upon opening in Acrobat, but just for the accessible features. (e.g., screeenreaders). I have tried clearing the cache, re-installing apps, Adobe customer support reps, etc and no one can fix the issue. I suspect it is due to licensing restrictions on editing font files - something is sending the signal that the Adobe Font is being edited when Accessibility Tools are used in Acrobat, but this should be allowed when the intention is to make the… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. InDesign Buttons in Interactive PDF Not Receiving Visible Focus When Tabbing

   Product and Version: Adobe InDesign 20.3 (2025) & Acrobat Pro 2025.001

   Steps to reproduce:

   1. Create a Button in InDesign using Buttons and Forms panel.
   2. Assign an action like "Go to Next Page" with event "On Release or Tap."
   3. Export as Interactive PDF with "Create Tagged PDF" and "Use Structure for Tab Order" enabled.
   4. Open in Acrobat.
   5. Tab through the document.

   Expected result: Button should show visible focus indicator when selected by keyboard tabbing, to meet WCAG 2.4.7 Focus Visible.

   Actual result: Button can be activated by Enter but shows no visible focus indicator. Rollover and Click states do not activate on tabbing. Hyperlinks, and other form fields like Checkboxes show proper focus highlighting, but not Buttons. This causes accessibility failure for keyboard users.

   Product and Version: Adobe InDesign 20.3 (2025) & Acrobat Pro 2025.001

   Steps to reproduce:

   1. Create a Button in InDesign using Buttons and Forms panel.
   2. Assign an action like "Go to Next Page" with event "On Release or Tap."
   3. Export as Interactive PDF with "Create Tagged PDF" and "Use Structure for Tab Order" enabled.
   4. Open in Acrobat.
   5. Tab through the document.

   Expected result: Button should show visible focus indicator when selected by keyboard tabbing, to meet WCAG 2.4.7 Focus Visible.

   Actual result: Button can be activated by Enter but shows no visible focus indicator. Rollover and Click states do not activate… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Accessibility  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Changing Description in Buttons Does Not Stick

   A description is needed in buttons for accessibility. This works fine if you add the description when you first create the button but if you try to edit the description it does not not stick. The only workaround is to recreate the button from scratch.

   MacStudio 2022, Sequoia 15.5, InDesign 20.3.1.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Buttons on Parent Pages Create Form Field Errors in Acrobat

   Using buttons on parent pages, e.g. for navigation, throws up 'Tagged form fields' errors in Acrobat. These have to be manually tagged as links, which is a nightmare in a large document with multiple buttons per page.

   It's not clear whether all parent pages create this error or whether it's confined to parent pages based on another parent page.

   MacStudio 2022, Sequoia 15.5, InDesign 20.3.1.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Some glyphs in ai files appear as other glyphs in PDFs (created from InDesign)

   DE: Einige Glyphen in ai-Dateien kommen in (aus InDesign erzeugten) PDFs als andere Glyphen an.

   InDesign 19.5.1.114 | Windows 11

   The ohm sign Ω - U+02126 is placed several times in an InDesign document:
   2x in an Illustrator graphic
   1x in another Illustrator graphic created additionally for test purposes
   1x placed directly in InDesign

   If a PDF is created from the InDesign document, only the Ohm characters present in both Illustrator graphics are written to the PDF as different Unicode characters - and also as different other Unicode characters: U+0001F and U+00016.
   (See AI-Glyph-Test.pdf)

   The problem was noticed by checking the PDF with 'PDF Accessibility Checker' from axes4: The error ‘Text object with characters without Unicode mapping’ is reported for the Ohm characters in the Illustrator graphics.
   (See PAC-Report_AI-Glyph-Test.png)

   The PAC error is not reported for the Ohm character set directly in the InDesign document. But: the glyph Ω - U+02126 set in the InDesign document was replaced by the glyph Ω - U+003A9 during PDF export.

   DE: Einige Glyphen in ai-Dateien kommen in (aus InDesign erzeugten) PDFs als andere Glyphen an.

   InDesign 19.5.1.114 | Windows 11

   The ohm sign Ω - U+02126 is placed several times in an InDesign document:
   2x in an Illustrator graphic
   1x in another Illustrator graphic created additionally for test purposes
   1x placed directly in InDesign

   If a PDF is created from the InDesign document, only the Ohm characters present in both Illustrator graphics are written to the PDF as different Unicode characters - and also as different other Unicode characters: U+0001F and U+00016.
   (See AI-Glyph-Test.pdf)

   The problem was noticed by checking… more

   •  

   • 

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Accessibility  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. InDesign stops at "Fetching Service Registry" on launch every time — only resolves when disabling fonts

    Hello Adobe team,

    I have been using InDesign regularly, but for the past year, I have been encountering a very annoying and recurring issue.
    Every time I try to launch InDesign, it gets stuck on the screen saying "Fetching Service Registry" and never completes the startup process.

    After troubleshooting, I found out that temporarily disabling some OS fonts allows InDesign to launch properly.
    However, this is extremely inconvenient as I have to do this every single time before starting my work.

    This issue is highly reproducible and happens almost every launch.

    I would kindly request that the team look into this issue and address it in a future update.

    【Environment】

    OS: Windows 10

    InDesign version: 20.3.1 ×64 (example: InDesign 2025)

    Creative Cloud: Always up to date

    Thank you very much for your attention and support.

    Hello Adobe team,

    I have been using InDesign regularly, but for the past year, I have been encountering a very annoying and recurring issue.
    Every time I try to launch InDesign, it gets stuck on the screen saying "Fetching Service Registry" and never completes the startup process.

    After troubleshooting, I found out that temporarily disabling some OS fonts allows InDesign to launch properly.
    However, this is extremely inconvenient as I have to do this every single time before starting my work.

    This issue is highly reproducible and happens almost every launch.

    I would kindly request that the team look into… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. InDesign 2025 can't read metadata from multiple images

    macOS 15.2, InDesign 20.0.1

    Problem: Metadata inside an image not being recognized by InDesign 2025.

    Details:

    Multiple images from different sources containing metadata that InDesign doesn't recognize
    Presence of metadata in XMP Description field verified in Bridge and via InDesign's Links panel XMP File Info command.
    Generating a Live Caption or Static Caption when using the Description field returns "<No data from link>".
    Setting Object Export Options > Alt Text Source to From XMP: Description results in "metadata property is not present on some selected content".
    When a PDF is generated using the images in question, the metadata is not passed through to the PDF, resulting in missing alt text accessibility errors.
    Manually writing (or copying and pasting) the metadata to the Alt Text Source as Custom works, but as does manually creating a caption, but automation is the point.

    macOS 15.2, InDesign 20.0.1

    Problem: Metadata inside an image not being recognized by InDesign 2025.

    Details:

    Multiple images from different sources containing metadata that InDesign doesn't recognize
    Presence of metadata in XMP Description field verified in Bridge and via InDesign's Links panel XMP File Info command.
    Generating a Live Caption or Static Caption when using the Description field returns "<No data from link>".
    Setting Object Export Options > Alt Text Source to From XMP: Description results in "metadata property is not present on some selected content".
    When a PDF is generated using the images in question, the metadata is not… more

    •  

    •  

    •  

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Before tag and after untag frame with different behavior

    If you tag a frame object (XML), this object does not behave the same after untagging as before tagging. In other words: tagging is not fully reversible. You can see a difference in the layer panel and in the exported PDF tag structure (Tagged PDF)

    How can this behavior be reproduced?

    1. Create a new InDesign document.
    2. Draw a placeholder (empty) graphic frame
    3. Assign any XML tag to the frame
    4. Remove the XML tag
    5. Export a tagged PDF
       

    What is the difference between the object before tagging and after untagging?

    The layer panel shows a different status.

    The frame before tagging is not assigned a tag in the tag structure of the PDF during PDF export. A tag is assigned to the object in the PDF structure after tagging and untagging. (see attached screenshots)

    What should be the correct behavior?

    Both states of the frames - i.e. without tagging and after untagging - should result in the same result in the layer panel and in the tag export for PDF.

    Why is this relevant?

    This causes a problem if these objects appear in the tag structure of the exported PDF. They are (empty) graphic frames, but InDesign assigns a Figure tag to them and they also have no alternative text. When checking the PDF for accessibility, an error is reported.

    These two states of the same object cannot be distinguished via ExtendScript. If an InDesign document is saved using IDML, these objects are converted back into “normal” graphic frames.

    InDesign, Platform

    InDesign 2024, 2025
    macOS Monteray

    Discussion

    https://community.adobe.com/t5/indesign-discussions/rectangle-vs-graphic-frame/td-p/15039102

    If you tag a frame object (XML), this object does not behave the same after untagging as before tagging. In other words: tagging is not fully reversible. You can see a difference in the layer panel and in the exported PDF tag structure (Tagged PDF)

    How can this behavior be reproduced?

    1. Create a new InDesign document.
    2. Draw a placeholder (empty) graphic frame
    3. Assign any XML tag to the frame
    4. Remove the XML tag
    5. Export a tagged PDF
       

    What is the difference between the object before tagging and after untagging?

    The layer panel shows a different status.

    The frame before tagging… more

    •  

    •  

    •  

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Improvement suggestion

    When we insert the date in a text, there is no way to specify that that part is a date and when we use the screen reader, it reads the date numbers one by one, taking away the meaning of the date, for example: cycle 2020-2025. It would be interesting if we could mark the section as a date.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Punjabi / Gurmukhi character encoding errors after exporting to interactive PDF

    InDesign 2025 and 2024:

    Punjabi / Gurmukhi documents exported to interactive PDF have character encoding issues. Some glyphs cannot be read by screen readers or output to braille.

    After many hours of research and testing, it was discovered that exporting from InDesign 2023 does not create this issue.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. button value

    Broken in 18.3 and 19.5: Non-ASCII text in the "Button Value" field in the "Buttons and Forms" panel fails to export to interactive PDF.

    To reproduce this issue:
    1) Create a radio button
    2) Add non-ASCII text to the "Button Value" field
    3) Export to Interactive PDF
    4) Look at the mouseover tooltip and see that the Button Value has lost any glyphs beyond U+00FF.

    I've attached a PDF file demonstrating the issue.

    • 

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Sur la version Mac 2025 (20,0) de indesign Je suis obligé pour voir les boites de sélection de faire une manœuvre pour les voir.

    les boites sont affichées en arrière de la fenêtre principale. elles n'apparaissent devant que lorsque j'ai fait une manœuvre (voir toutes les fenêtres de l'écran). C'est gênant.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Ouvrir un fichier en glissant l'icône dans la fenêtre ne fonctionne plus

    Depuis la version 20.0 x64 sur PC, je ne peux plus ouvrir un fichier InDesign en glissant l'icône sur la fenêtre de l'application. Cela m'est très utile vu qu'à cause d'un CMS installé, mon PC ne reconnaît plus l'icône du programme et que le double-clique ne fonctionne pas non plus.

    •  

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Table Stroke adjusment panel

    On the Table Stroke adjustment panel, the thin blue lines are difficult to see for someone with color deficient vision or reduced visual acuity. I suggest increasing the width of the highlighted stroke to indicate which are selected.

    •  

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Accessibility  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. cursor stuck on hand

    My system has just updated InDesign to 19.1 (08/01/24) and I now have a grabber hand cursor appearing every time I try and click on anything in my file.

    This also happens if I have another tool selected such as text box. The tool icon appears but if I click on a text box the hand comes back. It's rendered doing anything in InDesign files useless. I can't find a setting for it and I have tried resetting preferences but it is still happening. My computer system is running Ventura 13.6.

    Does anyone have a work around?

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Accessibility  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Scripting bug with Book files and the new EPUB Page Navigation option

    In InDesign 19.4 on macOS 14.4.1, the document.epubExportPreferences.epubCreatePageNavigation and book.epubExportPreferences.epubCreatePageNavigation properties are supposed to allow scripts to toggle the reflowable EPUB "page navigation" option on and off. However, only the document.epubExportPreferences.epubCreatePageNavigation property functions properly. The book.epubExportPreferences.epubCreatePageNavigation doesn't do anything. Regardless of whether it is "true" or "false", the output always includes the page break markers when outputting reflowable ePub from a book file via scripting.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating