Showing posts with label tagged PDF. Show all posts

Sample Section 508 Audit and Primer

Here's a little primer on tagging PDFs for Section 508 compliance, just four pictures worth a thousand words each- this is from an AIM document audit:

Screenreaders like JAWS read the content of standardized "tags" in PDF documents out loud. The name of the tag informs the screenreader as to what the content is- say a top-level heading <H1>, paragraph text <P>, a table <Table>, list <L>, etc. Correctly formed, ordered tags can give a blind reader almost as much information as the sighted reader has- the screenreader can scan the page and "see" the headings, lists, navigate through tables, etc.

So accessibility is all about the quality of the tags. Let's look at the doc. Well, first off, we look at the document properties. Sorry, they are empty, screenreader can't do much with that. But it doesn't matter, because, notice in the lower left, Where it says "Tagged PDF: No"? That tells the screenreader to take a hike, won't read a thing. Kind of a red flag, accessibility-wise, I'd say:

Easy enough to edit the meta-data and denote it as a tagged PDF, as there are some tags. Let's read!!!

First thing the screenreader would read out loud is the contents of the first tag. What do we have? look in the left column, the first tag in the document is the page number 63. Oops.... well that's not right obviously- page numbers should not be read out loud, to begin with, but we know right off we have reading order issues:

The first section of the tag list is all page numbers. In the next section we finally get to the title page.

Below: First tag is the logo, <Figure> tag- oops....it should have "alt text" like "LA Health Plan logo" to inform our sight-impaired user. Title gag is next, I've opened it up to show what the screenreader sees, "Medi-cal Program". But the title should be tagged <H1>- this one has a <no_paragraph_style> tag that the screenreader just sees as regular paragraph text. (Note: automatic PDF checkers would "pass" this; you can tag a doc as one big <P> tag and fool them...).

Big deal, you say, but wait, it gets better:

(What do you suppose those items to the left and outside the page are about? It is tagged content. We'll skip over it for now- certainly not content that needs to be read aloud. Sloppy tagging, at the least, hopefully just stray blank tags.The screenreader will call out "blank" and "Figure- no alternate text exists" as it passes through, doh...)

The real problem with this document, and the final slide in our lesson, comes right away after the cover page. There are NO TAGS on the body of the document. The screenreader would stop after the title page.

The next tags in the tag list are for the back cover, nary a tag in between.

This document is not accessible or compliant with Section 508, I guarantee it. This doc needs a complete remediation job.

Contact http://508compliantdocumentconversion.com/ ASAP!!!!

Why Use Accessibility In Mind For Your Section 508 Remediation: The AIM Difference

#1: Accessibility In Mind is a dedicated Section 508 and PDF/UA compliance service.

We are not a design/print house that does remediation on the side- remediating PDF documents, making them accessible and compliant, is our ONLY service. Look at the home page of our competitors if you want to know what their main business is, then come back to AIM for your Section 508 work!

#2: We are not a middle-man, taking a commission and passing the work on to contractors.

When you work with AIM you are dealing DIRECTLY with Section 508 expert remediators, and paying less-- often 30-50% less-- than through other vendors. Deal direct, SAVE TIME AND MONEY!

http://accessibilityinmind.com/

EDCS Levels of Service

Total accessibility is the goal of every EDCS remediation. Contrary to common belief, passing an automatic check alone does not ensure accessibility. Un-tagged content, inactive URLs, and incorrect reading order are examples of errors that are overlooked by Adobe Acrobat's autochecks. A document that is blank to a screen reader can be made to pass but is obviously not accessible or compliant.

Structured documents are accessible documents. Comprehensive remediation adds value to documents, for both sighted and sight-impaired users.

Bid Request Form

Complete remediation includes these services:

Determine if the PDF file has been properly tagged. Verify tagged elements are properly sequenced and applied. Ascertain that tag list follows document reading order exactly for optimum reading order and reflow for screen readers
Style tags applied appropriately to all text
Correct pagination added to thumbnails
URLs checked/activated
Bookmarks added (documents over 9 pages)
Table of Contents made active
All internal and external active links made BLUE (optional)
Correct properties, initial view settings, correct tab order, "fast view" set, custom properties removed, language set
Tables scoped (header and data cells appropriately tagged); all tabular data edited/tagged as tables with scoped columns and rows; tables created where absent
Add Alternative Text. Add informative and concise alternative text and descriptions for all non-text elements
Artifact all table PATH (border) tags (optional)
Removal/artifact all background graphics
Complete Adobe Acrobat Pro 11 accessibility report showing no errors or warnings
Complete HHS checklist (optional)
Spot check with screen reader (JAWS or equivalent)
Complete Quality Check

Exclusions or additions to the listed services at client's request. Deliverables include remediated PDF and time-stamped validation reports from Acrobat Pro 11: "Accessibility Full Check", and agency checklist if requested. Please provide guidelines/requirements at time of bid request.

Fillable Form PDFs- add these services:

Creation/edit of form fields
Tool tips added to form fields.
Formatting applied to form field (date, currency, etc.)

Note: Remediation limited to form documents created in Acrobat.

Minimum specifications:

No character encoding errors present
Document created with editable fonts
Alternate text descriptions of graphics/figures included or provided by client
Document properties (Title, Author, Subject, Keywords) provided by client

Terms and Conditions

All bid requests will include expected time frame for the job, date of document delivery from client to EDCS and date of remediated document delivery from EDCS to client. Bids provided by EDCS are valid for 30 days. EDCS will evaluate documents requiring remediation and deliver a quotation of price per page for desired level of remediation and any additional charges that may be incurred to complete the remediation. Our evaluations are thorough, but there are sometimes issues that do not show in our evaluation that may make some documents impractical or impossible to remediate into accessible documents. EDCS reserves the right to inform client of any documents that fall into this category prior to document remediation; documents will not be remediated and remediation charges for these documents will be subtracted from final invoice. At client’s request, and upon agreement from EDCS, documents not remediated due to aforementioned issues, or any pre or post-remediation document processing or editing, will be charged at $100 per hour. Services not specifically required for compliance may be excluded from remediation, at client's request. Documents 50 pages or less are subject to a $50 short-document administrative fee.

Bid Request Form

Terms effective 12/11/2013

Learning About Section 508 Document Compliance: "Tagging" a PDF

Learn about document compliance and how it is achieved:

Electronic documents come in many formats, but most are converted to PDF for publication on the Web. Invented by Adobe Systems over 20 years ago, Portable Document Format (PDF) is now an open standard for electronic document exchange maintained by the International Organization for Standardization (ISO). When you convert documents, forms, graphics, and web pages to PDF, they look just like they would if printed. But unlike printed documents, PDF files can contain clickable links and buttons, form fields, video, and audio — as well as logic to help automate routine business processes.

This underlying structure is not inherent in the PDF, but must be planned for during the source document creation, or added to the document during PDF "remediation". The process ensures that the published document is accessible for users with disabilities as well as more valuable to all users, with logical document structure, internal navigation, and active bookmarks, URLs, and functional forms. This document structure is contained in the document's "tags" that live behind the scenes and allows assistive technology like screen readers to interpret the document as intended by the authors. Similar to the HTML code that defines how Web pages display, PDF document tags define how a document is read aloud using programs such as JAWS, and the quality and organization of the tags determine just how accessible the document will be, and how close to an equivalent experience the audio version of the document is compared with reading. They are labels that help the screen readers inform a sight-impaired user how the document is structured, and allow navigation through the document with the same functions available to a sighted user.

Proper tagging is the first step. Depending on how a document is converted, and what the source is, documents may be close to accessible with minor editing. Proper conversions from late versions of Word or InDesign give the best results, but this, too, is dependent on how the document was "styled" ; the most common example is font selection- the document creator may not have followed best practices using CSS "styles", and the tags created during the conversion will need extensive editing. The document remediator's job is to ensure the tags will tell the story as the author intends, that there is a logical underlying structure. As a programmer writes the underlying code for a Web page, the remediator builds (or renovates) the foundation that holds the content and correctly "displays" the final document for assistive technologies like JAWS.

Section 508 was enacted to eliminate barriers in information technology; advances in this technology have made it possible to significantly reduce these barriers, or even eliminate them completely. Electronic Document Compliance Services (EDCS) is dedicated to helping fulfill this promise. We do one thing, and we do it well: Documents certified compliant by EDCS are guaranteed to be accessible and compliant with Section 508.

Overcoming Accessibility Challenges for Section 508 Compliance

This is based on an article from the National Center on Disability and Access to Education, describing how properly structured / tagged PDF documents can be made accessible and in compliance with Section 508, and the disability types that can be aided by the process:

Accessibility challenge	Disability type(s)	Solution(s)
Only true headings and lists will convey semantic meaning to a screen reader user.	Blind	Tag all headings so they are true headings (H1, H2, etc. Tag all lists as ordered or unordered lists.
Images must include an alternative description (alt text) to be meaningful to a screen reader user.	Blind	Add Alternate Text to each document. Combine complex figures and provide Alternate Text.
Complex charts or tables may not contain proper headings, captions or summaries.	Blind	Tag table rows (<TR>), table headers (<TH>), and table data cells (<TD>). Set the scope of each table header cell (column or row)
Poor color contrast, especially in images and charts.	Color blind, Low vision	Ensure sufficient color contrast in text, charts and images. One way to verify this is to print out the document on a black and white printer.
Documents with forms that can be filled in on the screen (checkboxes, text fields, etc.) may not be accessible to screen reader users and may not export correctly to other formats.	Blind, all users	Make sure form elements have appropriate tags. Verify that the form can be completed using common screen readers.
A page may be read out of order by a screen reader. That is, the reading order and the visual order may be different.	Blind	Check and edit the reading order using Acrobat reading order tools Verify reading order with screen reader
Scanned PDF files that are not converted to plain text will not be accessible to screen reader users.	Blind	Convert a scanned PDF file into text using an Optical Character Recognition program.
A PDF reader program must be used to view PDF files.	All users	The Adobe Reader can be downloaded free from the Adobe site. There are a number of free reader programs that are available for several platforms. The accessibility features of these readers vary.
Embedded multimedia may be inaccessible, especially if it is not captioned.	Deaf, Blind	Make sure embedded multimedia is captioned. This is possible in a PDF file. If necessary, provide audio descriptions for the blind.
Scanned PDF files converted to real text can have numerous misspellings that may only be apparent to screen reader users.	Blind	Use a spell check to make sure as many words are spelled correctly as possible.
Headers, footers, logos and other content that meant to be ignored may be read by a screen reader on every page.	Blind	Convert extraneous information to an artifact If appropriate, make the first instance of repetitive information visible and convert subsequent versions into artifacts.