Accessibility of Pandoc Documents

Accessibility of Pandoc Documents

[Conrad Cunningham]

[-- Attachment #1.1: Type: text/plain, Size: 1316 bytes --]

I have recently started using Pandoc-flavored Markdown to develop materials 
for the courses I teach. I generate HTML and LaTeX/PDF for now (and perhaps 
other formats in the future). I would like to make sure my documents are 
"accessible" according to my university's policy.

Are there any Pandoc-related tools to help check for and ensure 
accessibility of the output? (I know the HTML output can be checked with 
the WAVE tool, but I was looking for something upstream from 
that--templates, filters, preprocessors, etc.)

I have a student looking at this issue. We are open to suggestions on ways 
to approach this problem if there is nothing in existence.

Conrad Cunningham, Computer and Information Science, University of 
Mississippi

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/97f31872-3cd8-40f3-a099-e20aee8f5433%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 1821 bytes --]

Accessibility of Pandoc Documents

[Kolen Cheung]

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

I didn’t recall there’s such a tool (I could be wrong though). Have you read through the pandoc-extras in pandoc’s wiki page on GitHub? It seems using a post-processor to check and work backward to tweak your template is the way to go. Although pandoc’s output generally is quite good, but pandoc is no linter as it is not designed to be. So I don’t imagine any tool other than post-processor would help. Even if there’s a template designed to conform to a certain requirements, what pandoc writes could break it that requirement. And then pre-processor/filter are even more difficult to do what you need, because it doesn’t see the resultant format.

Does the doc involve math? If you use MathJax, I think it has been built with accessibility in mind.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/4669335d-216c-4ab0-8527-4979a3bc6f13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessibility of Pandoc Documents

[Conrad Cunningham]

[-- Attachment #1.1: Type: text/plain, Size: 2435 bytes --]

Yes, Pandoc goes a good job as long as the input is constructed carefully. 
That is one thing I like about it for generating instructional materials.

My primary output format is HTML. The existing WAVE ( 
http://wave.webaim.org/  <http://wave.webaim.org/>) tool seems to work well 
as a post-processor. The HTML template would likely need to be tweaked to 
generate accessible documents and authors will need to write to certain 
conventions, of course. There may be other tools for other formats.

However, it might be possible to write a filter that does some checks on 
the Pandoc AST to warn authors that there may be accessibility issues, much 
like what WAVE does, but in general. Of course, it is likely not possible 
to check all the WCAG 2.0 AA issues at that level. And, this would not 
guarantee that the writers are well-behaved.

In the HTML format, I currently generate MathML but MathJax would support a 
broader array fo browsers.


On Thursday, November 2, 2017 at 5:38:04 PM UTC-5, Kolen Cheung wrote:
>
> I didn’t recall there’s such a tool (I could be wrong though). Have you 
> read through the pandoc-extras in pandoc’s wiki page on GitHub? It seems 
> using a post-processor to check and work backward to tweak your template is 
> the way to go. Although pandoc’s output generally is quite good, but pandoc 
> is no linter as it is not designed to be. So I don’t imagine any tool other 
> than post-processor would help. Even if there’s a template designed to 
> conform to a certain requirements, what pandoc writes could break it that 
> requirement. And then pre-processor/filter are even more difficult to do 
> what you need, because it doesn’t see the resultant format. 
>
> Does the doc involve math? If you use MathJax, I think it has been built 
> with accessibility in mind.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/8ee5cb0b-b90a-4167-9616-7d4f16c18fd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 3053 bytes --]