W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2017

RE: PDF14 Running headers and footers

From: Gill Whitney <G.Whitney@mdx.ac.uk>
Date: Fri, 7 Apr 2017 08:38:11 +0000
To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <DB5PR0101MB1621C99C895C6A94B9E3A3EFAE0C0@DB5PR0101MB1621.eurprd01.prod.exchangelabs.com>
I agree that it would be very useful if we had a way of ensuring that LaTeX documents could be accessible.

Gill Whitney

-----Original Message-----
From: Michael A. Peters [mailto:mpeters@domblogger.net] 
Sent: 07 April 2017 08:25
To: w3c-wai-ig@w3.org
Subject: Re: PDF14 Running headers and footers

Off topic *slightly* but one frustrating thing I found when looking for accessibility guidelines for PDF is absolutely nothing on any of the standard standard sites that reference LaTeX.

I know LaTeX is virtually never used in typical business, but it is very heavily used in STEM and probably will continue to be used in STEM for some time due to its exceptional math typesetting, high portability (available on virtually any platform), journals often require submission in LaTeX, and the fact that you compile the final document from text files that work well in version control systems like git and svn.

STEM may be a minority market of geeks, but those types of documents should be accessible.

For what it is worth, most PDF documents created in LaTeX are created with the pdflatex binary and usually use the hyperref macro package, which has some macros specifically for PDF features.

I suspect that with hyperref the vast majority of PDF accessibility issues can be addressed, but they won't be met if the guidelines only include documentation for the commercial business oriented tools.

It would be nice of someone who understands both PDF and LaTeX could be found to help write some notes on how to meet the PDF accessibility guidelines in LaTeX.

On 04/04/2017 06:51 AM, David MacDonald wrote:
> http://davidmacd.com/blog/pdf-headers-footers.html

>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd <http://twitter.com/davidmacd>
>
> GitHub <https://github.com/DavidMacDonald>
>
> www.Can-Adapt.com <http://www.can-adapt.com/>
>
>
>
> /  Adapting the web to *all* users/
>
> /            Including those with disabilities/
>
> If you are not the intended recipient, please review our privacy 
> policy <http://www.davidmacd.com/disclaimer.html>
>
> On Tue, Apr 4, 2017 at 5:48 AM, Vlerken-Thonen, M. van (Michèlle) - 
> Logius <michelle.van.vlerkenthonen@logius.nl
> <mailto:michelle.van.vlerkenthonen@logius.nl>> wrote:
>
>     The PDF checker at http://checkers.eiii.eu/en/pdfcheck/

>     <http://checkers.eiii.eu/en/pdfcheck/> often returns the following
>     result:____
>
>     __ __
>
>     Fail: running headers and footers. Running headers and footers are
>     not provided or running headers and footers provided are
>     inconsistent with the section headers.____
>
>     __ __
>
>     However, PDF14 is only an advisory technique for 3.2.3. ____
>
>     __ __
>
>     Therefore I wonder what the importance of this technique is for PDF
>     files. Do running headers and footers always have to be present? And
>     is it a problem if some text in the header/footer is marked as an
>     artifact in InDesign but not as a header/footer (assuming the
>     important information in this text is also added to the main text on
>     the front page).____
>
>     __ __
>
>     Thanks for any insights.____
>
>     __ __
>
>     Michèlle____
>
>
>     ------------------------------------------------------------------------
>     Dit bericht kan informatie bevatten die niet voor u is bestemd.
>     Indien u niet de geadresseerde bent of dit bericht abusievelijk aan
>     u is toegezonden, wordt u verzocht dat aan de afzender te melden en
>     het bericht te verwijderen. De Staat aanvaardt geen
>     aansprakelijkheid voor schade, van welke aard ook, die verband houdt
>     met risico's verbonden aan het elektronisch verzenden van berichten.
>     This message may contain information that is not intended for you.
>     If you are not the addressee or if this message was sent to you by
>     mistake, you are requested to inform the sender and delete the
>     message. The State accepts no liability for damage of any kind
>     resulting from the risks inherent in the electronic transmission of
>     messages.
>
>


Received on Friday, 7 April 2017 08:38:47 UTC

This archive was generated by hypermail 2.3.1 : Friday, 7 April 2017 08:38:48 UTC