From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: pdf screen reader accessibility?
Date: Tue, 07 Apr 2015 10:12:03 +0200 [thread overview]
Message-ID: <877ftobbn0.fsf@gmx.us> (raw)
In-Reply-To: alpine.NEB.2.11.1504070340030.9202@panix3.panix.com
Hi,
Jude DaShiell <jdashiel@panix.com> writes:
> Let's try this with a slightly better url.
> http://webstandards.sonoma-county.org/content.aspx?sid=1014&id=1123#Content
From the above url
> Title field: Enter a meaningful name for the document.
Use #+TITLE.
> Author field
Use #+AUTHOR.
> Subject field
Use #+DESCRIPTION
> Set the appropriate language
Use #+LANGUAGE
> "Add Tags to Document" tool
Use #+KEYWORDS, I guess?
> Correct All Issues from Add Tags Report – All issues listed in the
> Accessibility section of the Add Tags Report must be corrected to make
> the file accessible.
I don't know what this is.
> Manually Tag – If you need to manually tag a section of a PDF page, use
> the TouchUp Reading Order Tool.
Not possible.
> Tagging PDF Content as a Table
I don't know what this is, and there's no text
> [More stuff about manual stuff]
> Step 5 - The Accessibility Statement
Feel free to do so. You could customize org-latex-title-command.
> Step 6 - Add Descriptive Text to Images
Not possible ATM but you can add captions. If a LaTeX package exists for
this, alttext could be added to images.
> Verify and Correct the Reading Order
> Verify Accessibility
I don't know how to do this.
> Optimization and Compatibility
There's a LaTeX options for optimization, I think, but it is not on by
default, but you could add it to org-latex-default-packages.
> Redact Personal and Private Information
See how to add metadata in the top of the file.
Hope it helps,
Rasmus
--
Send from my Emacs
next prev parent reply other threads:[~2015-04-07 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 7:49 pdf screen reader accessibility? Jude DaShiell
2015-04-07 8:12 ` Rasmus [this message]
-- 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
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=877ftobbn0.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).