From: Conrad Cunningham <hcc.olemiss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Accessibility of Generated Docx
Date: Thu, 12 Sep 2019 14:21:51 -0700 (PDT) [thread overview]
Message-ID: <677959fb-29b8-4eaa-837f-c53e5ea5ab51@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1693 bytes --]
I use pandoc to convert Pandoc-flavored Markdown documents to HTML
(primarily), Word docx, PDF (via LaTeX), etc. I am currently using pandoc
2.7.3. Microsoft Word for Mac 16.16.14, and MacTeX 2019 on MacOS 10.14.6
(Mojave).
According to the tests I have run using the WebAIM WAVE tool, the
accessibility of the generated HTML is reasonable. (I need to give some
attention to places in the Markdown input where I use tables and alt text.)
For the generated docx, I am using Word for Mac's builtin accessibility
checker. I found that the generated docx is in compatibility mode. Word for
Mac's accessibility checker cannot process that kind of file. If I load the
file into Word and then save as a normal docx, the checker will run.
Is there a less inconvenient way to get the generated output into the
normal docx mode? I would like to get the final output by running a shell
script on the Markdown input.
The issues I have found so far in my limited tests are warnings about
insufficient color contrasts and sequences of blank characters. Some of
these (e.g., colors in section headers and hyperlinks) seem to be fixable
by using a custom reference document with modified styles. The warnings
associated with code blocks, highlighting, etc., seem more problematic.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/677959fb-29b8-4eaa-837f-c53e5ea5ab51%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2125 bytes --]
next reply other threads:[~2019-09-12 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 21:21 Conrad Cunningham [this message]
[not found] ` <677959fb-29b8-4eaa-837f-c53e5ea5ab51-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-12 23:15 ` Devin Prater
2019-09-13 17:31 ` John MacFarlane
[not found] ` <yh480k1rwk6r2b.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-13 20:00 ` BP Jonsson
[not found] ` <CAFC_yuTPDWN5yxYnSObFq3kiRp+Z=Y3Kvd+67g16qz4D+EgeLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-09-20 18:53 ` Conrad Cunningham
[not found] ` <DF338AD1-4D4E-461B-8A66-F30986A9015E-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-09-21 17:54 ` John MacFarlane
[not found] ` <m2lfuh358a.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-22 10:10 ` mb21
[not found] ` <b37da1b5-c763-4fc0-9006-d69f2a5a0b64-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-25 3:54 ` 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=677959fb-29b8-4eaa-837f-c53e5ea5ab51@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).