From: "Connor P. Jackson via ntg-context" <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: "Connor P. Jackson" <connor@cpjackson.net>
Subject: Adobe Acrobat accessibility criteria
Date: Mon, 26 Jul 2021 18:11:36 -0700 [thread overview]
Message-ID: <CAD5a2m4b=30eeN=N7cbsDMQ9m-Oo2VmN+Rt9oHucXdtcrnmJkw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1617 bytes --]
Hello ConTeXt friends,
I am newly exploring ConTeXt in search of a better way to produce PDF/UA-1
accessible and PDF/A compliant documents programmatically. From my early
experiments, ConTeXt docs appear to fully satisfy the veraPDF validator,
but Adobe Acrobat’s Accessibility Checker has three qualms with
ConTeXt-produced documents:
1. The document is configured to display the file name rather than the
title in the top of the window (DisplayDocTitle == True is what I think is
required). See here <https://www.w3.org/TR/WCAG20-TECHS/PDF18.html>.
2. "Tagged Annotations" fails, suggesting that the document’s links are
not properly tagged. I believe the issue is missing "Link - OBJR” (object
reference) tags. See here
<https://amp.levelaccess.net/public/standards/view_best_practice.php?violation_id=807>,
here <https://www.w3.org/TR/WCAG20-TECHS/PDF11.html>, and here
<http://verapdf.org>.
3. "Tab Order" fails, I believe because ConTeXt does not specify that
the tab order should follow the Document Structure, so Acrobat reads it as
unspecified. See here <https://www.w3.org/TR/WCAG20-TECHS/PDF3.html>.
Is there something I could be doing to correct these issues in my ConTeXt
documents? Or is this a change that would have to be made within
ConTeXt itself? I know that Adobe is not the definitive arbiter of what an
“accessible” PDF looks like, but for many organizations, passing the
Acrobat accessibility checker is a prerequisite, so it seems worthwhile to
me to make ConTeXt capable of it.
Many thanks!
Connor Jackson
[-- Attachment #1.2: Type: text/html, Size: 1947 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2021-07-27 1:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 1:11 Connor P. Jackson via ntg-context [this message]
2021-07-27 7:35 ` Hans Hagen via ntg-context
2021-07-28 3:05 ` Connor P. Jackson via ntg-context
2021-07-28 9:51 ` Hans Hagen via ntg-context
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='CAD5a2m4b=30eeN=N7cbsDMQ9m-Oo2VmN+Rt9oHucXdtcrnmJkw@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=connor@cpjackson.net \
/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.
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 NNTP newsgroup(s).