[xep-support] Re: Tab order issue with accessibility check

[François Yergeau]

Le 2018-06-26 à 01:37, Kevin Brown a écrit :
> Set PDF version to 1.5 and use the latest software.

Bingo, that does it, thanks.

Since the PDF version defaults to 1.4, it would be nice to mention this 
in the Accessibility section of the User guide.  I wasted significant 
time chasing this issue.

Regards,

-- 
François Yergeau

>
> -----Original Message-----
> From: Xep-support [mailto:xep-support-bounces at renderx.com] On Behalf Of François Yergeau
> Sent: Monday, June 25, 2018 1:34 PM
> To: xep-support at renderx.com
> Subject: [xep-support] Tab order issue with accessibility check
>
> Hello XEP support,
>
> I'm trying to improve accessibility (à la WCAG or Section 508) of some publications that are created by XEP, and I'm running into an issue that I don't really understand.
>
> I created a fairly minimal test case that has some of the features I have to deal with (mostly tables).  I generate a PDF using XEP 4.21 (the version my customer currently runs), obviously with ENABLE_ACCESSIBILITY turned on, and then run Adobe Acrobat's accessibility checker.
>
> In the Page Content section of the report, Acrobat complains about tab order.  The explanation is that tab order must parallel document structure.
>
> At first I thought the failure was related to the presence of links (both internal and external) in my document, but I removed all links and still get the error.  There are no form fields or anything of that kind in the document, in fact nothing that I would consider a tabbable control.  Opening the Tab order entry in the report simply shows a list of all pages.  Are pages supposed to be tabbable, and XEP is failing to make them so?
>
> An interesting point is that selecting Correct in Acrobat's context menu for that issue does work.
>
> I was hoping that this was just a bug in the oldish XEP 4.21, or perhaps a recent a11y requirement implemented in more recent versions, so I tried 4.27, to no avail.  Does anybody have any idea what might be causing this, and how to fix it?
>
> Regards,
>
> --
> François Yergeau
>
> _______________________________________________
> (*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
> (*) By using the Service, you expressly agree to these Terms of Service http://w ww.renderx.com/terms-of-service.html
>
> _______________________________________________
> (*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
> (*) By using the Service, you expressly agree to these Terms of Service http://w
> ww.renderx.com/terms-of-service.html