E-mail List Archives
Re: Telerik .NET Reporting - Accessible PDF Output - How Control Tagging? Links to Resources?
From: Duff Johnson
Date: Apr 8, 2020 12:00PM
- Next message: Danielle Chouhan: "ADA-compliance for abstract reasoning testing"
- Previous message: Steve Green: "Re: understanding what goes into a Vpat and knowing the process"
- Next message in Thread: Philip Kiff: "Re: Telerik .NET Reporting - Accessible PDF Output - How Control Tagging? Links to Resources?"
- Previous message in Thread: Philip Kiff: "Telerik .NET Reporting - Accessible PDF Output - How Control Tagging? Links to Resources?"
- View all messages in this Thread
> But some colleagues are having difficulty matching that promise to reality(!). I couldn't find much documentation on how to control the tagging of the PDF output. Our initial attempts produced files that were woefully inaccessible, though, surprisingly, they still managed to pass the PAC (PDF Accessibility Checker) tool tests cleanly with zero errors.
When you say "woefully inaccessible" could you say more? What, in particular, was inaccessible?
PAC does the "machine" checks… but validation of tagging semantics is up to the person running the software…
Duff.
- Next message: Danielle Chouhan: "ADA-compliance for abstract reasoning testing"
- Previous message: Steve Green: "Re: understanding what goes into a Vpat and knowing the process"
- Next message in Thread: Philip Kiff: "Re: Telerik .NET Reporting - Accessible PDF Output - How Control Tagging? Links to Resources?"
- Previous message in Thread: Philip Kiff: "Telerik .NET Reporting - Accessible PDF Output - How Control Tagging? Links to Resources?"
- View all messages in this Thread