This is critically needed to automate numbered lists for technical documents, legal documents, and government publications.
Also ensure that when exported to accessible tagged pdf, the lists are correctly tagged.
6 votes2 comments · Adobe InDesign: Feature Requests » Text and Type · Flag idea as inappropriate… · Admin →
See this related post in the Acrobat User Forum:
The manual line break character from InDesign isn't Unicode compliant, which causes the PDF to fail in the accessibility checker.
5 votes1 comment · Adobe InDesign: Feature Requests » Text and Type · Flag idea as inappropriate… · Admin →
Not seeing this problem with versions 13.1 (CC:2018), and 14.0 and 14.1 (CC:2019).
We acknowledge that the issue is slowing you down and we regret the same.
Our investigation suggests that the issue lies in the latest update of Acrobat and there is little that can be done at our end to resolve the issue.
The problem has been communicated to the relevant team.
In the meanwhile we are closing this thread for InDesign.
At this time, the <Span> tags don't affect screen reader accessibility (SR's ignore them for now). I think that's also the case with other Assistive Technologies.
However, the PDF/UA standard is expanding and forthcoming releases will require much tighter control of tags, structure, nesting, etc. AND the <Span> tag could be used to convey valuable information to the user or technology, so we don't want it mis-used now and cause documents to fail in the future.
Adobe needs to correct this ASAP and ensure that <Span> tags are used appropriately (usually to designate visual formatting of the content) and not wrap them around every single element in the document.
10 votes1 comment · Adobe InDesign: Feature Requests » Layout/Graphics etc · Flag idea as inappropriate… · Admin →
We need a Preflight definition for InDesign that checks for accessibility issues, such as:
1) Unicode (OpenType) fonts
2) Alt-text on graphics
3) Tags defined in the paragraph styles
4) Correct formatting of lists and tables
5) Color contrast
6) Metadata / File Info
7) Sequential hierarchical headings
I think table footnotes should be in the table footer section of the table so that:
1) They are part of the table, not the rest of the page content, and
2) They automatically repeat at the bottom of multi-page tables.
Right now, as folks have said, the table footnotes are separated from the actual table itself.
For accessibility, the footnote <Note> tags would be in the <TFoot> section within the <Table> tag.
The fix for this issue is now available in the latest update (14.0.2) of InDesign 2019.
If you are unable to see the update notification, open the menu (three dots) from the top-right of Creative Cloud desktop application and click on ‘Check For App Updates’.
Once the update button is shown against InDesign, click on the button to update to Id 14.0.2.
If you face any problems with the new update, do let us know in the comments.
The list of fixed issues can be found at: helpx.adobe.com/indesign/kb/fixed-issues.html
Adobe InDesign team
The ability to customized the Properties panel.
Different types of publishing workflows need a different set of tools. Examples: accessibility, XML/automated, digital only, print only.
Just as I can set up my own workspace of panels and their locations, I'd also like to remove some of the items in the current Properties panel because I can't use them in my workflow. And there are others buried under an expansion arrow that I need to access all the time.
Different strokes for different folks!
13 votes3 comments · Adobe InDesign: Feature Requests » Print/Packaging · Flag idea as inappropriate… · Admin →
Lukas, I would love to work with you on this. Contact me off list.
—Bevi Chagnon | PubCom (accessibility experts)
Please respond to the email sent by us for more information regarding this issue.
Adobe InDesign team
This is a critical problem for those making accessible PDFs from InDesign layouts. Especially in STEM and technical documents, the graphic must be anchored at a precise spot in the layout (and the resulting PDF tag tree). This bug prevents us from either creating the design and accessibility we need, or spending costly labor to correct the PDF in Acrobat.
It's been 20 years, Adobe. Fix this *&^%$#@! bug.
Would be fabulous to have this in InDesign, too. Could be built into the existing Output panel. Maybe color it Color accessibility?
Also could include a contrast analyzer because contrast between foreground and background is in all of the accessibility standards: https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html
A good contrast checker to use as a model: https://webaim.org/resources/contrastchecker/
Thank you for your patience all this while.
This issue is now fixed in the latest update (Id 14.0.1) of InDesign CC.
If you are unable to see the update notification yet, open the menu (three dots) from the top-right of Creative Cloud desktop application and click on ‘Check For App Updates’.
Once the update button is shown against InDesign CC, click on the button to update your InDesign to Id 14.0.1 for the fix of the issue.
Do let us know in the comments, if you face any problem with the new update.
List of fixed issues can be found at: helpx.adobe.com/indesign/kb/fixed-issues.html
Some comments from other forums indicate that if you close the Control Panel (top of your screen) and use the new Properties panel instead, this lag will go away.
Mac folks say that the lag happens only when InDesign is first launched and then works fine.
Many Windows folks (including myself) experience the lag not only upon launch, but also when switching between the text and selection tools. Definitely vote for this bug to get fixed ASAP!
Thank you for reporting the issue.
We are currently reviewing the same.
I'm having this problem with CC:2019 (Oct release) — hang, then crash which sometimes creates a corrupted INDD file.