emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jude DaShiell <jdashiel@panix.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: Timothy <orgmode@tec.tecosaur.net>,
	Ihor Radchenko <yantar92@gmail.com>,
	 emacs-orgmode@gnu.org
Subject: Re: org exported pdf files
Date: Wed, 28 Sep 2022 09:02:13 -0400	[thread overview]
Message-ID: <1f90ea22-de8b-a58f-6b20-a0984f67eeac@panix.com> (raw)
In-Reply-To: <867d1nj1yn.fsf@gmail.com>

I've never done anything with latex.  The closest I got to latex was using
groff for a little bit of time a long time ago.  On this one I'm in way
over my head without scuba gear.  Apparently html and adobe left latex in
the dust in so far as accessibility is concerned.



Jude <jdashiel at panix dot com> "There are four boxes to be used in
defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

On Wed, 28 Sep 2022, Tim Cross wrote:

>
> Jude DaShiell <jdashiel@panix.com> writes:
>
> > It was one of the messages from this list that got me that reply.  For
> > now, when I get a pdf file I try extracting it with pdftotext and read the
> > extracted text.  I don't make pdf files or make pdf files available for
> > anyone else.  How adobe accessibility recommendations for pdf files will
> > translate to Linux I don't know many were geared toward windows if memory
> > serves.  I haven't used windows since 2013 and don't intend using windows
> > for the duration either.
> >
>
> The problem is not with org mode, but rather with the limitations of
> Latex. The basic problem is that latex pre-dates accessibility concerns
> and lacks full support for tagging, alt text and other document
> structure information necessary to make PDF files accessible. Adding a
> language environment setting will have only minimal benefit. It is the
> tagging and other structural information which is necessary to make
> things really accessible i.e. the ability to browse a PDF document and
> retain the structural relationships within the document and use that
> information in a meaningful way - consider for example, browsing data
> inside a table within a PDF document.
>
> There are accessibility working groups within the tex/latex community
> who have been working on trying to improve accessibility of documents
> created using latex and some progress has been made. However, it is
> nowhere near the same level of sophistication as supported by other PDF
> generators, like adobe's suite, which has very good accessibility
> support and can enable production of some of the best accessible
> documents I've used.
>
> There are a couple of additional latex packages which can be added to
> documents which will provide some tagging and other structural
> information which will significantly improve the accessibility of PDF
> documents. I've not tested these with different engines.
>
> https://ctan.org/pkg/accessibility?lang=en
>
> and you would want ot add
>
> \usepackage[tagged, highstructure]{accessibility}
>
> to your packages list.
>
> To add accessibility for math formulas etc, you need
>
> https://ctan.org/pkg/axessibility?lang=en
>
> and add
>
> \usepackage{axessibility}
>
> As with other authoring, you also need to consider accessibility
> requirements when creating your documents and do things like adding \alt
> textg for figures etc.
>
> It would probably be good to add the two above packages as part of the
> 'default' package preamble, but this would require considerable testing
> as it isn't known if there will be adverse effects when mixed with other
> packages.
>
>
>


  parent reply	other threads:[~2022-09-28 13:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  1:48 org exported pdf files Jude DaShiell
2022-09-27  2:48 ` Ihor Radchenko
2022-09-27  3:15   ` Jude DaShiell
2022-09-27  3:24     ` Ihor Radchenko
2022-09-27  4:31       ` Jude DaShiell
2022-09-27  4:58         ` Ihor Radchenko
2022-09-28  4:36           ` Jude DaShiell
2022-09-28  4:53             ` Timothy
2022-09-28  6:48               ` Jude DaShiell
2022-09-28  8:47                 ` Tim Cross
2022-09-28  9:19                   ` Timothy
2022-09-28 17:08                     ` Tim Cross
2022-09-28 17:39                       ` Timothy
2022-09-28 18:23                       ` Juan Manuel Macías
2022-09-29 20:58                         ` Tim Cross
2022-09-29  4:09                       ` Org HTML export accessibility (was: org exported pdf files) Ihor Radchenko
2022-09-29  8:22                         ` Tim Cross
2022-09-29 11:43                           ` Jude DaShiell
2022-09-29 21:05                           ` Apology [was: Re: Org HTML export accessibility (was: org exported pdf files)) Tim Cross
2022-09-30  5:34                             ` tomas
2022-10-02 10:59                             ` Apology [ Fraga, Eric
2022-10-02  9:42                           ` [HELP] Help implementing org-lint/warnings buffer during export (was: Org HTML export accessibility (was: org exported pdf files)) Ihor Radchenko
2022-10-02 20:52                             ` Tim Cross
2022-10-03  3:25                               ` Ihor Radchenko
2022-09-29  7:07                       ` org exported pdf files Max Nikulin
2022-09-29 21:00                         ` Tim Cross
2022-10-01 10:55                       ` Max Nikulin
2022-09-28 13:02                   ` Jude DaShiell [this message]
2022-09-28 16:12                 ` Max Nikulin
2022-09-27 11:08         ` Max Nikulin
2022-09-28  3:07           ` Ihor Radchenko
2022-09-28 15:58             ` Max Nikulin
2022-09-29  4:12               ` Add \usepackage{cmap} as default LaTeX class in ox-latex (was: org exported pdf files) Ihor Radchenko
2022-09-29 15:34                 ` Max Nikulin

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=1f90ea22-de8b-a58f-6b20-a0984f67eeac@panix.com \
    --to=jdashiel@panix.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@tec.tecosaur.net \
    --cc=theophilusx@gmail.com \
    --cc=yantar92@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).