all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jude DaShiell <jdashiel@panix.com>
To: emacs-orgmode@gnu.org
Subject: pdf screen reader accessibility?
Date: Tue, 7 Apr 2015 03:49:17 -0400 (EDT)	[thread overview]
Message-ID: <alpine.NEB.2.11.1504070340030.9202@panix3.panix.com> (raw)

Let's try this with a slightly better url.
http://webstandards.sonoma-county.org/content.aspx?sid=1014&id=1123#Content
My point is blind people that go down the emacs route when learning linux 
get introduced to org-mode as part of that process.  If they colaborate 
with other blind emacs users on a job that requires them to use pdf files 
as colaboration documents, are those blind emacs and org-mode users going 
to be able to read each other's official documents and have management 
that required the use of pdf documents in the first place also able to 
read those documents?
I take it there's no problem using adobe reader on windows to read an 
org-exported pdf file.  I may have to use windows and adobe reader on 
windows and find an org-mode pdf-export file and do a full accessibility 
check on it with windows before this question gets answered.  Thanks for 
your time and interest.



-- Twitter: JudeDaShiell

             reply	other threads:[~2015-04-07  7:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07  7:49 Jude DaShiell [this message]
2015-04-07  8:12 ` pdf screen reader accessibility? Rasmus
  -- strict thread matches above, loose matches on Subject: below --
2015-04-06  8:25 Jude DaShiell
2015-04-06 11:40 ` 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:48               ` Nick Dokos

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=alpine.NEB.2.11.1504070340030.9202@panix3.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.