emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jude DaShiell <jdashiel@panix.com>
To: emacs-orgmode@gnu.org
Subject: pdf screen reader accessibility?
Date: Mon, 6 Apr 2015 04:25:57 -0400 (EDT)	[thread overview]
Message-ID: <alpine.NEB.2.11.1504060417310.20962@panix2.panix.com> (raw)

http://www.adobe.com/accessibility/products.html
is a good place to start.
When a document gets written in Microsoft Word, its language is made part 
of that document.  If that document is later converted to a pdf file that 
language information is taken in by the conversion process then becomes 
the first component that starts to make screen reader accessibility of a 
pdf file possible.  Other components exist, but without that language 
attribute presence, screen reader accessibility is disabled.  Another 
major requirement is ocr scanned content pictures by themselves in pdf 
files are worthless to screen readers.  I'm using speakup over here on 
archlinux and am curious if it is now possible or some day will be 
possible for me to export to a screen reader accessible pdf file I can 
share with other screen reader users with no fear that the file won't be 
accessible.



-- Twitter: JudeDaShiell

             reply	other threads:[~2015-04-06  8:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06  8:25 Jude DaShiell [this message]
2015-04-06 11:40 ` pdf screen reader accessibility? Rasmus
2015-04-06 12:39   ` Marcin Borkowski
2015-04-06 13:19     ` Rasmus
2015-04-08 18:22       ` William Henney
2015-04-08 18:48         ` Rasmus
2015-04-08 20:22           ` Nick Dokos
2015-04-08 20:27             ` Rasmus
2015-04-08 21:07               ` Helm and multiple-tags in org mode issues Leo Ufimtsev
2015-04-08 21:48               ` pdf screen reader accessibility? Nick Dokos
  -- strict thread matches above, loose matches on Subject: below --
2015-04-07  7:49 Jude DaShiell
2015-04-07  8:12 ` Rasmus

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=alpine.NEB.2.11.1504060417310.20962@panix2.panix.com \
    --to=jdashiel@panix.com \
    --cc=emacs-orgmode@gnu.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. 
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).