<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Charles:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I suggest you ring me. In about three weeks, RenderX will release an update you our software. There are significant enhancements in Section 508 compliance in this update. </span><span style='font-family:"Calibri","sans-serif"'>This version supports many new features that are integral to 508 support. I can provide samples and a patch to get you started on using all the new features.<o:p></o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'>1) XEP now includes a rolemap that allows you to reassign structural FO tags in general to alternate tags in PDF. Examples would be fo:root->Document, fo:block->P, fo:table->T, fo:list-block->L ...<o:p></o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'>2) The rolemap also allows one to define "roll-up" FO structures. These would be completely eliminated from the Tag structure. Examples would usually be fo:block-container, fo:table-header, fo:table-body, fo:inline, fo:wrapper, ... These types of items add unnecessary Tags to documents.<o:p></o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'>3) XEP also includes spot over-riding of these through an extension rx:pdf-structure-tag, so particular tags can specified for certain structures. One would use this for things that have no equivalent in XSL FO, like heading tags H1, H2 and so on. This same extension allows someone to also mark something as an Artifact to exclude it from reading (like content in headers and footers).<o:p></o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'>4) The creation of tables is done to completely support 508 requirements. One can specify table headers (cells in a TH) and override cells in the table-body to get TH cells in table-body rows. All TH cells are marked with appropriate scope attributes for "row", "column" or "both"<o:p></o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'>5) Multiple types of alternate text are provided through rx: extension attributes for all situations<o:p></o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'>A few unique situations are also handled by a post-process for reorganizing content reading order on the first page, eliminating repeating table headers from reading on all but the first page of occurrence, etc. <o:p></o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoPlainText><span style='font-family:"Calibri","sans-serif"'>We are also working to modify our XSL FO to HTML conversion in order to handle all of the above situations so that one could use our FO to HTML output to obtain 508 compliant HTML from the same source. This will be sold as an add-on (FO to HTML for 508), all the other enhancements within PDF generation is part of the core product available to customers with current support contracts.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>Kevin Brown<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>Executive Vice President, Sales & Marketing RenderX, Inc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>(650) 327-1000 Direct<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>(650) 328-8008 Fax<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>(925) 395-1772 Mobile<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>skype:kbrown01<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'><a href="mailto:kevin@renderx.com">kevin@renderx.com</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'><a href="mailto:sales@renderx.com">sales@renderx.com</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'><a href="http://www.renderx.com">http://www.renderx.com</a> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> xep-support-bounces@renderx.com [mailto:xep-support-bounces@renderx.com] <b>On Behalf Of </b>Charles Porter<br><b>Sent:</b> Wednesday, October 03, 2012 11:45 AM<br><b>To:</b> xep-support@renderx.com<br><b>Subject:</b> [xep-support] ENABLE_ACCESSIBILITY and table headers<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi there,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I am using XEP to generate government regulated documents for clients. Thus, they must be compliant with Section 508 .<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Here is a test case:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><?xml version="1.0" encoding="UTF-8"?> <o:p></o:p></p></div><div><p class=MsoNormal><fo:root xmlns:fo="<a href="http://www.w3.org/1999/XSL/Format">http://www.w3.org/1999/XSL/Format</a>"><o:p></o:p></p></div><div><p class=MsoNormal> <fo:layout-master-set><o:p></o:p></p></div><div><p class=MsoNormal> <fo:simple-page-master master-name="simple-page" page-height="11in" page-width="8.5in"><o:p></o:p></p></div><div><p class=MsoNormal> <fo:region-body margin="0.5in"/><o:p></o:p></p></div><div><p class=MsoNormal> </fo:simple-page-master><o:p></o:p></p></div><div><p class=MsoNormal> </fo:layout-master-set><o:p></o:p></p></div><div><p class=MsoNormal> <fo:page-sequence master-reference="simple-page"><o:p></o:p></p></div><div><p class=MsoNormal> <fo:flow flow-name="xsl-region-body"><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-column<o:p></o:p></p></div><div><p class=MsoNormal> border="1pt solid black"/><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-column <o:p></o:p></p></div><div><p class=MsoNormal> border="1pt solid black"/><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-header border="1pt solid black"><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-row><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-cell><o:p></o:p></p></div><div><p class=MsoNormal> <fo:block>test</fo:block><o:p></o:p></p></div><div><p class=MsoNormal> </fo:table-cell><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-cell><o:p></o:p></p></div><div><p class=MsoNormal> <fo:block>test</fo:block><o:p></o:p></p></div><div><p class=MsoNormal> </fo:table-cell><o:p></o:p></p></div><div><p class=MsoNormal> </fo:table-row><o:p></o:p></p></div><div><p class=MsoNormal> </fo:table-header><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-body border="1pt solid black"><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-row><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-cell><o:p></o:p></p></div><div><p class=MsoNormal> <fo:block>test</fo:block><o:p></o:p></p></div><div><p class=MsoNormal> </fo:table-cell><o:p></o:p></p></div><div><p class=MsoNormal> <fo:table-cell><o:p></o:p></p></div><div><p class=MsoNormal> <fo:block>test</fo:block><o:p></o:p></p></div><div><p class=MsoNormal> </fo:table-cell><o:p></o:p></p></div><div><p class=MsoNormal> </fo:table-row><o:p></o:p></p></div><div><p class=MsoNormal> </fo:table-body><o:p></o:p></p></div><div><p class=MsoNormal> </fo:table><o:p></o:p></p></div><div><p class=MsoNormal> </fo:flow><o:p></o:p></p></div><div><p class=MsoNormal> </fo:page-sequence><o:p></o:p></p></div><div><p class=MsoNormal></fo:root><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>When I render the above FO into a tagged PDF, and then run the Adobe Acrobat Accessibility Check Report for 508 compliance, the report complains that the table has no table header, even though the FO clearly has a table header block.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Is there something I am doing wrong, and if so, what should I do to correct it?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Charles Porter<o:p></o:p></p></div><p class=MsoNormal>!DSPAM:87,506c87c463736705114962! <o:p></o:p></p></div></body></html>