We've installed build 2023070306 of 25.1 and that resolved the issue. Thanks.

We've noticed that nested links in the publication TOC (in WebHelp responsive) that are initially hidden when the page loads, are tagged with target = "_blank" when they are added to the page. Is this by design (for some security purpose) or has this been changed in build 2023042509? For r...

I just thought I'd send a quick follow-up that we were able to rewrite our code to load our javascript files with <script> elements (and setting the @defer attribute). However, we still had to add some timeout functions to wait for pieces of the Oxygen code to run before running some of our code tha...

Thanks for the replies. We have quite a bit of custom javascript code that we were loading with the AMD mechanism and are now trying to figure out the best way to move forward. Our code uses a lot of jQuery and we also have to manage some dependencies in terms of ensuring that various modules have b...

Thanks for that information! I didn't see anything about this pretty major change in the release notes for either 25 or 25.1. Was this announced somewhere?

We're upgrading from Oxygen 24.1 to 25.1 and noticed that our custom javascript modules are not getting loaded. For reference, we set the webhelp.enable.template.js.module.loading parameter to 'yes' in a publishing template and are generating responsive webhelp content. As a simple sanity check, we ...

Thank you!

Thanks!

We've also discovered that the tooltips generated from <shortdesc> elements in the DITA source are not keyboard accessible and are not read by a screen reader. We've been able to fix both of these issues in our custom javascript but were not sure if you might already have something in your road map ...

Thanks for the response!

We've noticed that the span elements used to display the expand/collapse buttons for expandable elements, such as sections and articles, have the aria-label attribute set to 'expand' or 'collapse' (in English). When using the keyboard to tab to one of these span elements, a screen reader (such as NV...

We generate PDF's with a customized version of the DITA-OT PDF2 plug-in, specifying PDF/UA-1 mode (in a customized version of the fop.xconf file) so that we generate PDF's that are 508 compliant. Our transform was failing whenever there was a registered trademark symbol in a title element of a topic...

Thanks!

Resurfacing this issue to see if the Oxygen team has any plans to modify the keyboard accessibility of the side TOC in responsive webhelp. Although the TOC is technically keyboard accessible, it isn't accessible in the standard way (as described in https://www.w3.org/WAI/ARIA/apg/example-index/treev...

We were actually using the Ant (with Saxon-HE XSLT support) transformation scenario, but we had initially created this in 23.1. When we upgraded to 24.1, we did not manually update our customized version of that transformation scenario so that it was based on the 24.1 version of the Ant (with Saxon-...

I've attached a zip file containing the following set of test files that will hopefully allow you to reproduce the issue: test.xsl - stylesheet for transforming a source DITA file test_build.xml - ANT build file test_in.dita - source DITA file to be transformed test_items.xml - auxilliary file to us...

We have an ANT-based transformation scenario with a stylesheet that reads in an external XML document and stores the contents to a global variable, which is then used in transforming a source DITA file. The job runs fine in Oxygen 23.1 but fails with the following error in Oxygen 24.1: Error checkin...

Hi Julien, Thanks very much for requesting this fix on the DITA-OT side. I should note that, since I originally discovered this issue, I've found that the same issue occurs for any instance of the <fo:basic-link> element, not just TOC entries. So, for example, the same issue occurs for <fo:basic-lin...

Hi Julien, Automated PDF accessibility checkers will not flag the absence of headings, but the absence of headings is something you'll notice if you read the document with a screen reader (such as NVDA). The absence of heading tags means that headings are specified with styling rather than structure...

I've found a very simple fix that leverages the get-topic-level code that's included in the DITA OT's version of topic.xsl. Specifically, to add the correct heading level to a section element, you just need to override the template (within topic.xsl) that matches the section title, as follows: <xsl:...

We've found that PDFs generated from the XSL-FO approach (e.g., built from the "DITA Map PDF - based on XSL-FO" transformation scenario), and with accessibility enabled, don't include heading tags such as H1, H2, etc. This poses a problem for meeting 508 accessibility standards since scree...

We've found what seems to be a very simple fix for this by overriding one of the templates in toc.xsl (from the org.dita.pdf2 plugin). Specifically, in the template that matches on *[contains(@class, ' topic/topic ')], and has mode="toc", we added the following attribute to the fo:basic-li...

Thank you!

We're attempting to create accessible PDF's from the map-based version of the HTML5 & CSS transformation scenario. When we set the pdf.accessibility parameter to 'yes', the <Link> tags associated with the table of contents entries are automatically populated with the following value for the Alte...

Thank you!

We're attempting to create accessible PDF's using the default Apache engine and are using a custom fop.xconf file. In that file, we've set the following: <accessibility>true</accessibility> ...and: <renderer mime="application/pdf"> <pdf-ua-mode>PDF/UA-1</pdf-ua-mode> In the generated PDF (...

Thanks for the information!

We've noticed that we're getting the following java warning in Oxygen 24.0 when we build responsive webhelp with fix.external.refs.com.oxygenxml set to true: [WARN] Could not override the default file protocol handler java.lang.reflect.InaccessibleObjectException: Unable to make field static java.ut...

We're currently in the process of testing our responsive webhelp against the WCAG 2.1 standard and have discovered that the side TOC (wh_publication_toc) does not appear to honor some of the standard keystrokes for navigating the tree. For example, according to the WAI-ARIA Authoring Practices for t...

Thanks!