<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Tagged Mathematics in PDFs for Accessibility and other purposes</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ross Moore</string-name>
          <email>ross.moore@mq.edu.au</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Mathematics Department, Macquarie University</institution>
          ,
          <addr-line>Sydney</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>PDF has been the preferred format for publishing mathematics for many years now. With changes to methods of delivery (i.e., electronic rather than predominantly paper) there need to be corresponding enhancements in the document format. Not least among these can be implicit legal obligations to satisfy Accessibility criteria. The answer developed for PDF is tagging of document structure and content types, as described in the PDF/UA Implementation Guide [4]. Wikipedia describes this as \not a separate le-format but simply a way to use PDF" [12], which when supported \reader software will be able to reliably re ow text onto small screens, provide powerful navigation options, transform text appearance, improve search engine functionality, aid in the selection and copying of text, and more" [12]. Academic publishers are starting to see these bene ts and will doubtless soon require at least minimal tagging of online PDF documents for Accessibility purposes, in a similar way to how Accessibility tags have been incorporated into HTML. Here is a brief overview of work done by the author to incorporate full MathML tagging of mathematical content in documents produced primarily using the LATEX typesetting system. Since the publicly available TEX software was not written to support such tagging of document content, further software tools are also required. This includes using a modi ed version of pdfTEX, a self-developed Perl program, TEX to MathML conversion software, some standard Unix command-line utilities, and extensive use of self-written TEX and LATEX macros. As this work is a continuation of work presented at the CICM meetings in 2009 [5], we concentrate here mostly on the advancements made since then. This includes the ability to capture complete math-environments from a running LATEX job, to automatically invoke a conversion of the LATEX source of the particular piece of mathematics into Presentation MathML using whatever appropriate conversion software is available. Previously the MathML version needed to have been available independent from the LATEX source. Now this conversion can be done `on-the- y', using TEX4HT for example, before merging the MathML and LATEX descriptions of the same piece of mathematics into a new extended LATEX description incorporating macros to cause the generation of appropriate tagging and enrichment to satisfy Accessibility requirements. Such automatic conversion and merging can add signi cantly to the total running time for the whole job, so an indexing system has been developed which</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>allows the resulting enriched LATEX description to be reused with
multiple occurrences of the same source coding within the same job, and to
be available for reuse in subsequent LATEX runs.</p>
      <p>Another development is better control over the words produced for
alternative text, to be read by screen-readers. Where previously this was
largely hard-coded in the enriched LATEX description, this is now replaced
by macros whose expansion text can be customised. This allows for the
possibility of generating speech text in di erent languages, or
customising what is to be spoken according to the eld of mathematics being
described within the document. Such customisations can be done at the
LATEX level, so that a document author need not be involved with the
highly intricate details of conversion to MathML and the enhancements
required for tagging.
1</p>
      <p>
        Background, Overview of \Tagged PDF"
The Web Content Accessibility Guidelines (WCAG 2.0) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], have been developed
primarily for the construction of websites to allow easier access to, and navigation
of, online content by persons having a disability, in particular by people with
visual impairment. The governments of some countries [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], including Canada
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and Australia [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], have established that adherence to these guidelines be a
requirement, at least for their own governmental web presence.
      </p>
      <p>
        While PDF les are not websites, the same principles of Accessibility should
still apply [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], which make tagging of both structure and content within a PDF
document an issue of some importance. Indeed the latest version of Adobe's
`Acrobat Pro' application has a suite of 32 checks which test whether a document
meets various aspects of the WCAG recommendations [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Typically a PDF
produced using LATEX software is lucky to satisfy 11 of these checks, with two others
requiring manual veri cation anyway. Lucky, because some of these checks refer
to content/structure types not even present, hence not deemed to be failing.
      </p>
      <p>
        With the help of a modi ed version of pdfTEX, having extra primitives
specifically to enable production of proper \Tagged PDF" documents, the author has
been able to produce PDFs containing extensive technical and mathematical
content, that fail none of those 32 tests. Such documents are deemed properly
Accessible by Adobe's checks, while at the same time being capable of
validation against both the PDF/A-2b and PDF/A-2u [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] speci cations. Just using the
modi ed version of pdfTEX is not su cient. While this enables tagging to be
implemented, much macro programming is required to (i) load extra Metadata
and font-encoding mappings; (ii) provide alternative-text to be read by
screenreader software; (iii) organise how the new tagging primitives are used and are
correctly nested; (iv) identify structural \artifacts" (such as page-numbers,
footnote rules, background images, etc.); (v) keep track of aspects of the document
structure; and (vi) many other details requiring special attention. Some of these
tasks enhance the Accessibility without the need for tagging; but the tagging is
e
m
a
n
w
o
d
n
i
w
s
a
e
li
t
t
t
n
e
m
u
c
o
D
r
e
d
r
o
g
n
i
d
a
e
r
h
t
i
w
t
n
e
t
s
i
s
n
o
c
,
t
n
e
t
n
o
c
g
n
i
w
o
h
s
e
e
r
t
s
g
a
T
t
n
e
t
n
o
c
d
n
a
e
r
u
t
c
u
r
t
s
r
o
f
d
e
g
g
a
t
s
c
i
t
a
m
e
h
t
a
m
”
s
t
c
a
if
t
r
A
“
e
k
li
t
n
e
t
n
o
c
s
g
n
il
b
i
s
t
n
e
t
n
o
c
s
t
h
g
li
h
g
i
h
e
e
r
t
b
u
s
e
r
u
t
c
u
r
t
s
f
o
n
o
i
t
c
e
l
e
s
s
m
e
t
i
d
n
a
t
s
li
d
e
g
g
a
T
certainly the most important requirement. Figure 1 shows part of a document,
indicating some of the above-listed features.
      </p>
      <p>Now the WCAG recommendations do not specify the detail to which
mathematical formulas should be tagged, but the natural format would be Presentation
MathML. Furthermore, since the forthcoming ISO 32000-2 speci cations are to
include MathML tagging, this is the natural choice for handling mathematical
content. In subsequent sections, we rst give a brief overview of how tagging is
implemented in PDF, then show what this means for a simple piece of
mathematical content, in which each single character has a special meaning and ts within
a very tight structural description. Also shown, in Figure 5 is the enriched LATEX
source to achieve this, requiring many lines of input to capture the meaning and
structure of just a few characters in the original LATEX description.</p>
    </sec>
    <sec id="sec-2">
      <title>Catalog 1</title>
      <sec id="sec-2-1">
        <title>Pages</title>
      </sec>
      <sec id="sec-2-2">
        <title>StructTreeRoot</title>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Pages 100</title>
      <p>
        Kids [...]
Fig. 2. Interleaving of structure and content tagging within a 2-page PDF
document, structured as a heading and two paragraphs. (based on an example in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]).
Picture reproduced with permission from [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        Overview of \Tagged PDF"
A brief history of Adobe's PDF format and speci cation was given by the author
at the CICM 2009 meeting, and published as [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Rather than repeat this here,
the basic structure of \Tagged PDF" can be understood using the diagram,
reproduced from [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and shown as Figure 2. This has been described as a
\doubletree" structure. The `Pages' tree is indicated by the top rows of blue boxes,
headed as `Page ...', each having another box headed as `Contents ...' which denotes
the `page content' streams; that is, the low-level commands to select fonts and
place text on the page. Relevant documentation and format speci cations are
listed in the bibliography, as [
        <xref ref-type="bibr" rid="ref1 ref2 ref3 ref4 ref8">1,2,3,4,8</xref>
        ].
      </p>
      <p>The 2nd tree is the `Structure Tree' which is much richer, represented by the
lower rows of blue boxes. Leaf-nodes for this tree consist of the tags show as
yellow rectangles within the blue `Contents ...' boxes, each with labels including
`MCID ...'. All the other yellow rectangles represent data structures required to do
the `book-keeping' of how these two tree structures intersect. In an actual Tagged
PDF document, these allow for navigation and selection of the content using the
`structure elements', as shown in Figure 1, and for extraction of individual pages
so as to preserve that part of the structure that is present on the speci c page.</p>
      <p>A useful way to see these two tree structures together is provided by the
`Tags' view, in Adobe's Acrobat Pro software. See Figure 1 for an example of
how this can appear.
3</p>
      <p>Example of Tagged content within a `page stream'
As with XML and HTML, tags can have attributes to help reader software tools
construct a more appropriate representation of the content. Two such attributes
are the `/Alt' text and `/ActualText' character strings. The former is used to
provide a short textual description of the content of an image, just as with HTML for
web-pages. But this attribute is available for any content, so is particularly useful
with mathematics to provide an audible description of the names of symbols or
their uses. On the other hand, the `/ActualText' is used with text-extraction, to
provide a mapping from characters shown onscreen to a friendlier representation;
e.g., the old German character may be mapped to `ss', or to the Unicode point
U+00DF when the font used in the document is coded in a non-standard way. For
mathematical symbols, this can be used to map variable names x, y, a, b, etc.
into mathematical alpha-numerics, such as U+1D465 etc., when the document
font uses ASCII positions, as in the following example.</p>
      <p>A portion of the page stream corresponding to part of the content which
renders as 34 R3 is shown in Figure 3. The lines which contain `/MCID' and
those following up to `EMC' are what determine the tagging of content. All
other lines are as would appear without tagging, apart from line-ends being
removed to allow this code sample to t on the printed page. Notice the use of
hexadecimal strings for `/ActualText' and plain English words for `/Alt' text, which
are the `Accessible Text' words that will be vocalised by screen-reader software.
The `/mi', `/mn' clearly corresponds to MathML tagging of the content. For this
example the MathML description used is shown in Figure 4.
Fig. 4. MathML representation of the same piece of mathematics: 43 R3 , used
to create the PDF portion shown in Figure 3. White-space has been massaged
for display purposes.
4%
3%
}%
R%
3%
}%</p>
      <p>\EMC
\SMC{attr{/Type/Layout/ActualText&lt;FEFF0028&gt;} }{-1}{Artifact}%
\left(% start of fence
\EMA
\TPDFfbrack
\tfrac{
\pdfinterwordspaceoff
\SMC{attr{/ActualText&lt;FEFF0034&gt;\TPDFaloud{0034}} }{5}{mn}%
\EMC
}{%
\SMC{attr{/ActualText&lt;FEFF0033&gt;\TPDFspeak{\TPDFthirds}} }{6}{mn}%
\SMC{attr{/ActualText&lt;FEFF2062&gt;\TPDFaloud{2062}} }{7}{mo}%
\pdffakespace
\EMC
\SMC{attr{/ActualText&lt;FEFF03C0&gt;\TPDFaloud{03C0}} }{8}{mi}%
\pi%
\EMC
\SMC{attr{/ActualText&lt;FEFFD835DC45&gt;\TPDFaloud{1D445}} }{10}{mi}%
^{%
\EMC
\TPDFcubed
\TPDFpopfence
\SMC{attr{/ActualText&lt;FEFF0033&gt;\TPDFaloud{0033}} }{11}{mn}%
\EMC
\SMC{attr{/Type/Layout/ActualText&lt;FEFF0029&gt;} }{-1}{Artifact}%
\right)% end of fence</p>
      <p>\EMA
\SSE{attr{/Type/StructElem/S/math
/A&lt;&lt;/O/XML-1.00/xmlns(http://www.w3.org/1998/Math/MathML)</p>
      <p>/style(font-size: xx-small)&gt;&gt;}\TPDFaloudtag{math}{2}}{1}{0}{2}%
\SSE{attr{/Type/StructElem/S/mfenced
/A&lt;&lt;/O/XML-1.00/separators()&gt;&gt;}\TPDFaloudtag{mfenced}{3}}{2}{2}{3}%
\SSE{attr{/Type/StructElem/S/mfrac}\TPDFaloudtag{mfrac}{4}}{1}{3}{4}%
\SSE{attr{/Type/StructElem/S/mn}\TPDFaloudtag{mn}{5}}{2}{4}{5}%
\SSE{attr{/Type/StructElem/S/mn}\TPDFaloudtag{mn}{6}}{3}{4}{6}%
\SSE{attr{/Type/StructElem/S/mo}\TPDFaloudtag{mo}{7}}{2}{3}{7}%
\SSE{attr{/Type/StructElem/S/mi}\TPDFaloudtag{mi}{8}}{3}{3}{8}%
\SSE{attr{/Type/StructElem/S/msup}\TPDFaloudtag{msup}{9}}{4}{3}{9}%
\SSE{attr{/Type/StructElem/S/mi}\TPDFaloudtag{mi}{10}}{2}{9}{10}%
\SSE{attr{/Type/StructElem/S/mn}\TPDFaloudtag{mn}{11}}{3}{9}{11}%
\TPDFcleanread {11}%
Fig. 5. Output from texmmljoin merging TEX source with the MathML content
from Figure 4. The original LATEX source can be read down the left-hand edge, as
\left (\frac 43 \pi R^3 \right ). The lower portion builds the structure
tree, using tag indices which are interpreted relative to an o set.
39 0 obj &lt;&lt; /K [ 34 0 R 35 0 R ] /P 37 0 R</p>
      <p>/Type/StructElem/S/msup &gt;&gt; endobj
38 0 obj &lt;&lt; /K [ 29 0 R 30 0 R ] /P 37 0 R</p>
      <p>/Type/StructElem/S/mfrac &gt;&gt; endobj
37 0 obj &lt;&lt; /K [ 38 0 R 31 0 R 32 0 R 39 0 R ] /P 36 0 R</p>
      <p>
        /Type/StructElem/S/mfenced /A&lt;&lt;/O/XML-1.00/separators()&gt;&gt; &gt;&gt; endobj
36 0 obj &lt;&lt; /K [ 37 0 R ] /P 27 0 R
/Type/StructElem/S/math /A&lt;&lt;/O/XML-1.00
/xmlns(http://www.w3.org/1998/Math/MathML)
/style(font-size: xx-small)&gt;&gt; &gt;&gt; endobj
35 0 obj &lt;&lt; /K [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] /Pg 5 0 R /P 39 0 R
      </p>
      <p>
        /Type/StructElem/S/mn &gt;&gt; endobj
34 0 obj &lt;&lt; /K [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] /Pg 5 0 R /P 39 0 R
      </p>
      <p>
        /Type/StructElem/S/mi &gt;&gt; endobj
32 0 obj &lt;&lt; /K [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] /Pg 5 0 R /P 37 0 R
      </p>
      <p>
        /Type/StructElem/S/mi &gt;&gt; endobj
31 0 obj &lt;&lt; /K [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] /Pg 5 0 R /P 37 0 R
      </p>
      <p>
        /Type/StructElem/S/mo &gt;&gt; endobj
30 0 obj &lt;&lt; /K [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] /Pg 5 0 R /P 38 0 R
      </p>
      <p>
        /Type/StructElem/S/mn &gt;&gt; endobj
29 0 obj &lt;&lt; /K [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] /Pg 5 0 R /P 38 0 R
      </p>
      <p>/Type/StructElem/S/mn &gt;&gt; endobj
27 0 obj &lt;&lt; /K [ 36 0 R ] /P 26 0 R
/Type/StructElem/S/Formula /ID(Math0.1)/T(InlineMath 0.1)
/A&lt;&lt;/O/XML-1.01 /TeX(sphere_volume-1.tex) /MathML(sphere_volume-1.txt)&gt;&gt;
&gt;&gt; endobj</p>
      <p>Encoding the tagging with LATEX
Starting from the LATEX source $\left (\frac 43 \pi R^3 \right )$, and
a MathML description obtained using TEX-to-MathML conversion software, as
shown in Figure 4, these two descriptions which capture the same mathematical
content need to be merged. This is done using a Perl program, written by the
author, called texmmljoin. For the speci c code sample its output includes the
TEX-like coding shown in Figure 5.</p>
      <p>The original LATEX source for the mathematics can be seen down the
lefthand edge. Also, `/ActualText' attributes are clearly seen, but what about the
`/Alt' attribute? This is built from the \TPDFaloud, \TPDFaloud and other
special command sequences such as \TPDFfbrack, \TPDFthirds, \TPDFcubed and
\TPDFpopfence. Using TEX macro coding, \TPDFaloud{1D445} expands into
something speci c to the unicode point U+1D445 which is an uppercase (or
`capital') letter `R'. This is what is spoken in English, but that could be replaced
with whatever is appropriate for another spoken language, simply using macro
de nitions | the output from texmmljoin does not need to be changed. Macros
\TPDFcubed and \TPDFpopfence add words to become part of the `/Alt' attribute
for the subsequent piece of content, or the previous when there is no more. These
also may be customised for languages other than English, or to change what is
to be spoken according to the mathematical context of their use. For example,
{...} might be notation for a `set' in one piece of mathematics, but in another it
could be denoting a `Lie bracket'. Through macro de nitions, the spoken version
can be adapted to provide the appropriate words.</p>
      <p>The lower part of the output from texmmljoin, as shown in Figure 5, contains
information on how to build the structure tree. These have the form of a TEX
macro (\SSE) taking four arguments, the rst indicating the MathML tag type
along with any attributes, with nal three being bracketed numbers. The last
of these is a unique index for the structure tag, with the preceding one being
the index of its parent structure tag. Before these, the rst bracketed number
is an index which a ects the ordering of those structure tags having the same
parent; lower numbers occur earlier within the structure tree. The PDF objects
that record this information within the PDF le are shown in Figure 6.</p>
      <p>For a speci c math-environment the parent and structure tag indices as
shown here are not used directly, but are rst incremented by an o set
determined as the environment is encountered. This o set is essentially the
highest tag index encountered so far, ensuring that the index used is unique for
all structure tags within the same document, allowing the structure tree to
be faithfully constructed internally by pdfTEX. The numerical argument to
\TPDFcleanread conveys the total number of new structure tags de ned within
the math-environment, so that the o set can be incremented correctly for
subsequent tagged content.
5</p>
      <p>
        Automatic generation of MathML
Previous work done by the author [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] detected all the math-environments in a
LATEX document, writing the contents into an external le before creating button
annotations to show/hide textual elds displaying these original source code
snippets. This work has now been adapted to prepare source for TEX to MathML
translation software; e.g., based upon TEX4HT. Thus now an existing LATEX
document can be processed, detecting the math-environments and initiating a
conversion to MathML. Then texmmljoin is run to merge the resulting pair of
les having LATEX and MathML descriptions of the same piece of mathematics,
creating new LATEX source enriched with full structure and content tagging.
      </p>
      <p>Since TEX4HT needs a complete run of LATEX on the source snippet, followed
by further post-processing to generate an XML le containing the MathML
description of the mathematics, this process can typically take many seconds. To
avoid repeating this work on each run of LATEX over the document source, an
indexing mechanism has been developed, which associates the speci c source
coding with the name pre x of the les created in the translation and merging
processes. Having created enriched source for a piece of mathematics, there is no
need to redo it, unless the content is changed by edited. Due to the use of tag
index o sets, as described in Section 4, editing which simply reorganises the
order of appearance of pieces of mathematics does not need to initiate re-tagging.
Using a di erent o set, the internal index remains unique for all structure tags.
&lt;file&gt;2013-Assign2-soln-inline-1&lt;/file&gt;&lt;code&gt;\( k \in \RR \) &lt;/code&gt;
&lt;file&gt;2013-Assign2-soln-inline-2&lt;/file&gt;&lt;code&gt;\( \begin {cases}\begin
{aligned} x - y &amp; = 2 \\ 3\,x - 3\,y &amp; = k \end {aligned}\end {cases}
\) &lt;/code&gt;
&lt;file&gt;2013-Assign2-soln-display-1&lt;/file&gt;&lt;code&gt;\[ \left ( \begin {array}
{rr | c} 1 &amp; -1 &amp; 2 \\ 3 &amp; -3 &amp; k \end {array} \right ) \;\; \sim \;\;
\left ( \begin {array}{rr | c} 1 &amp; -1 &amp; 2 \\ 0 &amp; 0 &amp; k-6 \end {array}
\right )\,. \] &lt;/code&gt;
&lt;file&gt;2013-Assign2-soln-inline-3&lt;/file&gt;&lt;code&gt;\( k \not = 6 \) &lt;/code&gt;
&lt;file&gt;2013-Assign2-soln-inline-4&lt;/file&gt;&lt;code&gt;\( k \) &lt;/code&gt;
&lt;file&gt;2013-Assign2-soln-inline-5&lt;/file&gt;&lt;code&gt;\( k=6 \) &lt;/code&gt;
&lt;file&gt;2013-Assign2-soln-inline-6&lt;/file&gt;&lt;code&gt;\( y \) &lt;/code&gt;
&lt;file&gt;2013-Assign2-soln-inline-7&lt;/file&gt;&lt;code&gt;\( (x\,,y)= (2+\lambda
\,, \lambda ) \) &lt;/code&gt;
&lt;file&gt;2013-Assign2-soln-inline-8&lt;/file&gt;&lt;code&gt;\( \lambda \in \RR \)
&lt;/code&gt;
&lt;file&gt;2013-Assign2-soln-inline-9&lt;/file&gt;&lt;code&gt;\( \RR ^2 \) &lt;/code&gt;</p>
      <p>One further advantage of this is that if the same piece of mathematics is
used repeatedly within a document, the generation and merging with MathML
need only be performed once. The previous output from texmmljoin may
simply be reused with di erent o sets ensuring that the resulting PDF document
is correctly formed. Thus much time-consuming work needs to be done only
once. Furthermore the way that the indexing is constructed, making use of the
\detokenize primitive of e-TEX and scanning to reduce runs of multiple spaces
to a single token, means that nearly identical math environments can be treated
as being actually identical for tagging purposes. The index of the mathematical
content is written to an external le, which is then read at the beginning of the
next LATEX run. This allows the association to be made early between a piece of
mathematics and the les required for its enrichment. Figure 7 shows a portion
of the index le, used with the document seen in Figure 1.</p>
      <p>Of course the tagged math-environments have to be tted into the structure
tagging of the document as a whole, generally as siblings of the surrounding
paragraph, which may or may not nish with the mathematics. Details of the
TEX coding to achieve this is beyond the scope of this report. This should be
discussed in a later report, delivered perhaps at a di erent forum.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <source>Adobe Systems Inc.; PDF Reference 1</source>
          .7,
          <string-name>
            <surname>November</surname>
          </string-name>
          <year>2006</year>
          . http://www.adobe.com/devnet/pdf/pdf_reference.html. Also available as [3].
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. ISO 19005-1:2005;
          <article-title>Document Management | Electronic document le format for long term preservation | Part 1: Use of PDF 1.4 (PDF/A-1</article-title>
          ); http://www.iso.org/iso/catalogue_detail?csnumber=
          <fpage>38920</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. ISO/DIS 32000;
          <article-title>Document management | Portable document format (PDF 1.7)</article-title>
          .
          <source>July</source>
          <year>2008</year>
          . http://www.iso.org/iso/catalogue_detail?csnumber=
          <fpage>51502</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Technical</given-names>
            <surname>Implementation</surname>
          </string-name>
          <article-title>Guide; AIIM Global Community of Information Professionals</article-title>
          . http://www.aiim.org/Research-and-Publications/standards/ committees/PDFUA/Technical-Implementation-Guide. Also available as ISO 14289-1:2012; http://www.iso.org/iso/home/store/ catalogue_tc/catalogue_detail.htm?csnumber=
          <fpage>54564</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Moore</surname>
          </string-name>
          , Ross R.;
          <article-title>Ongoing e orts to generate \tagged PDF" using pdfTEX, in DML 2009, Towards a digital Mathematics Library</article-title>
          , Proceedings, Petr Sojka (editor), Muni Press, Masaryk University,
          <year>2009</year>
          . ISBN 978-80-20-4781-5. Reprinted as:
          <source>TUGboat</source>
          , Vol
          <volume>30</volume>
          , No.
          <volume>2</volume>
          (
          <issue>2009</issue>
          ), pp.
          <volume>170</volume>
          {
          <fpage>175</fpage>
          . http://www.tug.org/TUGboat/tb30-2/tb95moore.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Moore</surname>
          </string-name>
          , Ross R.; serendiPDF, with searchable math- elds
          <source>in PDF documents; TUGboat</source>
          , Vol
          <volume>23</volume>
          , No.
          <volume>1</volume>
          (
          <issue>2002</issue>
          ), pp.
          <volume>65</volume>
          {
          <fpage>69</fpage>
          . http://www.tug.org/TUGboat/tb23-1/moore.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7. Policies Relating to Web Accessibility;
          <article-title>W3C Web Accessibility Initiative</article-title>
          . http://www.w3.org/WAI/Policy/.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Achieving</surname>
            <given-names>WCAG</given-names>
          </string-name>
          2.
          <article-title>0 with PDF/UA; AIIM Global Community of Information Professionals</article-title>
          . http://www.aiim.org/Research-and-Publications/standards/ committees/PDFUA/WCAG20-Mapping.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>Web</given-names>
            <surname>Content Accessibility</surname>
          </string-name>
          <article-title>Guidelines (WCAG) 2.0</article-title>
          .
          <string-name>
            <given-names>W3C</given-names>
            <surname>Web Content Accessibility</surname>
          </string-name>
          Guidelines Working Group. http://www.w3.org/TR/WCAG20/. Also available as ISO/IEC 40500:
          <year>2012</year>
          ; http://www.iso.org/iso/iso_catalogue/ catalogue_tc/catalogue_detail.htm?csnumber=
          <fpage>58625</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <article-title>Statement about WCAG 2.0 compliance, in accordance with the Disability Discrimination Act 1992</article-title>
          . http://australia.gov.au/about/accessibility.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <article-title>Guidance on Implementing the Standard on Web Accessibility; Treasury Board of Canada Secretariat</article-title>
          . http://www.tbs-sct.gc.ca/ws-nw/wa-aw/
          <article-title>wa-aw-guid-eng</article-title>
          .asp
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <article-title>Wikipedia entry for `PDF/Universal Accessibility (PDF/UA)'</article-title>
          . Quotations taken from: http://en.wikipedia.org/wiki/PDF/UA#Description and http:// en.wikipedia.org/wiki/PDF/UA#Audience_.26_Benefits.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>