IGP:Digital Publisher 9.0.0

IGP:DP 9.0.0 - Updates, Upgrades & Enhancements

The following updates have been implemented in this release:

PDF profile PDF/UA updates for ‘Universal Accessibility’

Digital Publisher now supports generating of accessible tagged PDFs using Prince. This will only be applicable for servers with PrinceXML 13+ installed.

On the DPI form, under Online PDF Processing options, added "Accessibility Processing" header along with the below checkbox option:
☑ PDF-Profile: PDF/UA-1 (Applicable only if PrinceXML 13+ installed on the server).

This checkbox is selected by default, which would generate PDF profile PDF/UA-1 output, when an Online PDF format request is given.

The default ACCESSIBILITY DEFAULT MAPPING CSS is stored in a file on the server.

 
/*  ACCESSIBILITY DEFAULT MAPPING CSS Starts  */
article { prince-pdf-tag-type: Art }
section { prince-pdf-tag-type: Sect }
blockquote { prince-pdf-tag-type: BlockQuote }
h1 { prince-pdf-tag-type: H1 }
h2 { prince-pdf-tag-type: H2 }
h3 { prince-pdf-tag-type: H3 }
h4 { prince-pdf-tag-type: H4 }
h5 { prince-pdf-tag-type: H5 }
h6 { prince-pdf-tag-type: H6 }
ol { prince-pdf-tag-type: OL }
ul { prince-pdf-tag-type: UL }
li { prince-pdf-tag-type: LI }
dl { prince-pdf-tag-type: DL }
dl > div { prince-pdf-tag-type: DL-Div }
dt { prince-pdf-tag-type: DT }
dd { prince-pdf-tag-type: DD }
table { prince-pdf-tag-type: Table }
figure { prince-pdf-tag-type: Div } /* figure grouper */
figcaption { prince-pdf-tag-type: Caption }
p { prince-pdf-tag-type: P }
q { prince-pdf-tag-type: Quote }
code { prince-pdf-tag-type: Code }
img, input[type="image"] {
    prince-pdf-tag-type: Figure;
    prince-alt-text: attr(alt);
}
abbr, acronym {
    prince-expansion-text: attr(title)
}
/*  FX ACCESSIBILITY DEFAULT MAPPING CSS Starts  */
body {prince-pdf-tag-type: Document}
div.Part-rw, div.Unit-rw, div.Alpha-rw, div.Volume-rw {prince-pdf-tag-type: Part}
div.Article-rw {prince-pdf-tag-type: Art}
div.epigraph-rw {prince-pdf-tag-type: BlockQuote}
div.list-toc-rw ol, div.list-figures-rw ol, div.list-tables-rw ol, 
div.list-equations-rw ol, div.list-images-rw ol, div.list-illustrations-rw ol, 
div.list-maps-rw ol, div.list-plates-rw ol {prince-pdf-tag-type: TOC}
div.list-toc-rw li, div.list-figures-rw li, div.list-tables-rw li, 
div.list-equations-rw li, div.list-images-rw li, div.list-illustrations-rw li, 
div.list-maps-rw li, div.list-plates-rw li {prince-pdf-tag-type: TOCI}
div.list-references-rw p {prince-pdf-tag-type: BibEntry}
div.list-notes-rw p {prince-pdf-tag-type: Note}
p.caption-rw {prince-pdf-tag-type: Caption}
tr {prince-pdf-tag-type: TR}
th {prince-pdf-tag-type: TH}
td {prince-pdf-tag-type: TD}
thead {prince-pdf-tag-type: THead}
tbody {prince-pdf-tag-type: TBody}
tfoot {prince-pdf-tag-type: TFoot}
span {prince-pdf-tag-type: Span}
a:link, a {
prince-pdf-tag-type: link;
prince-alt-text: attr(alt);
}
div.list-index-rw {prince-pdf-tag-type: Index}
div.list-notes-rw p {prince-pdf-tag-type: Notes}
div.list-footnotes-rw p {prince-pdf-tag-type: Notes}
div.Act-rw, div.ArticleRunOn-rw, div.Chapter-rw, div.ChapterRunOn-rw, 
div.Column-rw, div.ColumnRunOn-rw, div.Division-rw, div.Drama-rw, 
div.DramaRadio-rw, div.DramaScreen-rw, div.Entracte-rw, div.Epilogue-rw, 
div.Introduction-rw, div.Lesson-rw, div.LessonRunOn-rw, div.Page-rw, 
div.Poem-rw, div.PoemRunOn-rw, div.Prologue-rw, div.Recipe-rw, div.Scene-rw, 
div.Section-rw, div.Topic-rw, div.TopicRunOn-rw {prince-pdf-tag-type: Sect}
.toc-num-rw, .ref-note-rw, .ref-footnote-rw, 
.num-note-rw, .num-footnote-rw { prince-pdf-tag-type: Lbl }
 
.list-index-rw h4 { prince-pdf-tag-type: Lbl }
p.title-num-rw { prince-pdf-tag-type: Lbl }
a.pagebreak {prince-pdf-tag-type: Artifact}
div.frontmatter-rw, div.backmatter-rw, div.specials-rw {prince-pdf-tag-type: Sect}
div.block-rw, div.poem-rw, div.drama-rw {prince-pdf-tag-type: Div}
div.epigraph-rw, div.extract-rw {prince-pdf-tag-type: BlockQuote}
/*  FX ACCESSIBILITY DEFAULT MAPPING CSS Ends  */
/* ACCESSIBILITY DEFAULT MAPPING CSS Ends */

It is possible to assign PDF tag types to elements in the document using the -prince-pdf-tag-type property. So editor's can define custom tags in the Print CSS of the Document, which would override the default ACCESSIBILITY DEFAULT MAPPING CSS.

For more details about the CSS Properties related to PDF Tags, supported by Prince, refer the below mentioned URL
https://www.princexml.com/doc/css-props/#prop-prince-pdf-tag-type

The PDF metadata is also created from the content of the XHTML metadata elements. The content of the <title> element is used for the document title, while the <meta> element is used to specify the document author, subject, keywords, date, and generator application.

Ultimately claiming that a document meets the PDF/UA-1 profile actually requires some human review, so Application has to trust that the editor has done their part in terms of making the input intelligible.

Epubchecker updates

The ePubchecker version will be updated to Version 4.2.5 from Version 4.2.1. This is the latest production-ready release of EPUBCheck, which provides complete support for checking conformance to the EPUB 3.2 family of specifications.

ARIA Accessibility updates

ACE Accessiblity checker, reported Critical violations for Table, regarding "aria-required-children" Rule. For "Table" tagging structure the new ace validator "Ace by DAISY 1.1.3" generated the following validation error:
'Violations' catogory >> 'critical' error generated by Accessibility Validator i.e.: Required ARIA children role not present: rowgroup, row

We have updated the Accessibility Aria Role for table tagging structure:

1. Removed the existing epub:type="table" role="table" attributes from <div class="table-rw ...> and added it to <table ...> element
2. Added role="rowgroup" to <thead> and <tbody> and <tfoot>
3. Added epub:type="table-row" role="row" to <tr>
4. Added epub:type="table-cell" role="cell" to <th> and <td>

IGP:DP 9.0.0 - Presentation Template updates

The Master Presentation Templates will be updated by IGP during the update activity. If you have created any custom templates based on the IGP Master Templates, please check that these updates are applied in your templates if applicable.

• DPI Form update - Added "Accessibility Processing" header along with the below checkbox option, under Online PDF Processing options
  ☑ PDF-Profile: PDF/UA-1 (Applicable only if PrinceXML 13+ installed on the server)

[ PT updated: DPMaster-2012, DPMasterSMIL-2012, TradeMaster-2012, MinimalCSS and StaticSiteMaster-2012 ]

IGP:DP 9.0.0 - Bug Fixes

1. When "Copy Backmatter Notes to Section End" option is used, and the End Notes Section is also retained, the notes get moved along with pagebreak-rw's in the respective section. But the <nav epub:type="page-list"> section in the TOC.xhtml file populates the href value of the items with the section references in which the notes have been moved, resulting in EPUBCHECK ERROR(NAV-011). This has now been fixed for EPub2, EPub3 and Kindle formats by removing the pagebreak-rw's from the notes that have been moved to the Section End.

2. For ePub3, when on DPI form, Index Processing > Alpha Segment Index (ABC, DEF, etc.) checkbox option is selected, the <nav epub:type="toc"> section in the TOC.xhtml file contained blank classes for <li>. This is now fixed to populate the respective section classes.

3. Handled footnote-ref hyperlinking process to match footnote-ref and footnote-num content with dot(.) in footnote-num. Also updated Notes and Footnotes QC Report (Content Tools) with this change.

4. Epub3 – TOC.xhtml > chapters section were not appearing in <nav epub:type="toc". This is now fixed.

5. Wrong section numbers are generated in Introduction, Prologue and Epilogue "body-rw" section. This is now fixed.

6. When DPI options are selected - “Copy Backmatter Notes to Section End” and “Insert separate span for Endnote text and map ePubtype and ref ID.”, Getting ePub validation ERROR for blank ID value on <span id="" epub:type="rearnote" role="doc-endnote"> in the Endnotes Section. This is now fixed.

7. DP > Library > Modify Metadata - The metadata updated in DP using the spreadsheet also updates the metadata in the Reader database including the DPI INFO metadata. The earlier code only updated the Title and Presentation Template in the Reader database.

8. Manuscript import: Multiple "rowspan" in table first row creating issue while converting table first row into table-head process. This table first row "rowspan" was not continued to the next row in table-body hence table data showing misplaced.

9. Manuscript import: Handled placeholder image processing in Document End Note section.