From: William Henney <firstname.lastname@example.org>
To: Rasmus <email@example.com>
Cc: emacs-org <firstname.lastname@example.org>
Subject: Re: pdf screen reader accessibility?
Date: Wed, 8 Apr 2015 12:22:58 -0600 [thread overview]
Message-ID: <CAKchnZN3=wEYEr85AAV65k_Bxh+-Fi+9Z3LWJYBo_dYRMr8hUw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
On Mon, Apr 6, 2015 at 7:19 AM, Rasmus <email@example.com> wrote:
> Marcin Borkowski <firstname.lastname@example.org> writes:
> > On 2015-04-06, at 13:40, Rasmus <email@example.com> wrote:
> >> Jude DaShiell <firstname.lastname@example.org> writes:
> >>> http://www.adobe.com/accessibility/products.html
> >>> is a good place to start.
> >> It's a list of a bunch of software packages of which most are not (i)
> >> in any meaning of the word; and (ii) supported on GNU/Linux.
> > So what? IIUC, the OP wants to have something similar using Emacs and
> > (maybe) free (in a usual sense, or in FSF sense) software. Isn't it
> > a valid request?
> Of course it is, but OP is referring to features of some software that I
> don't have access to, so how am I supposed to make sense of it? I'm not
> going to (i) install a new OS; and (ii) buy/torrent software to understand
> and test a feature in named software.
> If there's a standard I'm eager to hear about it.
I believe the relevant standard is PDF/UA
As far as I can tell, support for this from LaTeX is still very much a work
in progress, but there is an accessibility.sty package that has made a
start. Here is a recent SO discussion:
Dr William Henney, Centro de Radioastronomía y Astrofísica,
Universidad Nacional Autónoma de México, Campus Morelia
[-- Attachment #2: Type: text/html, Size: 2603 bytes --]
next prev parent reply other threads:[~2015-04-08 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 8:25 pdf screen reader accessibility? 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 [this message]
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
2015-04-07 7:49 Jude DaShiell
2015-04-07 8:12 ` Rasmus
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).