Macromedia Acrobat - XI Professional Accessibility Guide
For more information
Solution details: www.adobe.com/accessibility/products/acrobat/
Program details: www.adobe.com/accessibility
Contact information: access@adobe.com
Adobe Sy stems Inco rporated
345 Par k Avenue
San Jo se, CA 95110-2704
USA
www.a dobe.com
Adobe, the Adobe lo go, Acrobat , Acrobat Co nnect, Ac tionScri pt, Adobe C aptivate, A uthorwar e, Flash, and JRun are either reg istered tr ademarks or tradema rks of Adob e
Syste ms Incorpo rated in the United Sta tes and/or ot her countri es. Micro so and Win dows are ei ther regis tered trad emarks or trademark s of Micro so Corpor ation in the
Unite d States an d/or other cou ntries. J ava is a trad emark or re gistered t rademark o f Sun Micro systems , Inc. in t he United St ates and ot her countr ies. All ot her tradem arks
are the propert y of their r espectiv e owners.
© 2012 Ad obe System s Incorpor ated. All ri ghts rese rved. Pri nted in the U SA.
10/12
Adobe® Acrobat® XI Pro Accessibility Guide:
Best Practices for PDF Accessibility
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Contents
PDF Accessibility Overview ................................................................................................................................................. 1
Overview of Portable Document Format (PDF)
Determine the Accessibility Path for each PDF Document
Start with an Accessible Document
Characteristics of Accessible PDF les
Adobe Acrobat and Adobe Reader Accessibility Features
Accessibility Features of Adobe XI Reader, Adobe XI Standard, and Adobe XI Pro
e Acrobat XI Pro Accessibility Guide Series
Using the Acrobat XI Pro Accessibility Checker
e Make Accessible Action Wizard
Accessibility Checker (Full Check)
Additional Functional Validation Techniques
WCAG 2.0 Mapng to PDF/UA
Acrobat XI Pro PDF Accessibility Repair Workow
Step 1: Examine the PDF File
Step 2: Add Document Properties and Interactive Features
Document Title, Subject, Author, and Keywords ................................................................................................32
Set Security at Permits Accessibility .................................................................................................................33
............................................................................................................................2
...........................................................................................................................7
..............................................................................................................................7
......................................................................................................................................24
......................................................................................................................................31
.......................................................................................................1
...................................................................................1
.......................................................................................................................2
.................................................................................... 4
........................................ 5
..........................................................................................................6
..............................................................................................................7
........................................................................................................23
.....................................................................................................30
..............................................................................31
Create Accessible Links .............................................................................................................................................35
Add Bookmarks ..........................................................................................................................................................36
Set Initial View/Open Options .................................................................................................................................37
Step 3: Per form OCR on Scanned Document
How to Determine if a PDF File is a Scanned Document ...................................................................................37
Perform OCR on a Scanned Document .................................................................................................................40
Step 4: Add Form Fields and Set the Tab Order
Step 5: Set the Document Language
Step 6: Add Tags to the Document .........................................................................................................................42
Determine if the Document has been Tagged .....................................................................................................42
Add Tags to an Untagged Document .....................................................................................................................49
Step 7: Examine and Repair the Tag Structure
Touch Up Reading Order Tool (TURO) ...................................................................................................................53
Tips for using the Touch Up Reading Order Tool ................................................................................................56
Checking Read Order with the Touch Up Read Order Tool ..............................................................................57
Edit Tags with the Touch Up Reading Order Tool ................................................................................................59
Using the Touch Up Reading Order Tool Table Editor .......................................................................................62
.........................................................................................................37
.....................................................................................................41
.........................................................................................................................41
.......................................................................................................52
Editng Table Tags ........................................................................................................................................................63
Remove or Replace Document Structure Tags using the Touch Up Reading Order Tool ..........................66
Tags Panel .....................................................................................................................................................................69
II
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Correct Table Tags with the Tags Panel .................................................................................................................74
Step 8: Add Alternative Text
Add Alternate Text and Supplementary Information to Tags ..........................................................................76
Step 9: Use the Accessibility Checker to Evaluate the PDF File..........................................................................78
Acrobat XI Pro Accessible Forms and Interactive Documents
Types of interactive PDF Form Fields
Automatic Field Detection using the Acrobat Form Wizard
Creating a Form without the Forms Wizard
Forms Editing Mode......................................................................................................................................................84
Selecting a New Form Field to Create
Form Field Properties...................................................................................................................................................86
Seing Tooltips for Form Fields
Editing or Modifying an Existing Form Field
Deleting a Form Field
Field Actions
Validation and Error Messages
Set the Tab Order
Provide Instructions and Onscreen Labels
...................................................................................................................................................................89
...........................................................................................................................................................89
.......................................................................................................................................76
..................................................................................80
.......................................................................................................................81
...............................................................................81
............................................................................................................83
......................................................................................................................84
.................................................................................................................................86
..........................................................................................................88
...................................................................................................................................................88
..................................................................................................................................89
.............................................................................................................90
Other Accessibility Considerations
...........................................................................................................................90
III
PDF Accessibility Overview
PDF Accessibility Overview
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
PDF le format accessibility features combined with Adobe® Acrobat®
and Adobe Reader® allow universal access to documents
A document or application is considered accessible if meets certain technical criteria and can
be used by people with disabilities. is includes access by people who are mobility impaired,
blind, low vision, deaf, hard of hearing, or who have cognitive impairments. Accessibility
features in Adobe Acrobat, Adobe Reader and in the Portable Document Format (PDF) make
it easier for people with disabilities to use PDF documents and forms, with and without the aid
of assistive technology soware and devices such as screen readers, screen magniers, text-tospeech soware, speech recognition soware, alternative input devices, Braille embossers, and
refreshable Braille displays.
e Web Content Accessibility Guidelines (WCAG) 2.0 (ISO/IEC 40500:2012) and the PDF/
UA (ISO 14289-1) standard cover a wide range of recommendations for making content more
accessible to people with disabilities. One bene t of following these guidelines is that content
becomes more usable for all users. For example, the underlying document structure that makes
it possible for a screen reader to properly read a PDF out loud also makes it possible for a mobile
device to correctly reow and display the document on a small screen. Similarly, the preset tab
order of an accessible PDF form helps all users—not just users who rely on the keyboard—
complete the form more easily.
Overview of Portable Document Format (PDF)
e PDF format is the native le format of the Adobe® Acrobat® family of products. e goal of
this format and these products is to enable users to exchange and view electronic documents
easily and reliably, independently of the environment in which they were created. PDF relies
on the same imaging model as the PostScript® page description language to describe text and
graphics in a device-independent and resolution-independent manner. To improve performance
for interactive viewing, PDF denes a more structured format than that used by most PostScript
language programs. PDF also includes objects, such as annotations and hypertext links, that are
not part of the page itself but that are useful for interactive viewing and document interchange.
A logical tagged structure tree is used within each document to provide a meaningful reading
order for content, as well as a method for dening structural elements role and relationship to
page content. Within this tag structure, other properties such as alternative text and replacement
text can be provided.
Determine the Accessibility Path for each PDF Document
PDF les are created in a variety of ways, from a variety of applications, and for a variety
of purposes. Achieving the desired accessibility goals for an individual PDF le requires
understanding the nature of the PDF and its intended use. Adobe Acrobat XI Pro provides
several tools including the Make Accessible Action wizard and the Accessibility Checker to assist
authors in evaluating and xing issues that can impact accessibility.
e Adobe® Acrobat® XI Pro Accessibility Guide: PDF Accessibility Repair Workow document
provides details on how to assess existing PDF les for accessibility. By following these
procedures in the recommended order, authors can eciently proceed through the analysis of
1
PDF Accessibility Overview
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
a PDF le in a systematic fashion. Systematically ruling out or conrming certain characteristics
found in a PDF le will guide the author to the most appropriate path for making an individual
PDF document accessible.
Note: ese Best Practices techniques require access to Adobe Acrobat Pro XI for Windows.
Adobe Reader XI and Adobe Acrobat XI Standard do not have the complete set of tools
needed to create and validate PDF documents for accessibility.
Start with an Accessible Document
e PDF format is a destination le format. PDF les are typically created in some other
application. Optimally document accessibility should begin in the native document format.
For example, many documents are created in a word processing or desktop publishing
application, and then exported as PDF documents. ere many things that can be done in
native document applications to support accessibility, such as adding alternative text for
images; dening structural headings, lists, and data tables; providing document language;
and seing document properties such as titles. Adobe desktop publishing applications such
as Adobe InDesign and Framemaker support these features, as well as other word processing
applications such as Microso Word. For information on building accessibility into documents
created with Adobe products visit the Adobe Accessibility website. To gain assistance on
adding accessibility into Microso Word documents prior to conversion to PDF format please
visit the Microso Enable website. Making the native document accessible allows for less work
when changes are made to the native document and the PDF document is regenerated.
If the native document is not available, in most cases, the document can still be made fully
accessible. Without accessibility in the native format there will likely be more manual work
required in the PDF to properly tag the document. ere are some items such as choosing
sucient contrast between foreground and background colors that must be implemented in
the native document.
Characteristics of Accessible PDF les
Accessible PDFs include but are not limited to the following characteristics:
Searchable text
A document that consists of scanned images of text is inherently inaccessible because the
content of the document is a graphic representing the leers on the page, not searchable text.
Assistive technology soware cannot read or extract the words in a graphical representation.
Furthermore, users cannot select or edit the text or manipulate the PDF for accessibility.
Scanned images of text must be converted into to searchable text using optical character
recognition (OCR) before addressing accessibility in the document.
Fonts that allow Characters to be Extracted to Text
e fonts in an accessible PDF must contain enough information for Acrobat to correctly extract
all of the characters to text for purposes other than displaying text on the screen. Acrobat
extracts characters to Unicode text when you read a PDF with a screen reader or the Read Out
Loud tool, or when you save as text for a Braille embosser. is extraction fails if Acrobat cannot
determine how to map the font to Unicode characters.
2
PDF Accessibility Overview
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Interactive Labeled Form Fields with Accessible Error Messages and No Timing
Some PDFs contain interactive forms that people ll out using a computer. To be accessible,
form elds must be interactive; that is, a user must be able to enter values into the form elds.
Interactive PDF forms also have a dened tab order which allows users of assistive technology
to use the Tab key in order to progress from one form eld or interactive control to the next in
a logical manner. Refer to the document Adobe® Acrobat® XI Pro Accessibility Guide: Creating
Accessible Forms for complete details. Forms must provide identication, give tips on proper
completion, and prevent errors. Form entry should not be timed unless the user can request
more time.
Other Interactive Features: Hyperlinks and Navigational Aids
Navigational aids in a PDF—such as links, bookmarks, headings, a table of contents, and a preset
tab order for form elds—assist all users in using the document without having to read through
the entire document, word by word. Bookmarks are especially useful and can be created from
document headings. ese features can be accessed using the keyboard without relying on the
mouse, and allow for multiple way for users to navigation content.
Document Language and Title Indication
Specifying the document language in a PDF enables some screen readers to switch the current
speech synthesizer to the appropriate language, allowing correct pronunciation of content
in dierent languages. Providing a document title allows the user to locate and identify the
document.
Security that will not Interfere with Assistive Technology
Some authors of PDFs restrict users from printing, copying, extracting, editing or adding
comments to text. e text of an accessible PDF must be available to a screen reader. Acrobat’s
security seings can be set to protect document content while not interfering with a screen
reader’s ability to convert the on-screen text to speech or Braille.
Document Structure Tags and Proper Reading Order
To read a document’s text and present it in a way that makes sense to the user, a screen reader
or other text-to-speech tool requires that the document be structured. Document structure tags
in a PDF dene the reading order and identify headings, paragraphs, sections, tables and other
page elements. e tags structure also allows for documents to be resized and reowed for
viewing at larger sizes and on mobile devices.
Alternative Text Descriptions for Non-Text Elements
Document features such as images and interactive form elds cannot be understood by the
user of a screen reader unless they have associated alternative text. ough link text is available
to screen reader users, it is possible to provide more meaningful descriptions via replacement
(actual) text. Alternative text for images and tooltips can aid many users, including those with
learning disabilities. Equivalents for multimedia, including any audio and video elements, must
also be present.
Other Accessible Characteristics
ere are additional characteristics of accessible documents including:
• No reliance on color or sensory characteristics alone to convey meaning
• Use of color combinations that provides a sucient degree of contrast
• Controls for audio
3
PDF Accessibility Overview
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
• Use of text instead of images of text
• No use of ashing or blinking elements
• No focus changes without user initiation
• Consistent navigation and identication of elements
Adobe Acrobat and Adobe Reader Accessibility Features
Accessibility features in Adobe Acrobat XI and Adobe Reader XI fall into two broad categories:
features that make the reading of PDF documents more accessible, and features that help create
accessible PDF documents. To create accessible PDF documents, you must use Acrobat Pro.
Features to Support the Reading of PDFs by People with Disabilities
All versions of Adobe Acrobat XI, Adobe Reader XI, Acrobat XI Standard and Acrobat XI Pro
provide support for the accessible reading of PDF files by persons with disabilities:
• Preferences and commands to optimize output for assistive technology
soware and devices, such as saving as accessible text for a Braille printer
• Preferences and commands to make navigation of PDFs more accessible,
such as automatic scrolling and opening PDFs to the last page read
• An Accessibility Setup Assistant Wizard for easy seing of most
preferences related to accessibility
• Keyboard alternatives to mouse actions
• Reow capability to temporarily present the text of a PDF in a single,
easy-to-read column
• Read Out Loud text-to-speech conversion
• Support for screen readers and screen magniers
• Support for high contrast and alternative foreground and background
colors
Features to Support the Creation of Accessible PDFs
• Creation of tagged PDFs from authoring applications
• Conversion of untagged PDFs to tagged PDFs from within Acrobat
• Security seings that allow screen readers to access text while preventing
users from copying, printing, editing and extracting text
• Ability to add text to scanned pages to improve accessibility
• Tools for editing reading order and document structure
• Tools for creating accessible PDF forms
• Ability to set document properties including title and expose them
through the title bar of the application
ough Acrobat Standard provides some functionality for making existing PDFs accessible,
Acrobat Pro must be used to perform most tasks—such as editing reading order or editing
document structure tags—that are necessary to make PDF documents and forms accessible
(“Table 1. Features for Creating Accessible PDF Files by Product” on page 5).
4
PDF Accessibility Overview
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Accessibility Features of Adobe XI Reader, Adobe XI Standard, and Adobe
XI Pro
Table 1. Features for Creating Accessible PDF Files by Product
Create PDF documents from
any application that prints
Convert Microso Word,
Excel, PowerPoint, Publisher
and Access les to PDF with
one-buon ease*
Capture web pages from
Microso Internet Explorer
and Mozilla Firefox as rich,
dynamic PDF les for review
and archiving with onebuon ease*
Scan paper documents
to PDF and automatically
recognize text with optical
character recognition (OCR)
Save PDF les as Microso
Word documents, retaining
the layout, fonts, formaing
and tables to facilitate reuse
of content*
Easily create llable PDF
forms from paper or existing
les using the Form Wizard
Enable users of Adobe
Reader® (version 8 or later)
to ll in and save PDF forms
locally
Customize Accessibility
Preferences with an easy-touse wizard
Set high contrast colors for
beer visibility
Enable large type display by
seing text to reow through
pages
Listen to the text in a PDF le
as it is read aloud
Make PDF documents more
accessible by adding tags to
control reading order and
improve navigation
Specify a reading order for
pages or columns of text
Validate accessible PDF
documents and check for
possible accessibility issues
Adobe
Reader XI
Acrobat XI
Standard
• •
• •
• •
• •
• •
• •
• •
• • •
• • •
• • •
• • •
Acrobat XI
Pro
•
•
•
5
PDF Accessibility Overview
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
e Acrobat XI Pro Accessibility Guide Series
Adobe has created a series of accessibility guides for Adobe Acrobat XI Pro to assist content
authors in creating accessible PDF documents. ere are four guides in this series:
PDF Accessibility Overview (this document)
e Adobe® Acrobat® XI Pro Accessibility Guide: PDF Accessibility Overview details what is meant
by accessibility in the PDF le format. It distinguishes between the accessibility features of the
le format, of Adobe Acrobat XI and of the Adobe Reader application, and how the features of
the soware and the le format interact to achieve accessibility for people with disabilities.
Acrobat XI Pro PDF Accessibility Repair Workow
e Adobe® Acrobat® XI Pro Accessibility Guide: PDF Accessibility Repair Workow provides a step-
by-step method for analyzing existing PDF les and making them accessible based upon that
analysis. is workow coincides with the workow provided in the Make Accessible Action
wizard and potential issues tested for in the Accessibility Checker tool.
Using the Accessibility Checker in Acrobat XI Pro
e Adobe® Acrobat® XI Pro Accessibility Guide: Using the Accessibility Checker describes the
PDF accessibility checkers that are included in Adobe Acrobat XI Pro. Even if you generate an
accessible PDF le from an authoring application such a word processor or desktop publishing
program, you should then follow the steps in this guide in order to identify any items that may
have been missed in the initial conversion, or to add PDF accessibility features that were not
provided by the authoring tool.
Creating Accessible PDF Forms with Acrobat XI Pro
e guide entitled Adobe® Acrobat® XI Pro Accessibility Guide: Creating Accessible Forms describes
how to use the forms tools within Adobe Acrobat XI Pro to add descriptions to form elds, tag
untagged forms, set the tab order, manipulate tags and perform other PDF accessibility tasks.
ese techniques do not apply to PDF forms from Adobe LiveCycle Designer, as a separate
process is provided for making LiveCycle forms accessible.
Acrobat XI Pro Complete Best Practices for Accessibility
e complete content of each individual guide is also available as a single, comprehensive
document entitled Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for Accessibility.
6
Using the Acrobat XI Pro Accessibility Checker
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Determine how easily persons with disabilities can access PDF
documents with the Adobe Acrobat XI Pro Accessibility Checker
e accessibility checking tools in Adobe Acrobat XI Pro—Accessibility Checker (Full Check) and
the Make Accessible action wizard—can identify many issues in PDF documents that may be in
conict with Adobe’s interpretations of the accessibility guidelines referenced in the application
and its documentation. ese tools do not check documents for all accessibility criteria,
including those in such referenced guidelines, and Adobe does not warrant that documents
comply with any specic guidelines or regulations.
e Make Accessible Action Wizard
e Make Accessible action wizard walks users through the steps required to make a PDF
accessible. It prompts to address accessibility issues, such as a missing document description
such a document title. It looks for common elements that need further action, such as scanned
text, form elds, tables, and images without alternative text. is action wizard can be run
on all PDFs except dynamic forms (XFA documents) and portfolios. e last step of the Make
Accessible action wizard is to run the Acrobat Pro Accessibility Checker (Full Check). For
complete instructions on how to make documents accessible and repair the accessibility tag
structure of a document refer to the document titled “Adobe Acrobat XI Pro Accessibility Repair
Workow”.
Accessibility Checker (Full Check)
Use the Accessibility Full Check to perform a thorough check for many characteristics of
accessible PDFs, such as the use of alternative text on images, the presence of tags, document
language, and fonts that can be mapped reliably to Unicode text.
From the Accessibility Checker dialog, it is possible to choose which kinds of accessibility issues
to look for. ere are also options to view and save the results. To run the Accessibility Full
Check, perform the following:
1. Open the Accessibility Tool pane.
2. Select View > Tools > Accessibility from the Adobe Acrobat XI Pro menu.
(Refer to “Figure 1. Acrobat XI Pro Accessibility Full Check Tool” on
page 8.)
3. Select Full Check from the Accessibility tools.
4. e Accessibility Checker Options dialog appears (Refer to “Figure 2.
Acrobat XI Pro Accessibility Checker Options Dialog” on page 8).
5. Set Report Options.
6. You can save the results as an HTML le or aach the report to the
document.
7. Select a page range if you prefer to perform a check on individual sections
of a document.
8. Select checking options.
7
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
9. Choose a category from the dropdown, and then select the accessibility
options to check for. By default, everything but “tables must have a
summary” is checked.
10. You can select Document; Page Content; Forms, Tables and Lists; and
Alternate Text and Headings to reveal checkboxes that let you set the
level of testing that you want Acrobat to perform.
11. Activate the Start Checking buon.
Figure 1. Acrobat XI Pro Accessibility Full Check Tool
Figure 2. Acrobat XI Pro Accessibility Checker Options Dialog
Figure 3. Aer the check is complete, the results are displayed via the Accessibility Checker
8
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
panel. (See “Figure 4. Acrobat Xi Pro Accessibility Checker Panel” on page 9)
Figure 4. Acrobat Xi Pro Accessibility Checker Panel
If a report was checked to be created in the Accessibility Checker Options dialog, the results are
available in the selected folder or an aachment. (See “Figure 5. Acrobat XI Pro Accessibility
Report” on page 10) e Accessibility Report can also be displayed by activating the
Accessibility Report tool command in the Accessibility tools pane.
9
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Figure 5. Acrobat XI Pro Accessibility Report
e Accessibility Full Check feature is unable to distinguish the intention of the document
author such as whether a gure is purely decorative, so some issues it reports may not aect
the functional accessibility of the document. Manual review of the issues may be required to
determine whether to x or ignore the issue.
Accessibility Checker Options
The Accessibility Checker (Full Check) has the following options that can be selected:
• Document
• Accessibility permission ag is set
• Document is not image-only PDF
• Document is tagged PDF
• Document structure provides a logical reading order
• Text language is specied
• Document title is showing in title bar
• Bookmarks are present in large documents
• Document has appropriate color contrast
• Page Content
• All page content is tagged
• All annotations are tagged
• Tab order is consistent with structure order
• Reliable character encoding is provided
• All multimedia objects are tagged
• Page will not cause screen to icker
• No inaccessible scripts
• Navigation links are not repetitive
• Page does not require timed responses
10
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
• Forms, Tables and Lists
• All form elds are tagged
• All form elds have description
• TR must be a child of Table, THead, TBody, or TFoot
• TH and TD must be children of TR
• Tables must have headers
• Tables must contain the same number of columns in each row and
rows in each column
• Tables must have a summary
• LI must be a child of L
• Lbl and LBody must be children of LI
• Alternate Text and Headings
• Figures require alternate text
• Alternate text that will never be read
• Alternate text must be associated with some content
• Alternate text should not hide annotation
• Elements require alternate text
• Appropriate heading nesting
Accessibility Checker Panel
Once a report has been run, the issues that have been found are displayed in the Accessibility
Checker panel. e results tree displays one of the following states for each rule check (See
“Figure 6. Acrobat Rule Check States” on page 12):
• Passed: e item passed this accessible check.
• Passed Manually: e item was marked passed by manual inspect.
• Skipped By User: e rule was not selected in the Accessibility Checker
Options dialog box.
• Needs Manual Check: e Full Check feature could not check the item
automatically. Verify the item manually.
• Failed: e item did not pass the accessibility check.
11
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Figure 6. Acrobat Rule Check States
To x a failed check aer running Accessibility Full Check, activate the context menu—right-click
(Windows) or Control-click (Mac OS) the item in the Accessibility Checker panel. Choose one
of the following options from the context menu (See “Figure 7. Accessibility Checker Panel
Showing Issue States for each Checker Option” on page 13):
• Fix: Acrobat either xes the item automatically, or displays a dialog box
prompting the user to x the item by entering information or making
a choice. For example, a dialog is displayed allowing the user to enter
alternative text for an image.
• Skip Rule: Deselects this option in the Accessibility Checker Options
dialog box for future checks of this document, and changes the item
status to Skipped.
• Explain: Opens the online Help.
• Check Again: Runs the checker again on all items. Choose this option
aer modifying one or more items.
• Show Report: Displays the accessibility report for the page range/
document with links to tips on how to repair failed checks. e link to tips
is the same as the help that is provided by the “explain” item. Once the
report is shown, a new option to aach the report also appears.
• Options: Opens the Accessibility Checker Options dialog box where
checking options can be set.
12
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Figure 7. Accessibility Checker Panel Showing Issue States for each Checker Option
Accessibility Checker Option Details
This section provides information on each option in the Accessibility Checker. Please refer to the
“Adobe Acrobat XI Pro Accessibility Repair Workflow” document for details on how to address
issues for each category.
Documentation Category
Accessibility permission ag: A document author can specify that no part of an accessible PDF
is to be copied, printed, extracted, commented on, or edited. is seing can interfere with the
user of a screen reader’s ability to read the documents screen readers must be able to copy or
extract the document’s text to convert it to speech.
is ag reports whether it’s necessary to turn on the security seings that allow accessibility.
To x the rule automatically, select Accessibility Permission Flag on the Accessibility Checker
panel. en, choose Fix from the Options menu.
Note: Refer to the related WCAG section: 1.1.1 Non-text Content. (A), 4.1.2 Name, role,
value
Image-only PDF: Reports whether the document contains non-text content that is not
accessible. If the document appears to contain text, but doesn’t contain fonts, it could be an
image-only PDF le.
To x this item automatically, select Image-only PDF on the Accessibility Checker panel, and
choose Fix from the Options menu. is will open the “Recognize Text - General Seings” dialog
and then perform optical character recognition (OCR) on the document.
Note: See the related WCAG section: 1.1.1. Non-text content (A)
13
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Tagged PDF: If this rule check fails, the document is not tagged to specify the correct reading
order for reow and assistive technology. Documents without tags also do not provide
information describing the logical structure and relationship of elements to users of assistive
technology.
To x this item automatically, select Tagged PDF on the Accessibility Checker panel, and then
choose Fix from the Options menu. Acrobat automatically adds tags to the PDF. e tags that
were added still must be reviewed to ensure they are correct.
Note: Refer to the related WCAG section: 1.3.1 Info and Relationships, 1.3.2 Meaningful
Sequence, 2.4.1 Bypass Blocks, 2.4.4 Link Purpose, 2.4.5 Multiple Ways, 2.4.6
Headings and labels, 3.1.2 Language of Parts, 4.1.2 Name, role, value
Logical reading order: Verify this rule check manually. Make sure that the reading order
displayed in the Tags panel reects the logical reading order of the document.
Primary language: Seing the document language in a PDF enables some screen readers to
switch to the appropriate language. is check determines whether the primary text language
for the PDF is specied. If the check fails, set the language.
To set the language automatically, select Primary Language in the Accessibility Checker tab, and
then choose Fix from the Options menu. Choose a language in the Set Reading Language dialog
box, and then click OK. is does not set the language for specic parts of the document that
may be in dierent languages. To set specic portions of the document in dierent languages
refer to the Adobe Acrobat XI Pro Accessibility Repair Workow guide.
Note: See the related WCAG section: Language of Page (Level A)
Title: Reports whether there is a document title. Document authors can choose to have the title
appear in the Acrobat or Adobe Reader application title bar rather than the document le name.
To x the title automatically, select Title in the Accessibility Checker tab, and choose Properties
from the Options menu. Enter the document title in the Description dialog box (deselect Leave
As Is, if necessary).
Note: See the related WCAG section: 2.4 Page Titled (Level A)
Bookmarks: is check fails when the document has 21 or more pages, but does not have
bookmarks that parallel the document structure.
To add bookmarks to the document, select Bookmarks on the Accessibility Checker panel, and
choose Fix from the Options menu. In the Structure Elements dialog box, select the element(s)
that you want to use as bookmarks, and click OK (See “Figure 8. Fix missing bookmarks in
Acrobat” on page 15). You can also access the Structure Elements dialog box by clicking the
Options menu on the Bookmark tab.
Note: See the related WCAG sections: 2.4.1 Bypass Blocks (Level A), 2.4.5 Multiple
Ways (Level AA)
14
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Figure 8. Fix missing bookmarks in Acrobat
Color contrast: When this check fails, it’s possible that the document contains content that is
not accessible to people who have low vision or color deciencies.
To x this issue, make sure that the document’s content adheres to the guidelines outlined in
WCAG section 1.4.3 or include a recommendation that the PDF viewer use high-contrast colors
and verify that all content is readable in the high-contrast color scheme:
To check the document in a high contrast color scheme perform the following:
1. Choose Edit > Preferences (Windows) or Acrobat > Preferences (Mac OS).
2. Choose the Accessibility category.
3. Select Replace Document Colors, and then select Use High-Contrast
Colors. Choose the color combination that you want from the popup menu, and then click OK (See “Figure 9. Adjust viewer to display
document with high contrast seings” on page 16).
15
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Figure 9. Adjust viewer to display document with high contrast seings
Page content
Tagged content: is check reports whether all content in the document is tagged. Make sure
that all content in the document is either included in the Tags tree, or if decorative marked as an
artifact.
Perform one of the following to x this check:
• If the content is purely decorative, set it as an artifact.
• Use the Touch Up Reading Order tool to tag the content.
• Use the Tag panel to tag the content.
Please refer to the Adobe Acrobat XI Pro Accessibility Repair Workflow Guide for instructions on
how to tag content.
Note: See the related WCAG sections: 1.1.1 Non-text content (A), 1.3.1 Info and
Relationships (Level A), 1.3.2 Meaningful Sequence (Level A), 4.1.2 Name, role,
value
Tagged annotations: is option checks whether all annotations are tagged. Make sure that
annotations such as comments and editorial marks (such as insert and highlight) are either
included in the Tags tree if meaningful, or marked as artifacts if they’re purely decorative or
duplicated in the content.
• If the content is purely decorative, set it as an artifact.
• Use the Tag Panel and the Find command to search for and tag the
content as an annotation.
Please refer to the Adobe Acrobat XI Pro Accessibility Repair Workflow Guide for instructions on
how to tag annotations.
To have Acrobat assign tags automatically to annotations as they’re created, choose Tag
Annotations from the Options menu on the Tags panel. is is the easiest approach to tag
annotations that have not already been created, as the annotation tags will appear in the correct
location in the reading order of a properly tagged document.
16
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Note: See the related WCAG section: 1.3.1 Info and Relationships (Level A), 4.1.2 Name,
role, value
Tab order: Because the Tab key is oen used to navigate links, annotations, and form elds in a
PDF, it’s necessary that the tab order parallels the document structure.
To x the tab order automatically, select Tab Order on the Accessibility Checker panel, and
choose Fix from the Options menu. is will specify the tab order to follow the document
structure.
Note: See the related WCAG section: 2.4.3, Focus Order (Level A)
Character encoding: Specifying the encoding helps PDF viewers present users with readable
text. However, some character-encoding issues are not repairable within Acrobat.
To ensure proper encoding, do the following:
• Verify that the necessary fonts are installed on your system.
• Use a dierent font (preferably OpenType) in the original document, and
then re-create the PDF.
• Re-create the PDF le with a newer version of Acrobat Distiller.
• Use the latest Adobe PostScript driver to create the PostScript le, and
then re-create the PDF.
Note: e WCAG does not directly address Unicode character mapping.
Tagged multimedia: is rule checks whether all multimedia objects are tagged. Make sure that
content is either included in the Tags tree or, if decorative or duplicative, marked as an artifact.
Perform one of the following to x this check:
• If the content is purely decorative, set it as an artifact.
• Use the Touch Up Reading Order tool to tag the content.
• Use the Tag panel to tag the content.
Please refer to the Adobe Acrobat XI Pro Accessibility Repair Workflow Guide for instructions on
how to tag content.
In addition to providing tags and description of all multimedia, captions (for people who are
deaf or hard of hearing) or audio descriptions (for people who are blind or visually impaired)
may need to be synchronized with the multimedia. Please refer to the relevant guideline or
standard for multimedia requirements.
Note: See the related WCAG sections: 1.1.1 Non-text Content. (A), 1.2.1 Audio- only
and Video- only (Prerecorded). (A), 1.2.2 Captions (Prerecorded). (A), 1.2.3 Audio
Description or Media Alternative (Prerecorded). (A), 1.2.5 Audio Description
(Prerecorded). (AA)
17
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Screen icker: Elements that make the screen icker, such as animations and scripts can cause
seizures in individuals who have photosensitive epilepsy. ese elements can also cause
diculty for users with low vision and people with cognitive disabilities.
If the Screen Flicker rule fails, manually remove or modify the script or content that causes
screen icker.
Note: See these related WCAG sections: 2.3.1 ree Flashes or Below reshold. (Level
A)
Scripts: Content cannot be script-dependent unless both content and functionality are
accessible with the keyboard and to assistive technologies. Make sure that scripting does not
interfere with keyboard navigation or prevent the use of any input device.
Check the scripts manually. Remove or modify any script or content that compromises
accessibility.
Note: See these related WCAG sections: 1.1.1 Non-text Content. (A), 2.1.1 Keyboard
(Level A), 2.2.2 Pause, Stop, Hide. (Level A), 4.1.2 Name, role, value
Timed responses: is check applies to documents that contain forms with JavaScript. If the rule
check fails, make sure that the page does not require timed responses. Edit or remove scripts
that impose timely user responses so that users have enough time to read and use the content.
Note: See the related WCAG section: 2.2.1 Timing Adjustable. (Level A)
Navigation links: For URLs to be accessible to screen readers, they must be active links that
are correctly tagged in the PDF document and keyboard accessible. (e best way to create
accessible links is with the Create Link command, which adds link objects that screen readers
require to recognize a link.) Use the Tags panel’s Find command to properly tag Links that are
not accessible.
Link text must also be understandable on its own without surrounding content. If this rule check
fails, check navigation links manually and verify that the content does not have links with an
identical name but dierent target locations. Either change the link text or add actual text to the
link tag to provide additional description out of context for users of screen readers.
Documents must also provide a way for users to skip over items that appear multiple times.
For example, if the same links appear on each page of the document, also include a bookmark
element to skip past the repetitive link group to the next tagged element in the structure . Links
can not be used to skip past repetitive links as links can not focus tags in the tree and only scroll
or zoom to a particular page view.
Note: See the related WCAG section: 2.4.1 Bypass Blocks (Level A), 2.1.1 Keyboard
(Level A), 2.4.4 Link Purpose (In Context) (Level A).
Forms
Tagged form elds: All form elds must be tagged with a form tag and form object element and
part of the document structure. In addition, eld descriptions (labels) must be provided via the
tooltip form eld property to provide the user with a label or instructions for a eld.
18
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
To tag form elds, choose Tools > Accessibility > Add Tags To Form Fields. is add the tags and
form object elements to the form elds in the proper location in the Tags panel. is step does
not add eld descriptions.
Note: See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 4.1.2
Name, role, value
Field descriptions: All form elds must have a text label/description (this is set via the form
eld’s tooltip property).
To add a text description to a form eld, use the form tools. Please refer to the “Adobe Acrobat
XI Pro Accessibility Form Guide” document for complete instructions on how to set form eld
descriptions. Accessibility guidelines and standards may also require that visual labels be
present. e tooltip property is only visible via the mouse and not the keyboard, thus, onscreen labels should also be provided for all user input.
Note: See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 3.3.2
Labels or Instructions (Level A), 4.1.2 Name, role, value
Alternate Text
Figures alternate text: Make sure that images in the document either have alternate text or, if
decorative, are marked as artifacts.
If this check fails, perform one of the following:
• Select Figures Alternate Text in the Accessibility Checker panel, and
choose Fix from the Options menu (or context menu). Add alternate text
as prompted in the Set Alternate Text dialog box (See “Figure 10. Set
Alternate Text through the Fix option in the Accessibility Checker” on
page 20).
• Use the Tags panel to add alternate text for images in the PDF.
• Use the Tags panel, Content Panel, or Touch Up Reading Order tool to
make the content an artifact.
Note: See the related WCAG section: 1.1.1 Non-text Content. (A)
19
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Figure 10. Set Alternate Text through the Fix option in the Accessibility Checker
Nested alternate text/actual text:
Screen readers do not read the alternate/actual text for nested elements. erefore, do not
apply alternate text to elements with children unless the alternative text or actual text covers the
content for these elements as well. Alternative text is used to provide an alternative for images
(gures). Actual text is used to provide an alternative to text content.
Remove alternate/actual text from nested elements via the Tags panel. For more information
on using alternative text and actual text refer to the Adobe Acrobat XI Pro Accessibility Repair
Workow Guide.
Refer to the related WCAG success criteria: 1.1.1 Non-text Content (Level A).
Associated with content: Make sure that alternate text is always an alternate representation for
content on the page. If an element has alternate text, but does not contain any page content,
there is no way to determine which page it is on. If the Screen Reader Option in the Reading
preferences is not set to read the entire document, then screen readers never read the alternate
text.
To x this issue, assign page content to the tag that contains the alternative/actual text.
Note: See the related WCAG section: 1.1.1 Non-text Content. (A)
Hides annotation: Alternate text can not hide an annotation. If an annotation is nested under a
parent element with alternate/actual text, then a screen reader will not announce it.
Remove alternate/actual text from parent element. If alternate/actual text is needed make
sibling objects out of content and the annotation and assign the actual/alternate text to the
sibling tag. For more information on using alternate text and actual text, refer to the Adobe
Acrobat XI Pro Accessibility Repair Workow Guide.
See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 4.1.2 Name, role, value
Other elements alternate text: is option checks for content other than gures that requires
alternate text such as multimedia, annotation, or 3D models. Make sure that alternate text is
always an alternate representation for content on the page. If an element has alternate text
but does not contain any page content, there is no way to determine which page it is on. If the
Screen Reader Options in the Reading preferences is not set to read the entire document, then
20
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
screen readers won’t read the alternate text. If additional description is required for the object
beyond what can be provided in alternative text, provide a on-page description or link to a
description of the non-text object.
Note: See the related WCAG section: 1.1.1 Non-text Content. (A)
Tables
Because table structure can be complex, it is best practice to check them for accessibility
manually.
Rows: is check indicates whether each TR in a table is a child of Table, THead, TBody, or
TFoot.
To x this issue ensure that any TR tags are a child of a Table, THead, TBody, or TFoot tag.
Note: Related WCAG section: 1.3.1 Info and Relationships. (Level A)
TH and TD: is check indicates whether a proper table structure exists. TH and TD must be
children of a TR element; if not this check fails.
To x this issue, ensure that TH or TD tags are place under a TR tag.
Note: See related WCAG section: 1.3.1 Info and Relationships (Level A)
Headers: For accessibility, it’s necessary that all tables in the PDF have a header.
To x this issue, ensure that all tables contain table header cells.
Note: See the related WCAG section: 1.3.1 Info and Relationships (Level A)
Regularity: To be accessible, tables must contain the same number of columns in each row, and
rows in each column.
To x this issue, ensure that each table row has the same number of columns or the ColSpan and
RowSpan properties of a cell are set properly to account for all cells in a row.
Note: See the related WCAG section: 1.3.1 Info and Relationships (Level A)
Summary: Table summaries are optional unless the table data cannot be understood without it.
Summaries can improve accessibility in complex data tables or when the way in which the data
is read may be important.
To x this issue, provide a table summary for data tables where it is needed to make the data
easier to understand, or to provide instructions on the data should be reviewed.
Note: See the related WCAG section: 1.3.1 Info and Relationships. (Level A)
21
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Lists
List items: is check reports whether each LI is a child of L tag. When this check fails, the
structure of this list is incorrect. Lists must have the following structure: a List element must
contain List Item elements; List Item elements can only contain Label elements and List Item
Body elements.
To x this issue, ensure that all list item elements have a parent L tag.
Note: See the related WCAG section: 1.3.1 Info and Relationships. (Level A)
Lbl and LBody: Lists must have the following structure: a List element must contain List Item
elements; List Item elements can only contain Label elements and List Item Body elements.
When this check fails, the structure of this list is incorrect.
To x the list structure, use the Tags panel to place Lbl and LBody elements under each list item.
e list bullet or number should be a text node of the Lbl tag and the list item text a text node
of the LBody tag.
Note: Refer to the related WCAG success criteria: 1.3.1 Info and Relationships (Level
A)
Headings
Appropriate nesting: is rule checks nested headings. When this check fails, headings are
not nested properly. For example, a level 1 heading should precede a level 2 heading, etc. e
Accessibility Checker is not able to determine when heading structures must be used—that
must be determined by manually reviewing the document.
To x this issue, ensure that all heading levels are nested accordingly with no missing heading
levels. Use the Tags Panel or Touch Up Reading Order tool to assign heading tags.
Refer the related WCAG section: 1.3.1 Information and Relationships. (Level A). e order of
headings is not required under WCAG, and is only an advisory technique.
Continue Checking Until All Issues are Addressed
Repeat the process of running the Accessibility Checker and associated repair techniques along
with the Hints for Repair until the Accessibility Checker indicates “Passed” for all selected tests
(See “Figure 11. A Successful Accessibility Check” on page 23).
Note: While the Accessibility Checker helps evaluate the accessibility of a document
and helps identify areas that may be in conict with Adobe’s interpretations
of the referenced guidelines, the Accessibility Checker can not automatically
check all accessibility guidelines and criteria, including those in such referenced
guidelines, and Adobe does not warrant that any documents will comply with
any specic guidelines or regulations. Please consult with appropriate legal
counsel for guidance on compliance with the referenced guidelines or any other
accessibility guidelines.
22
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
Figure 11. A Successful Accessibility Check
Additional Functional Validation Techniques
The Accessibility Checker can evaluate many of the technical requirements for accessibility. The
best way to test the functional accessibility of a document is to use the document with the same
tools that readers will use. It is recommended to review the document with assistive technology
including a screen reader. Even when a screen reader is not available, the following methods
provided by Acrobat should be used to check the accessibility of a PDF file:
Use Reflow view to quickly check reading order:
1. Activate the View > Zoom > Zoom Text.
2. Enter 200 in the zoom eld.
3. Activate the View > Zoom.
4. Activate e reow option.
5. Verify that all content appears in the correct order.
6. Verify that all content is readable while zoomed.
Use Read Out Loud to experience the document as it will be heard by readers who use this
text-to-speech tool.
1. Activate > View > Read Out Loud > Activate Read Out Loud
2. Activate > View > Read Out Loud > Read this page only
3. Verify that all page content is announced in the correct order.
23
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
4. Repeat for each page.
Save the document as accessible text and then read the saved text file in a word-processing
application to experience the document as it will be read by readers who may emboss the
document in Braille.
1. Activate File > Save as > Text Plain (.txt)
2. Select the desired location.
3. Activate the Save buon.
WCAG 2.0 Mapng to PDF/UA
The table below provides a mapping between WCAG 2.0 success criteria, the PDF/UA standard
(ISO 14289-1) and PDF techniques for WCAG 2.0.
WCAG 2.0 ISO 14289 -1 (File) Techniques
1.1.1 Non-text Content. (A) • 7.3 addresses content
requiring text alteration.
• 7.18.1 paragraph 4
addresses control
descriptions.
• 7.18.6.2 addresses timebased media alternatives.
Test, Sensory, and
CAPTCHA use cases are
addressed via the technical
means used.
• PDF1
• PDF4
1.2.1 Audio- only and Videoonly (Prerecorded). (A)
1.2.2 Captions (Prerecorded).
(A)
• 7.1 paragraph 1, sentence 2
addresses decoration.
• 7.18.6.2 addresses timebased media alternatives.
Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
• 7.18.6.2 addresses timebased media alternatives.
Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
• General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrmedia-equiv-av-only-alt
• General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrmedia-equiv-captions
24
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
WCAG 2.0 ISO 14289 -1 (File) Techniques
1.2.3 Audio Description
or Media Alternative
(Prerecorded). (A)
1.2.4 Captions (Live). (AA)
1.2.5 Audio Description
(Prerecorded). (AA)
1.2.6 Sign Language
(Prerecorded). (AAA)
1.2.7 Extended Audio
Description (Prerecorded).
(AAA)
1.2.8 Media Alternative
(Prerecorded). (AAA)
1.2.9 Audio- only (Live).
(AAA)
1.3.1 Info and Relationships. (Level
A)
• 7.18.6.2 addresses timebased media alternatives.
Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
• Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
• 7.18.6.2 addresses timebased media alternatives.
Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
• Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
• Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance
• 7.18.6.2 addresses timebased media alternatives.
Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
• Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
• 7.1 - 7.10 and 7.20 address
structure and relationships
in content.
• General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrmedia-equiv-audio-desc
• General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrmedia-equiv-real-timecaptions
• General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrmedia-equiv-audio-desconly
• PDF6
• PDF9
• 7.17 and 7.18 address
structure and relationships
in annotations.
• PDF10
• PDF11
• PDF12
• PDF17
• PDF20
• PDF21
25
Using the Acrobat XI Pro Accessibility Checker
Adobe® Acrobat® XI Pro Accessibility Guide: Best Practices for PDF Accessibility
WCAG 2.0 ISO 14289 -1 (File) Techniques
1.3.2 Meaningful Sequence.
(Level A)
1.3.3 Sensory Characteristics.
(Level A)
1.4.1 Use of Color. (Level A)
1.4.2 Audio Control. (Level A)
1.4.3 Contrast (Minimum).
(Level AA)
1.4.4 Resize text. (Level AA)
1.4.5 Images of Text. (Level
AA)
1.4.6 Contrast (Enhanced).
(Level AAA)
1.4.7 Low or No Background
Audio. (Level AAA)
1.4.8 Visual Presentation.
(Level AAA)
• 7.2 paragraph two
• PDF3
addresses the meaningful
sequence of content.
• 7.17 addresses navigation
features.
• 7.18.3 addresses tab order
in annotations.
• 7.1, paragraphs 6 and 7 • General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrcontent-structureseparation-understanding
• 7.1, paragraph 6 • General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrvisual-audio-contrastwithout-color
• Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
• General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrvisual-audio-contrast-disaudio
• 7.1, paragraph 6 and note 4 • General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrvisual-audio-contrastcontrast
• Not applicable • G142
• 7.3, paragraph 6 • PDF7
• General Techniques:
hp://www.w3.org/WAI/
WCAG20/quickref/#qrvisual-audio-contrast-textpresentation
• 7.1, paragraph 6
• While ISO 14289 does
not address this success
criterion, conformance in
PDF requires ISO 14289
conforming les and
readers. e manner in
which developers support
this success criterion in
PDF in not dened in ISO
14289 or ISO 32000.
• Design-specic. It’s
necessary that authors
and developers consider
this provision and ensure
conformance.
26
Loading...