From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Ulrike Fischer <luatex-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Generating Tagged PDFs That Are Accessible to Screen Readers?
Date: Tue, 02 Apr 2019 08:37:09 -0700 [thread overview]
Message-ID: <yh480ka7h8ju56.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <e1r9tb6rvroj.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
> The problem is that I don't want something only working with latex
> generated from other format like markdown or html and pandoc can't
> tag all existing latex documents.
> E.g. if I compile this with pandoc to html
>
> \documentclass{article}
> \usepackage{lipsum}
> \begin{document}
> abc
>
> \lipsum[1-3]
> \end{document}
>
> then the output is <p>abc</p> and the lipsum is lost.
Yes, I completely understand the need to make this
work in regular LaTeX documents. But I don't see a
good way right now to tag paragraphs automatically.
That seems the biggest sticking point: if you can
solve this, it will be great!
(I have been trying to use tagpdf to make a book
I'm working on accessible, and this is the biggest
stumbling block. I don't want to go back through
the whole book inserting special environments
around every paragraph!)
next prev parent reply other threads:[~2019-04-02 15:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 14:42 Brandon Keith Biggs
2019-04-01 8:10 ` Ulrike Fischer
[not found] ` <ukrij1lawu2s.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
2019-04-01 9:21 ` Brandon Keith Biggs
2019-04-01 9:59 ` Ulrike Fischer
[not found] ` <1jnewh8r1pdrv$.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
2019-04-01 18:22 ` John MacFarlane
2019-04-01 21:33 ` Ulrike Fischer
[not found] ` <2vap744mxcf1.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
2019-04-02 0:07 ` John MacFarlane
2019-04-02 9:04 ` Ulrike Fischer
[not found] ` <e1r9tb6rvroj.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
2019-04-02 9:38 ` Brandon Keith Biggs
2019-04-02 15:37 ` John MacFarlane [this message]
2019-04-02 21:19 ` Ulrike Fischer
[not found] ` <1lce9q7wcf06g.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
2019-06-01 6:37 ` Pranesh Prakash
[not found] ` <yh480kimvxjmmn.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-04-02 9:21 ` Brandon Keith Biggs
[not found] ` <CAKAWQkW03eFnLofHrVfWsDQVm4bFFUPkwuzc-t10GGiqJuv-AA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-03-31 17:50 ` BP Jonsson
2019-04-02 19:59 ` Václav Haisman
2019-04-02 20:13 ` Ulrike Fischer
2019-06-20 11:02 ` CR
[not found] ` <dbeb757a-cf86-45f1-85a4-22005b296424-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-11-06 9:09 ` Pranesh Prakash
2020-02-05 14:03 ` Ignacio Jonatan Hernández López
[not found] ` <c0988854-abbb-4f44-8e7b-75f7c95066f6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-02-05 19:16 ` Brandon Keith Biggs
2020-10-20 17:45 ` Pranesh Prakash
[not found] ` <e8bf8cd7-c96e-4a4f-b99b-04abf645985en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-10-20 17:54 ` Leonard Rosenthol
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=yh480ka7h8ju56.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=luatex-bMiYgyzgJ3Ab1SvskN2V4Q@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).