Re: org exported pdf files

[Jude DaShiell <jdashiel@panix.com>]

I checked that out and putting the example text into my .emacs file
generates a warning when emacs starts up  I put the parens and everything
between the parens in the .emacs file and that caused the warning to be
thrown.
What may work and circumvent all of this would be to add:
#+LANGUAGE: en
into a text source file which is part of the files exported through
orgmode pdf.
Adobe has plenty of pdf accessibility guidelines available for those
interested in accessibility to implement.
if those #+ items are called orgmode-directives maybe an
orgmode-accessibility directive could be used at minimum to put the
system's default org-export-language directive into that source text file
that goes into the pdf file.
I have done nothing with exporting to pdf from orgmode since several years
ago I was told orgmode pdf's were not accessible.



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 Tue, 27 Sep 2022, Ihor Radchenko wrote:

> Jude DaShiell <jdashiel@panix.com> writes:
>
> > Having examined 13.10.2, with the polyglossia package installed and
> > accessible to orgmode putting set-language into the right place would
> > default to English and other languages would need to specify their
> > language for a pdf export.
>
> The default can be changed in your Emacs configuration. Check out
> org-export-default-language.
>
> > On Linux I have espeak-ng running as default
> > and I run orca as necessary.  I mostly live on the command line so orca is
> > used rarely.
> > I think a reasonable test of export quality will be to make a pdf with
> > orgmode then run that pdf through pdftotext and compare the extracted text
> > with the pdf file.  I can't do that since without use of pdftotext the
> > screen readers will not work on pdf files.
>
> I checked on of my exported PDFs, and it looks mostly consistent with the
> org source from a brief look. The only minor deficiency is sparkled text
> from included vector images with text, but I imagine that it is common
> and may or may not be a real deficiency.
>
> Do note that Org to PDF export works by first exporting to a .tex file
> and then running TeX. As long as TeX makes a decent job with PDF
> accessibility, we should be good to go. Just need to make sure that we
> pass the correct options to TeX in the generated .tex file.
>
> You mentioned that one of the TeX options is setting the correct
> metadata. I am not aware about other required options that can improve
> accessibility. If you know any, feel free to share.
>
> Also, you can refer to our previous discussion about accessibility of
> documents exported by Org.
> https://list.orgmode.org/orgmode/87czew3w5l.fsf@localhost/
>
>