User login

Accessibility of PDF electronic books, case of DGD7

Accessibility and Drupal expert Everett Zufelt was kind enough to look at the PDF e-book version of the Definitive Guide to Drupal 7.

1. The PDF is tagged, this is good. In order for a screen-reader user to interact with a PDF the file needs to be parsed into an accessibility API / virtual buffer. Tagging makes it easier and faster for the file to be parsed.

2. Lack of proper structure. Tables and headings "look" like tables and headings, but they are not semantically represented as such. This makes it difficult to navigate between and within pages.

3. Alternative text for images. The images don't appear to have alternative text, although it does seem (I might be wrong) that some have captions. Captions do help where alternative text isn't available, but they sometimes are not sufficient to communicate the meaning. Alternative text should be written from the perspective of "What text needs to be here if the image isn't?"


Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Syntax highlight code surrounded by the {syntaxhighlighter SPEC}...{/syntaxhighlighter} tags, where SPEC is a Syntaxhighlighter options string or "class="OPTIONS" title="the title".
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.