public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Conrad Cunningham <hcc.olemiss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Accessibility of Pandoc Documents
Date: Thu, 2 Nov 2017 18:57:35 -0700 (PDT)	[thread overview]
Message-ID: <8ee5cb0b-b90a-4167-9616-7d4f16c18fd5@googlegroups.com> (raw)
In-Reply-To: <4669335d-216c-4ab0-8527-4979a3bc6f13-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- 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 --]

      parent reply	other threads:[~2017-11-03  1:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 14:30 Conrad Cunningham
     [not found] ` <97f31872-3cd8-40f3-a099-e20aee8f5433-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-02 22:38   ` Kolen Cheung
     [not found]     ` <4669335d-216c-4ab0-8527-4979a3bc6f13-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-03  1:57       ` Conrad Cunningham [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ee5cb0b-b90a-4167-9616-7d4f16c18fd5@googlegroups.com \
    --to=hcc.olemiss-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).