From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/23454 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: mb21 Newsgroups: gmane.text.pandoc Subject: Re: Accessibility of Generated Docx Date: Sun, 22 Sep 2019 03:10:24 -0700 (PDT) Message-ID: References: <677959fb-29b8-4eaa-837f-c53e5ea5ab51@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1075_86757994.1569147024491" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="79747"; mail-complaints-to="usenet@blaine.gmane.org" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBDCMBBVJ5EFBBEMRTXWAKGQEYKAFHBY-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Sun Sep 22 12:10:28 2019 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-ot1-f58.google.com ([209.85.210.58]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1iByp1-000KZ3-Fb for gtp-pandoc-discuss@m.gmane.org; Sun, 22 Sep 2019 12:10:27 +0200 Original-Received: by mail-ot1-f58.google.com with SMTP id d12sf1374850ote.0 for ; Sun, 22 Sep 2019 03:10:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe; bh=3TbSpYkdoD6gi6qhiKVZgu9sBXvWIyqiaOtNq3H/kjc=; b=Aro2pG6KtH1W45RtJQZX5zgQgJDaLV1sVPOuKS7aB300niaIwBK94G48fZWrR+9fz/ Wrn9SLrpY8J9FdFDx4QZbLPGz9fafvQtrrGvuDCI4DBtswBogSetrxueU39iOhUXY200 mGqyj5P82UxrLwjTMMSRmxuEy28jYF+Pnh+OhyH9m8vPRaeB6D6Acl3hWC9IbEDVOF+Q De8Q8oLyVfqWBUwWPINSyS0F1OXb/U4bFqG8d9LWjncUQQK4VkYfl2qm+QRl3hoNBbIz RafYVW5IJZfNudqpVsX42g2abh95Y5W4OXv2tJtdDwdxSA/LCheaK/+VcI6QOCbztDW1 vEDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=3TbSpYkdoD6gi6qhiKVZgu9sBXvWIyqiaOtNq3H/kjc=; b=Jne3KZgeGk/QNZy2Csrv6YArN6k02YD7C8s8GPzUite/uJElKK2KPRPnrVbrCSADV8 3U/Q0EWPRUNv1f6RDGvxNQBuQHwX1Q+h1dm0dtuCw4HLz7cUpw2nUO4ZMMGsOgg4+f9y elQCimv5qP5PjIsG1DUNbLWJ9x88DzMoRfhNo5QJANOzXamdeIvxOvTzOzyq/2JaWmn4 VpzX3kuyoCY1ASRU9vBCBNm61fOXf3JcBBvVG7Xna/Ja0nrNSJLEbOij+a+iNJuGgGaz t06iTkehBPBa+rRiuA6IUW4rC9os8vSjcAhBO2YGnc+q7dBQMnuQHBzHzkuZtcZ//4+K IBYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=sender:x-gm-message-state:date:from:to:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=3TbSpYkdoD6gi6qhiKVZgu9sBXvWIyqiaOtNq3H/kjc=; b=uKaZ4X9bnOzIZhcuix43fyIvxJKj7kwuJs2NEOoszMmWvA9Aw26V+q8CKius7cvS3L RXyYzEL4cYuQ3nggrCDLVxCZLIl9zf51SzUWuLU3l5XhGE09QimRguToB5+qHU1R7iek KMGw9niNXIpKuTXvK7hcxgtXoMaXz79WocQQzSYW/qaEpMUh+ITXOUun0a4Nd3Ynj5ID GyVovVUsAI0Jlc2SOJ4bH8NbbBVNmdoj0UPOw74NplfCuAK8iZNs2APQWGD4wgsWssid LwFmFfjIy3lI/E/4iis1qWy4gbR3Ltnb9/UdxFLVpcqxAr3VFkpZf6QHfP5WkqosEfDo tzAw== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: APjAAAVMLYH/beH6PCJYI2PDQuszo2syX+R8/wSYWqkLdK/NBWOPSdwV FsiAqLknLWeAIDr6GBJoaO8= X-Google-Smtp-Source: APXvYqzz1FZes3sV1nasrWwASBcxBsynCsPmUCHUx7qmo+HxlUKKEGU2tmFnQS9PcXY2K7mvW3R+5g== X-Received: by 2002:a9d:4c02:: with SMTP id l2mr12371816otf.326.1569147026207; Sun, 22 Sep 2019 03:10:26 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a9d:813:: with SMTP id 19ls1078698oty.11.gmail; Sun, 22 Sep 2019 03:10:25 -0700 (PDT) X-Received: by 2002:a9d:2007:: with SMTP id n7mr17327045ota.132.1569147025098; Sun, 22 Sep 2019 03:10:25 -0700 (PDT) In-Reply-To: X-Original-Sender: mauro.bieg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.org gmane.text.pandoc:23454 Archived-At: ------=_Part_1075_86757994.1569147024491 Content-Type: multipart/alternative; boundary="----=_Part_1076_1225123360.1569147024492" ------=_Part_1076_1225123360.1569147024492 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable You can try: pandoc --pdf-engine=3Dcontext -M pdfa -o output.pdf see the description of pdfa in=20 https://pandoc.org/MANUAL.html#variables-for-context Maybe the pdfa part is not even needed, since the default pandoc context=20 template includes \setuptagging[state=3Dstart] On Saturday, September 21, 2019 at 7:54:29 PM UTC+2, John MacFarlane wrote: > > > You can try using alternative paths to pdf (--pdf-engine supports=20 > a number of options, some via HTML, and they may do better for=20 > accessibility, I'm not sure).=20 > > Conrad Cunningham > writes:=20 > > > Thanks.=20 > >=20 > > It is useful that Pandoc=E2=80=99s docx writer generates files in compa= tibility=20 > mode and that the generated documents are accessible.=20 > >=20 > > Given my institution=E2=80=99s push to make all public documents access= ible, I=20 > am looking at convenient (automatable) ways to get my Pandoc-flavored=20 > course documents into accessible PDFs and other accessible formats.=20 > Unfortunately, mLaTeX-to-PDF support for PDF/UA seems =E2=80=9Cnot ready = for prime=20 > time=E2=80=9D.=20 > >=20 > >> On Sep 13, 2019, at 3:00 PM, BP Jonsson > wrote:=20 > >>=20 > >> I believe compatibility mode is helpful also when opening docx files i= n=20 > LibreOffice. At least even quite large files produced by Pandoc open much= =20 > faster than some DOCX files people send me.=20 > >>=20 > >>=20 > >> Den fre 13 sep. 2019 19:31John MacFarlane > skrev:=20 > >>>=20 > >>> We use compatibility mode so that the docx pandoc produces=20 > >>> will be readable by the widest variety of Word versions (even=20 > >>> quite old ones).=20 > >>>=20 > >>> This isn't itself an issue with accessibility; it's just an=20 > >>> issue with the Mac's checker I guess, and I don't think we should=20 > >>> modify pandoc just to work around that.=20 > >>>=20 > >>> We could change pandoc to avoid compatibility mode, but that=20 > >>> would mean our docxs can't be read by older Word versions.=20 > >>> At some point it may be worth having this conversation.=20 > >>>=20 > >>> In principle we could have a flag to generate either=20 > >>> compatibility mode or not, but that adds a lot of complexity=20 > >>> for little gain.=20 > >>>=20 > >>> > by using a custom reference document with modified styles. The=20 > warnings=20 > >>> > associated with code blocks, highlighting, etc., seem more=20 > problematic.=20 > >>>=20 > >>> The code coloring is affected by the --highlight-style option. We=20 > >>> provide several styles out of the box, including a monochrome=20 > >>> style which is very high contrast. You can also create and use=20 > >>> your own style. See the docs.=20 > >>>=20 > >>>=20 > >>> Conrad Cunningham > writes:=20 > >>>=20 > >>> > I use pandoc to convert Pandoc-flavored Markdown documents to HTML= =20 > >>> > (primarily), Word docx, PDF (via LaTeX), etc. I am currently using= =20 > pandoc=20 > >>> > 2.7.3. Microsoft Word for Mac 16.16.14, and MacTeX 2019 on MacOS=20 > 10.14.6=20 > >>> > (Mojave).=20 > >>> >=20 > >>> > According to the tests I have run using the WebAIM WAVE tool, the= =20 > >>> > accessibility of the generated HTML is reasonable. (I need to give= =20 > some=20 > >>> > attention to places in the Markdown input where I use tables and al= t=20 > text.)=20 > >>> >=20 > >>> > For the generated docx, I am using Word for Mac's builtin=20 > accessibility=20 > >>> > checker. I found that the generated docx is in compatibility mode.= =20 > Word for=20 > >>> > Mac's accessibility checker cannot process that kind of file. If I= =20 > load the=20 > >>> > file into Word and then save as a normal docx, the checker will run= .=20 > >>> >=20 > >>> > Is there a less inconvenient way to get the generated output into= =20 > the=20 > >>> > normal docx mode? I would like to get the final output by running a= =20 > shell=20 > >>> > script on the Markdown input.=20 > >>> >=20 > >>> > The issues I have found so far in my limited tests are warnings=20 > about=20 > >>> > insufficient color contrasts and sequences of blank characters. Som= e=20 > of=20 > >>> > these (e.g., colors in section headers and hyperlinks) seem to be= =20 > fixable=20 > >>> > by using a custom reference document with modified styles. The=20 > warnings=20 > >>> > associated with code blocks, highlighting, etc., seem more=20 > problematic.=20 > >>> >=20 > >>> > --=20 > >>> > You received this message because you are subscribed to the Google= =20 > Groups "pandoc-discuss" group.=20 > >>> > To unsubscribe from this group and stop receiving emails from it,= =20 > send an email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org .=20 > >>> > To view this discussion on the web visit=20 > https://groups.google.com/d/msgid/pandoc-discuss/677959fb-29b8-4eaa-837f-= c53e5ea5ab51%40googlegroups.com.=20 > > >>>=20 > >>> --=20 > >>> You received this message because you are subscribed to the Google=20 > Groups "pandoc-discuss" group.=20 > >>> To unsubscribe from this group and stop receiving emails from it, sen= d=20 > an email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org .=20 > >>> To view this discussion on the web visit=20 > https://groups.google.com/d/msgid/pandoc-discuss/yh480k1rwk6r2b.fsf%40joh= nmacfarlane.net.=20 > > >>=20 > >> --=20 > >> You received this message because you are subscribed to a topic in the= =20 > Google Groups "pandoc-discuss" group.=20 > >> To unsubscribe from this topic, visit=20 > https://groups.google.com/d/topic/pandoc-discuss/Y8Q1z1mdgVM/unsubscribe.= =20 > >> To unsubscribe from this group and all its topics, send an email to=20 > pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org .=20 > >> To view this discussion on the web visit=20 > https://groups.google.com/d/msgid/pandoc-discuss/CAFC_yuTPDWN5yxYnSObFq3k= iRp%2BZ%3DY3Kvd%2B67g16qz4D%2BEgeLA%40mail.gmail.com.=20 > > >=20 > > --=20 > > You received this message because you are subscribed to the Google=20 > Groups "pandoc-discuss" group.=20 > > To unsubscribe from this group and stop receiving emails from it, send= =20 > an email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org .=20 > > To view this discussion on the web visit=20 > https://groups.google.com/d/msgid/pandoc-discuss/DF338AD1-4D4E-461B-8A66-= F30986A9015E%40gmail.com.=20 > > --=20 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 e= mail 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/b37da1b5-c763-4fc0-9006-d69f2a5a0b64%40googlegroups.com. ------=_Part_1076_1225123360.1569147024492 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You can try:

pandoc --pdf-engine=3Dcont= ext -M pdfa -o output.pdf

see the description of pdfa in= https://pandoc.org/MANUAL.html#variables-for-context

<= div>Maybe the pdfa part is not even needed, since the default pandoc contex= t template includes=C2=A0\setuptagging[state=3Dstart]

<= div>

On Saturday, September 21, 2019 at 7:54:29 PM UTC+2, John MacFa= rlane wrote:

You can try using alternative paths to pdf (--pdf-engine supports
a number of options, some via HTML, and they may do better for
accessibility, I'm not sure).

Conrad Cunningham <hcc.o...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Thanks.=20
>
> It is useful that Pandoc=E2=80=99s docx writer generates files in = compatibility mode and that the generated documents are accessible.=20
>
> Given my institution=E2=80=99s push to make all public documents a= ccessible, I am looking at convenient (automatable) ways to get my Pandoc-f= lavored course documents into accessible PDFs and other accessible formats.= Unfortunately, mLaTeX-to-PDF support for PDF/UA seems =E2=80=9Cnot ready f= or prime time=E2=80=9D.=20
>
>> On Sep 13, 2019, at 3:00 PM, BP Jonsson <bpjo...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org&g= t; wrote:
>>=20
>> I believe compatibility mode is helpful also when opening docx= files in LibreOffice. At least even quite large files produced by Pandoc o= pen much faster than some DOCX files people send me.
>>=20
>>=20
>> Den fre 13 sep. 2019 19:31John MacFarlane <j...-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org= > skrev:
>>>=20
>>> We use compatibility mode so that the docx pandoc produces
>>> will be readable by the widest variety of Word versions (e= ven
>>> quite old ones).
>>>=20
>>> This isn't itself an issue with accessibility; it'= s just an
>>> issue with the Mac's checker I guess, and I don't = think we should
>>> modify pandoc just to work around that.
>>>=20
>>> We could change pandoc to avoid compatibility mode, but th= at
>>> would mean our docxs can't be read by older Word versi= ons.
>>> At some point it may be worth having this conversation.
>>>=20
>>> In principle we could have a flag to generate either
>>> compatibility mode or not, but that adds a lot of complexi= ty
>>> for little gain.
>>>=20
>>> > by using a custom reference document with modified st= yles. The warnings=20
>>> > associated with code blocks, highlighting, etc., seem= more problematic.
>>>=20
>>> The code coloring is affected by the --highlight-style opt= ion. We
>>> provide several styles out of the box, including a monochr= ome
>>> style which is very high contrast. You can also create and= use
>>> your own style. See the docs.
>>>=20
>>>=20
>>> Conrad Cunningham <hcc.o...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>>=20
>>> > I use pandoc to convert Pandoc-flavored Markdown docu= ments to HTML=20
>>> > (primarily), Word docx, PDF (via LaTeX), etc. I am cu= rrently using pandoc=20
>>> > 2.7.3. Microsoft Word for Mac 16.16.14, and MacTeX 20= 19 on MacOS 10.14.6=20
>>> > (Mojave).
>>> >
>>> > According to the tests I have run using the WebAIM WA= VE tool, the=20
>>> > accessibility of the generated HTML is reasonable. (I= need to give some=20
>>> > 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=20
>>> > checker. I found that the generated docx is in compat= ibility mode. Word for=20
>>> > Mac's accessibility checker cannot process that k= ind of file. If I load the=20
>>> > file into Word and then save as a normal docx, the ch= ecker will run.
>>> >
>>> > Is there a less inconvenient way to get the generated= output into the=20
>>> > normal docx mode? I would like to get the final outpu= t by running a shell=20
>>> > script on the Markdown input.
>>> >
>>> > The issues I have found so far in my limited tests ar= e warnings about=20
>>> > insufficient color contrasts and sequences of blank c= haracters. Some of=20
>>> > these (e.g., colors in section headers and hyperlinks= ) seem to be fixable=20
>>> > by using a custom reference document with modified st= yles. The warnings=20
>>> > associated with code blocks, highlighting, etc., seem= more problematic.
>>> >
>>> > --=20
>>> > You received this message because you are subscribed = to the Google Groups "pandoc-discuss" group.
>>> > To unsubscribe from this group and stop receiving ema= ils from it, send an email to pandoc-...@googlegroups.com.
>>> > To view this discussion on the web visit ht= tps://groups.google.com/d/msgid/pandoc-discuss/677959fb-29b8-4eaa= -837f-c53e5ea5ab51%40googlegroups.com.
>>>=20
>>> --=20
>>> You received this message because you are subscribed to th= e Google Groups "pandoc-discuss" group.
>>> To unsubscribe from this group and stop receiving emails f= rom it, send an email to pandoc-...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/<= wbr>yh480k1rwk6r2b.fsf%40johnmacfarlane.net.
>>=20
>> --=20
>> You received this message because you are subscribed to a topi= c in the Google Groups "pandoc-discuss" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to= pic/pandoc-discuss/Y8Q1z1mdgVM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an ema= il to pandoc-...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.c= om/d/msgid/pandoc-discuss/CAFC_yuTPDWN5yxYnSObFq3kiRp%2BZ%3D= Y3Kvd%2B67g16qz4D%2BEgeLA%40mail.gmail.com.
>
> --=20
> 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-...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msg= id/pandoc-discuss/DF338AD1-4D4E-461B-8A66-F30986A9015E%40gmail.co= m.

--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/= msgid/pandoc-discuss/b37da1b5-c763-4fc0-9006-d69f2a5a0b64%40googlegroups.co= m.
------=_Part_1076_1225123360.1569147024492-- ------=_Part_1075_86757994.1569147024491--