From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Adobe Acrobat accessibility criteria
Date: Tue, 27 Jul 2021 09:35:28 +0200 [thread overview]
Message-ID: <76c799fe-6ed3-03d7-5aae-a08dd78b36d7@xs4all.nl> (raw)
In-Reply-To: <CAD5a2m4b=30eeN=N7cbsDMQ9m-Oo2VmN+Rt9oHucXdtcrnmJkw@mail.gmail.com>
On 7/27/2021 3:11 AM, Connor P. Jackson via ntg-context wrote:
> 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>.
Does this work at your end?
\setupinteraction
[title=MyTitle,state=start]
\setupinteractionscreen
[option={title}]
\starttext
test
\stoptext
> 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.
Most fo this is rather trivial but we need examples (mwe) and expected
result (in only have an old acrobat x pro and the latest reader, so
maybe i can't check all the latest greatest fancy features).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 prev parent reply other threads:[~2021-07-27 7:35 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
2021-07-27 7:35 ` Hans Hagen via ntg-context [this message]
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=76c799fe-6ed3-03d7-5aae-a08dd78b36d7@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
/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).