From: Conrad Cunningham <hcc.olemiss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Accessibility of Pandoc Documents
Date: Thu, 2 Nov 2017 07:30:07 -0700 (PDT) [thread overview]
Message-ID: <97f31872-3cd8-40f3-a099-e20aee8f5433@googlegroups.com> (raw)
[-- 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 --]
next reply other threads:[~2017-11-02 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 14:30 Conrad Cunningham [this message]
[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
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=97f31872-3cd8-40f3-a099-e20aee8f5433@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).