xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.U. Anderegg" <hansuli.ander...@bluewin.ch>
Subject AW: tagged PDF
Date Tue, 08 Apr 2003 20:35:31 GMT
What are your application requirements? When I look at the Adobe description
of accessibility below, I see some features easy to program in FOP and some
ones rather challenging.

Hansuli Anderegg

What is Accessibility?

Here are some things to consider to optimize your documents for
accessibility and help screen reader applications use them:

Logical reading order.

Documents are more accessible if they have been authored with a logical
structure in mind. Using application-based tools to define and create
document structure such as titles, chapters, headings, and multi-column text
can make it easier for assistive technologies such as screen readers to
understand the logical reading order of the content without any ambiguity.
For example, if a document has been correctly authored using two columns to
create a two-column format, the screen reader knows it should read all the
way down the first column and then proceed to the second column. On the
other hand, if the writer used tabs to imitate the look of two-column text,
the screen reader would not recognize the layout as two-column. Instead, it
would simply read horizontally, going from the first line in the first
column and then tabbing over to the first line in the second column.

Alternate text descriptions for images.

The document should contain written descriptions of images in the document.
For example, you can use the Tags palette discussed later in this guide to
add a description of an image. Then, when a screen reader encounters that
image in the document, it will read the alternate text description so the
user can understand what the image is about.

To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

View raw message