2013 Review of the Accessibility of the Portable Document Format for People with a Disability

Report prepared by Vision Australia for Department of Finance


Vision Australia contact details

Leona Zumbo
Digital Accessibility Consultant
P: 02 9334 3522
E: leona.zumbo@visionaustralia.org

Neil King

National Manager Digital Access
P: 02 9334 3547
M: 0438 511 761
E: neil.king@visionaustralia.org

Registered Office
Vision Australia
454 Glenferrie Road
Kooyong
Victoria 3144

Mailing Address
Vision Australia
4 Mitchell Street
Enfield
NSW 2136

ABN: 67 108 391 831
ACN: 108 391 831

Purpose

The Australian Government’s Web Accessibility National Transition Strategy (NTS) requires all Australian Government websites, and information published on them, to achieve conformance to World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines (WCAG) version 2.0 Level AA by the end of 2014. In relation to documents published in the Portable Document Format (PDF), the current practice to achieve compliance with the NTS is to provide an alternative WCAG 2.0i Level AA compliant version of the PDF, often produced as the authoritative document.

The position relating to the publication of documents in the Portable Document Format was influenced by the findings of the 2010 Australian Government’s study into the Accessibility of the Portable Document Format for people with a disability ii. The study looked at the accessibility of the Portable Document Format when accessed by commonly used assistive technologies in conjunction with the adaptive strategies used by people with a disability. The study identified there was insufficient evidence to prove that PDFs could conform to the WCAG 2.0 standard. The study concluded that “until further data is available on the characteristics of an accessible PDF file and there are Sufficient Techniques available to support the conformance of the PDF technology to WCAG 2.0, the Australian Government position recommending that alternative file formats be provided whenever PDF files are used should remain unchanged”. The Australian Human Rights Commission’s WWW Advisory Notesiii also recommended organisations “make the content available in at least one additional format and in a manner that incorporates principles of accessible document design”.

In January 2012, the W3C released “Sufficient Techniques for PDFiv” under WCAG 2.0. These techniques are supported with a comprehensive test suite of working examples. This means that PDF files are now able to be assessed for conformance against WCAG 2.0. In August 2012 PDF/UA was released as ISO Standard 14829-1v, which assists vendors creating PDF software and assistive technologies in applying the same set of technical principles in the development of their products and services.

In light of the release of the PDF Sufficient Techniques for WCAG 2.0 and PDF/UA as ISO standard 14829-1, the Australian Government Information Management Office (AGIMO)commissioned Digital Access at Vision Australia to review the technical capability of the most commonly used desktop and mobile screen readers in an Australian context against applicable WCAG 2.0 Success Criteria. For comparative purposes, the scope of the study remained the same as in 2010, with scanned PDF files, interactive forms, SmartForms, media rich content and dynamic content excluded from consideration.

The Australian Government recognises that the uptake of mobile devices has significantly increased since the 2010 study; for this reason the 2013 study was extended to include a review of the Portable Document Format when viewed on the iOS 7 and Android 4.3 Jelly Bean platforms.

The findings from this research are intended to inform the Australian Government in reviewing its policy position on the use of the Portable Document Format.

i World Wide Web Consortium, 2008, Web Content Accessibility Guidelines (WCAG) 2.0, viewed 3 July 2013, http://www.w3.org/TR/WCAG20/

ii Australian Government Information Management Office, 2010, Australian Government’s study into the Accessibility of the Portable Document Format for people with a disability, viewed 8 July 2013, http://www.finance.gov.au/publications/pdf-accessibility-study/

iii AHRC, World Wide Web Access: Disability Discrimination Act Advisory Notes ver 4.0 (2010), Viewed 4 November 2013, www.humanrights.gov.au/world-wide-web-access-disability-discrimination-act-advisory-notes-ver-40-2010#pdf

ivWorld Wide Web Consortium, 2013, PDF Techniques for WCAG 2.0, viewed 3 July 2013, http://www.w3.org/TR/WCAG20-TECHS/pdf.html

v SAI Global, 2012, ISO 14289-1:2012 Document management applications – Electronic document file format enhancement for accessibility – Part 1: Use of ISO 32000-1 (PDF/UA-1)

Summary

The objective of this review was to assess the technical capability of the most commonly used screen readers, in an Australian context, against the W3C documented techniques for the creation of WCAG 2.0 compliant PDF files. The 2010 test suite provided by Adobe did not cover all the relevant Success Criteria of WCAG 2.0. This review used the comprehensive WCAG 2.0 test suite that applies to all applicable Success Criteria, validating conformance by assessing each screen reader against the PDF test suite (example files). With the inclusion of these testable resources for WCAG 2.0, it can be determined if the Portable Document Format is an ‘Accessibility Supported Technologyvi’ in the Australian context.

The review identified four screen readers on the desktop and two on mobile platforms that, when used in conjunction with the leading PDF readers, accurately reflect the most common interaction preferences of the blind community in Australia; these are outlined in Table 1.

Table 1. Screen reader support for WCAG 2.0 PDF test suites in 2013
Screen ReaderEstimated UsageSufficientPartially SufficientNot Sufficient
JAWS 82% desktop use v.14    
NVDA 11% desktop use v.2013    
Window-Eyes 4% desktop use   v.8.2  
VoiceOver (Mac OS X) 3% desktop use     v.10.8
VoiceOver 99% mobile use     iOS v.7
TalkBack 1% mobile use     Android v.4.3

Table notes: Three levels are used to describe the technical capability of the screen readers against the PDF test suites: Sufficient: Provides technical capability that enables the assistive technology to interact with PDF files; Partially Sufficient: There are some technical capabilities using the assistive technology, but also potential issues that may impact upon the interaction with a PDF file; and Not Sufficient: Provides inadequate technical capability for the assistive technology to interact with PDF files as opposed to just accessing the text.

The desktop assessment identified that the current versions of JAWS and NVDA (combined market share of 92%) were able to comply with all WCAG 2.0 Success Criteria except ‘3.2.3 Consistent Navigation’. In the Portable Document Format headers and footers are rendered as artefacts with no associated tag, but as this information is available elsewhere in a document this would not ordinarily cause the end user any issue when interacting with a document. The level of WCAG 2.0 compliance when assessing the test suites with Window-Eyes with Adobe Reader, and VoiceOver with Preview was much lower, which reflects the situation reported in 2010.

The mobile assessment concluded that the support for the Portable Document Format by user agents on mobile devices is still far behind the support offered by their desktop equivalents.

The 2013 review also assessed the technical capabilities using the most commonly used or previous versions of the desktop four screen readers to identify if the support significantly differed. The previous and current versions displayed similar results, though support has positively increased in all of the current versions.

As the Adobe test suites used in the 2010 study did not provide a comprehensive assessment against applicable WCAG 2.0 Success Criteria, a direct comparison could not be made. However, the results from both the study and the review demonstrate a consistently high level of technical capability for the JAWS screen reader, and increased capability for the current version of NVDA.

vi http://www.w3.org/TR/WCAG20/#accessibility-supporteddef

Scope of review

In light of the release of the PDF Sufficient Techniques for WCAG 2.0 and PDF/UA as ISO standard 14829-1 conformance, the Australian Government required a review of the technical capability of the most commonly used desktop and mobile screen readers in the Australian context. The findings of this review are intended to inform the policy position on digital publishing formats – to determine if the Portable Document Format can be considered an accessibility supported technology. As the current position was reaffirmed with the findings of the 2010 study, it was imperative that the overall scope of review remained similar:

  • Assess the most commonly used user agents in an Australian context (screen readers and PDF readers) that support interaction on desktop based systems.
  • The PDF test suite must display the characteristics of a form, long document, short document and brochure ware document, and exclude dynamic functionality or media rich content. 

The Australian Government also recognises that the uptake of mobile and tablet devices has significantly increased since the 2010 study; as such the scope was expanded to include the two most popular viewers for portable devices in the review.

Screen Readers

Table 2. The following four desktop and two mobile screen readers were identified as the most commonly used screen readers in Australia as indicated by their estimated market share.
Screen ReaderVersionsPlatformEstimated Percentage of UsersEstimated number of Users*
JAWS 11 – 14 Desktop 82% 5,000
NVDA 2012 – 2013 Desktop 11% 700
Window-Eyes 7.5 – 8.2 Desktop 4% 250
VoiceOver (Mac OS X) 10.6 – 10.8 Desktop 3% 200
VoiceOver iOS 7 Mobile 99% 4,400
TalkBack Android 4.3 (Jelly Bean) Mobile 1% 30

Table notes: The number of users is an informed estimation and based upon statistical data. These numbers could be expected to underrepresent actual usage.

Operating System and Viewer Application

As in 2010, the WCAG 2.0 PDF test suits were viewed using the most commonly used PDF reader for the operating system.

Table 3. Test suite testing environment
Screen ReaderOperating SystemPDF Reader
JAWS 11 - 14 Windows 7 Adobe Reader XI
NVDA 2012 - 2013 Windows 7 Adobe Reader XI
Window-Eyes 7.5 - 8.2 Windows 7 Adobe Reader XI
VoiceOver 10.6 - 10.8 (Mac OS X) Snow Leopard (10.6) - Mountain Lion (10.8) Preview (10.6 - 10.8)
VoiceOver iOS 7 iBooks (iOS 7)
TalkBack Android 4.3 (Jelly Bean) Adobe Reader mobile 10.6.1

WCAG 2.0 Success Criteria

The objective of the study was to establish the technical capability, in the context of WCAG 2.0, for screen readers to interact with the Portable Document Format. Therefore, WCAG 2.0 Success Criteria were excluded from the study if their conformance requirement was satisfied by one of the behaviours below:

  • Adobe Reader UI: Controlled by the PDF reader user interface (UI)
  • Content: Capability exists, but a content issue controlled by the author of the document 
  • Media rich content: Out of scope
  • Dynamic content: Out of scope
  • Not Applicable: Does not apply to the Portable Document Format

19 of the 38 combined WCAG 2.0 Level A and AA Success Criteria were deemed ‘out of scope’ for the study as identified in Table 4.

Table 4. Status of WCAG 2.0 Success Criteria in test suite
WCAG 2.0 GuidelineStatusRational
1.1.1 Non-text Content Included Supported
1.2.1 Audio-only and Video-only (Prerecorded) Excluded Media rich content
1.2.2 Captions (Prerecorded) Excluded Media rich content
1.2.3 Audio Description or Media Alternative (Prerecorded) Excluded Media rich content
1.2.4 Captions (Live) Excluded Media rich content
1.2.5 Audio Description (Prerecorded) Excluded Media rich content
1.3.1 Info and Relationships Included Supported
1.3.2 Meaningful Sequence Included Supported
1.3.3 Sensory Characteristics Excluded Content
1.4.1 Use of Colour Excluded Content
1.4.2 Audio Control Excluded Content
1.4.3 Contrast (Minimum) Excluded Reader UI
1.4.4 Resize text Excluded Reader UI
1.4.5 Images of Text Included Supported
2.1.1 Keyboard Included Supported
2.1.2 No Keyboard TrapIncluded Included Supported
2.2.1 Timing Adjustable Excluded Dynamic content
2.2.2 Pause, Stop, Hide Excluded Dynamic content
2.3.1 Three Flashes or Below Threshold Excluded Dynamic content
2.4.1 Bypass Blocks Included Supported
2.4.2 Page Titled Included Supported
2.4.3 Focus Order Included Supported
2.4.4 Link Purpose (In Context) Included Supported
2.4.5 Multiple WaysIncluded Included Supported
2.4.6 Headings and Labels Excluded Content
2.4.7 Focus Visible Excluded Reader UI
3.1.1 Language of Page Included Supported
3.2.1 On Focus Excluded Dynamic content
3.1.2 Language of Parts Included Supported
3.2.2 On Input Included Supported
3.2.3 Consistent Navigation Included Supported
3.2.4 Consistent Identification Excluded Content
3.3.1 Error Identification Included Supported
3.3.2 Labels or Instructions Included Supported
3.3.3 Error Suggestion Included Supported
3.3.4 Error Prevention (Legal, Financial, Data) Excluded Dynamic content
4.1.1 Parsing Excluded Not Applicable
4.1.2 Name, Role, Value Included Supported

Methodology

Screen Reader Market Share

To determine the most commonly used screen readers from an Australian context, and the most commonly used versions thereof, two activities in line with the approach followed in the 2010 study were undertaken.

Vendors

Vendors of the screen readers included in the 2010 study were contacted to establish their estimations of current levels of use within Australia. The organisations that provided feedback were Quantum Technology (on behalf of Freedom Scientific), NV-Access, GW Micro and Apple.

As each vendor records different statistics (seats, licences, downloads, average number of users per day) or provides their products to market via different channels (multiple resellers, free downloadable licences – full or demo, bundled with operating system) a definitive answer as to the number of users cannot be determined for any screen reader. The vendors or their representatives provided estimation based upon the statistics1 available.

Vision Australia: Equipment Solutions

To further substantiate the statistics provided by the vendors the data was cross referenced with the number of enquiries received by Vision Australia’s Equipment Solutions help desk in relation to specific screen readers for the financial year 2012 - 20132.

Interviews with Equipment Solutions were also conducted to ascertain the most commonly used versions of each screen reader based upon their experiences as technology trainers and dealings with help desk enquiries.

Mobile Screen Reader Market Share

The Australian market share is based on statistics produced from Vision Australia’s Equipment Solutions department and international studies on mobile screen reader usage and smartphone penetration. These figures reflect market share for the usage of the screen readers only on portable devices rather than other functionality available to low vision users. The screen readers are used for general navigation purposes rather than for specifically accessing the Portable Document Format.

Vendors

Vendors could not approximate the number of screen reader users due to the functionality being built into the device (iPhone or Samsung Galaxy Nexus), i.e. the software is not a separate licence where downloads or purchases can be recorded.

Vision Australia: Equipment Solutions

To determine the most commonly used mobile screen readers from an Australian context, data from Vision Australia’s Equipment Solutions help desk was analysed to extract statistics on specific mobile screen reader enquiries for the financial year 2012 - 2013.

Statistical usage

Vision Australia used the following formula to approximate the Australian market share for mobile screen readers.

Total number of Australian users of screen readers (6,150) multiplied by the WebAIM National statisticvii on mobile screen reader usage (71.6 %)3.

Equals total number of Australian users of mobile screen readers (4,403).

To disseminate the total market into VoiceOver and TalkBack mobile screen reader users, Vision Australia used statistics extracted from the Equipment Solutions help desk database to calculate market share. The data was extracted for the financial year 2013.

Total number of enquiries regarding VoiceOver iOS (982) divided by the total number of enquiries regarding mobile screen readers (987) multiplied by 100.

Equals total percentage of VoiceOver iOS users in Australia (99.5%).

Total number of enquiries regarding TalkBack Android (5) divided by the total number of enquiries regarding mobile screen readers (987) multiplied by 100.

Equals total percentage of TalkBack Android users in Australia (0.5%).

Vision Australia’s subject matter experts suggest that the Android OS is preferred by low vision users due to its magnification capabilities rather than users that require screen reader capacity, hence the low adoption rate when compared to that of iOS. Android TalkBack has been included in the study as there is a small proportion of the Australian market currently using this mobile screen reader.

Technical Testing

The WCAG 2.0 PDF Sufficient Techniques and accompanying test suite was created by W3C members and validated by the W3C Web Accessibility Initiative (WAI). The test suite includes 20 example files that relate to screen readers4. The test suite maps to the 23 PDF Sufficient Techniques, replicating specific behaviours or elements of a PDF file that require testing. The test suite validates the successful application of each Sufficient Technique, supporting the conformance requirement of the related Success Criterion.

One General Sufficient Technique was also identified as applicable to the assessment of the Portable Document Format, and the test file reading-order.pdf was used to validate conformance; ‘2.1.2 No Keyboard Trap’.

The default settings for verbosity and keyboard commands were used for each of the assessments, unless otherwise directed by the Sufficient Technique.

The testing process replicated the methodology applied to the 2010 PDF study:

  • Test file opened in the accompanying PDF reader (Adobe Reader or Preview)
  • Screen reader attempts to satisfy the requirements of the Sufficient Technique using the test file
  • Outcome and screen reader behaviour are recorded

1 Refer to Appendix B Table 1.17 Statistics provided by screen reader vendors.

2 Refer to Appendix B Table 1.18 Statistics provided by Equipment Solutions Vision Australia.

3 Statistics sourced from Our Mobile Planet by Google ranks Australia as 6th on an international scale of smartphone market penetration. Therefore Vision Australia believes that the international figure of mobile screen reader usage is a fair representation of the Australian market.

4 Digital Access created new test files where that provided on the PDF Techniques for WCAG 2.0 website were not constructed according to its associated PDF sufficient technique. 7 out of 20 test files were updated and have been submitted to W3C.

vii WebAIM (Web Accessibility in Mind), 2012, Screen Reader Survey #4 Results, viewed 8 Nov 2013, http://webaim.org/projects/screenreadersurvey4/

Evidence

Of the 38 Success Criteria (25 Level A and 13 Level AA) only 19 were applicable to the scope of this study as the others are supported by factors not related to the Portable Document Format. For example, the provision of sufficient colour contrast (1.4.3 Contrast (Minimum)) is at the discretion of the author of the PDF file.

Table 5. Screen reader results against WCAG 2.0 Success Criteria
Screen ReaderVersionSupportedNot SupportedNot ApplicableTotal
JAWS 14 37 (18/19) 1 (1/19) 19 38
JAWS 11 36 (17/19) 2 (2/19) 19 38
NVDA 2013 37 (18/19) 1 (1/19) 19 38
NVDA 2012 36 (17/19) 2 (2/19) 19 38
Window-Eyes 8.2 30 (11/19) 8 (8/19) 19 38
Window-Eyes 7.5 30 (11/19) 8 (8/19) 19 38
VoiceOver (Mac OS X) 10.8 23 (4/19) 15 (15/19) 19 38
VoiceOver (Mac OS X) 10.6 23 (4/19) 15 (15/19) 19 38
VoiceOver (iOS) 7 23 (4/19) 15 (15/19) 19 38
TalkBack (Android) 4.3 Jelly Bean 0 (0/19) 19 (19/19) 19 38

Screen Reader Support for WCAG 2.0

All screen readers failed Success Criterion ‘3.2.3 Consistent Navigation’ as Adobe automatically renders headers and footers as an artefact. An artefact element is implemented into a PDF file without an associated tag and is therefore not detectable by current screen readers.

Note: In general, the information contained within a header and footer is also available from the title page of the document. Also, JAWS and NVDA announces the page numbers within the PDF therefore the impact of this issue on the end user is marginal.

JAWS 11-14

JAWS 11 demonstrated a high level of technical support against WCAG 2.0. All Success Criteria were satisfied with the exception of ‘1.3.2 Consistent Navigation’ and ‘1.3.1 Info and Relationships’ (36/38). When JAWS 11 was released the setting to detect structured table headers only, and so provide support for nested tables, was not implemented.

The ability to correctly detect nested table headers is supported in JAWS 14 and resulted in a very high level of technical support (37/38).

NVDA 2012 – 2013

NVDA 2012 provided support for all Success Criteria with the exception of ‘1.3.2 Consistent Navigation’ and ‘1.3.1 Info and Relationships’ (36/38). As NVDA 2012 does not detect table headers, there is no support for tables.

The ability to detect table headers is supported in NVDA 2013 and resulted in a very high level of technical support (37/38).

Window-Eyes 7.5 – 8.2

Window-Eyes only provided minimal technical support against core WCAG 2.0 Success Criteria (30/38).

The basic structure of the PDF is not announced by the screen reader. Specifically headings, lists, information about form labels and controls, and pagination are not detected. There is no support for bookmarks or a table of contents so no method to skip to different sections of the PDF document. A keyboard trap occurs when Window-Eyes does not anchor onto the document when forms mode is exited. The accent of a foreign language is also not announced.

Consequently, the following Success Criteria were not satisfied:

1.3.1 Info and Relationships

2.1.2 Keyboard Trap

2.4.1 Bypass Blocks

2.4.5 Multiple Ways

3.1.2 Language of Parts

3.2.3 Consistent Navigation

3.3.2 Labels and Instructions

4.1.2 Name, Role, Value

VoiceOver Mac OS X 10.6 – 10.8

VoiceOver provided poor technical support against core WCAG 2.0 Success Criteria (23/38).

Structural markup and tags are not identified when using VoiceOver with Preview leading to significant accessibility issues, including the inability of VoiceOver to read alternative descriptions for images or identify and enable navigation of headings and tables.

VoiceOver was also unable to access and interact with form elements correctly, identify error messages or identify the language of the whole document or sections within it.

This finding is consistent with the 2010 PDF study.

The following Success Criteria were not satisfied:

1.1.1 Non-text Content
1.3.1 Info and Relationships
2.1.1 Keyboard
2.4.1 Bypass Blocks
2.4.2 Page Titled
2.4.3 Focus Order
2.4.4 Link Purpose (In Context)
2.4.5 Multiple Ways
3.1.2 Language of Parts
3.2.2 On Input
3.2.3 Consistent Navigation
3.3.1 Error Identification
3.3.2 Language of Parts
3.3.3 Error Suggestion
4.1.2 Name, Role, Value

VoiceOver iOS 7

VoiceOver iOS 7 did not provide technical support against WCAG 2.0 (23/38).

VoiceOver iOS 7 provides the same level of support as its desktop equivalent (VoiceOver 10.6 - 10.8) with the exception of pagination.

The page numbering displayed in the PDF reader (iBooks) page controls do not match the page numbering of the document. For example, the document page numbering is “i”, “ii”, “iii”, “1”, and the page controls are displayed as “1”, “2”, “3”, “4”. Thus, VoiceOver iOS 7 announces the page controls as “1”, “2”, “3”, “4” rather than “i”, “ii”, “iii”, “1”.

VoiceOver iOS 7 fails the same Success Criteria as Voiceover Mac OS X 10.8.

TalkBack Android 4.3 Jelly Bean

TalkBack did not provide any technical support against WCAG 2.0 (0/38).

TalkBack did not recognise the PDF in Adobe Reader for mobile 10.6.1. The functions of Adobe Reader UI are announced as “button [number]”.

Findings

Table 6. Full test results against WCAG 2.0 Success Criteria and Test Suite for Desktop Screen Readers commonly used in Australia
WCAG 2.0 Success CriteriaTest FilePDF TechniqueJAWS 14JAWS 11NVDA 2013NVDA 2012Window-Eyes 8.2Window-Eyes 7.5Voice Over 10.8 (Mac OS X)Voice Over 10.6 (Mac OS X)Desired Results
1.1.1 alt-entry-to-an-image.pdf PDF 1: Applying text alternatives to images with the Alt entry in PDF documents Supported Supported Supported Supported Supported Supported Not Supported Not Supported Image alt must be read by speech AT
1.1.1 decorative-image.pdf PDF 4: Hiding decorative images with the Artefact tag in PDF documents Supported Supported Supported Supported Supported Supported Supported Supported No indication of the decorative image should be announced
1.3.1 table-example-repaired-new-test-file.pdf PDF 6: Using table elements for table markup in PDF Documents Supported Supported Supported Not Supported Supported Supported Not Supported Not Supported Name, value, and role is available for table
1.3.1 cooking.pdf PDF 9: Providing headings by marking content with heading tags in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Headings are identified by speech AT
1.3.1 form.pdf PDF 10: Providing labels for interactive form controls in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Text field controls are correctly identified by labels
1.3.1 links-new-test-file.pdf PDF 11: Providing links and link text using the /Link structure element in PDF documents Supported Supported Supported Supported Supported Supported Not Supported Not Supported Name, value, and role is available for links
1.3.1 form.pdf PDF 12: Providing name, role, value information for form fields in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Name, value, and role is available for form controls (text field and checkbox)
1.3.1 page-numbers.pdf PDF 17: Specifying consistent page numbering for PDF documents Supported Supported Supported Supported Not Supported Supported Not Supported Not Supported Pagination is identified in "Page Thumbnails"
1.3.1 table-new-test-file.pdf PDF 20: Using Adobe Acrobat Pro's Table Editor to repair mistagged tables Supported Not Supported Supported Not Supported Not Supported Not Supported Not Supported Not Supported Name, value, and role is available for nested table
1.3.1 lists.pdf PDF 21: Using List tags for lists in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Name, value, and role is available for lists
1.3.2 reading-order-2cols-word.pdf PDF 3: Ensuring correct tab and reading order in PDF documents Supported Supported Supported Supported Supported Supported Supported Supported Document is read in a logical order
1.4.5 ocr-example-tagged.pdf PDF 7: Performing OCR on a scanned PDF document to provide actual text Supported Supported Supported Supported Supported Supported Supported Supported Visually rendered text is presented in such a manner that it can be perceived without its visual presentation interfering with its readability
2.1.1 reading-order.pdf PDF 3: Ensuring correct tab and reading order in PDF documents Supported Supported Supported Supported Supported Supported Not Supported Not Supported Form controls  are keyboard accessible
2.1.1 links-new-test-file.pdf PDF 11: Providing links and link text using the /Link structure element in PDF documents Supported Supported Supported Supported Supported Supported Not Supported Not Supported Links controls  are keyboard accessible
2.1.1 form-fields-keybd.pdf PDF 23: Providing interactive form controls in PDF documents Supported Supported Supported Supported Supported Supported Not Supported Not Supported Form controls  are keyboard accessible
2.1.2 reading-order.pdf N/A Supported Supported Supported Supported Not Supported Not Supported Supported Supported No keyboard trap
2.4.1 cooking.pdf PDF 9: Providing headings by marking content with heading tags in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Headings allow skipping around within document
2.4.2 title-bar.pdf PDF 18: Specifying the document title using the Title entry in the document information dictionary of a PDF document Supported Supported Supported Supported Supported Supported Not Supported Not Supported PDF document is titled
2.4.3 reading-order.pdf PDF 3: Ensuring correct tab and reading order in PDF documents Supported Supported Supported Supported Supported Supported Not Supported Not Supported Document text and control order is correct when tabbing in sequential document
2.4.4 links-new-test-file.pdf PDF 11: Providing links and link text using the /Link structure element in PDF documents Supported Supported Supported Supported Supported Supported Not Supported Not Supported Name, value, and role is available for links
2.4.4 link-text-oo-new-test-file.pdf PDF 13: Providing replacement text using the /Alt entry for links in PDF documents Supported Supported Supported Supported Supported Supported Not Supported Not Supported Alternate text is detected for links
2.4.5 bookmarks.pdf PDF 2: Creating bookmarks in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Bookmarks allow skipping around via keyboard
3.1.1 language-en.pdf PDF 16: Setting the default language using the /Lang entry in the document catalog of a PDF document Supported Supported Supported Supported Supported Supported Supported Supported The language of the document is identified
3.1.2 lang-of-phrase-new-test-file.pdf PDF 19: Specifying the language for a passage or phrase with the Lang entry in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported The language of part of the document is identified
3.1.2 lang-of-phrase-new-test-file.pdf PDF 19: Specifying the language for a passage or phrase with the Lang entry in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported The language of part of the document is identified
3.2.2 submit-button-js-new-test-file.pdf PDF 15: Providing submit buttons with the submit-form action in PDF forms Supported Supported Supported Supported Supported Supported Not Supported Not Supported Name, value, and role is available for submit button
3.2.3 headers-footers-word.pdf PDF 14: Providing running headers and footers in PDF documents Not Supported Not Supported Not Supported Not Supported Not Supported Not Supported Not Supported Not Supported Header and Footer artefact is detected
3.2.3 page-numbers.pdf PDF 17: Specifying consistent page numbering for PDF documents Supported Supported Supported Supported Not Supported Not Supported Supported Not Supported Pagination is identified in "Page Thumbnails"
3.3.1 required-fields.pdf PDF 5: Indicating required form controls in PDF forms Supported Supported Supported Supported Supported Supported Not Supported Not Supported Error message telling users more than one required form field has not been entered is  detected
3.3.1 required-fields-new-test-file.pdf PDF 22: Indicating when user input falls outside the required format or values in PDF forms Supported Supported Supported Supported Supported Supported Not Supported Not Supported Input error is identified and automatically changed
3.3.2 required-fields.pdf PDF 5: Indicating required form controls in PDF forms Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Error message telling users more than one required form field has not been entered is  detected
3.3.2 form.pdf PDF 10: Providing labels for interactive form controls in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Text field controls are correctly identified by labels
3.3.3 required-fields.pdf PDF 5: Indicating required form controls in PDF forms Supported Supported Supported Supported Supported Supported Not Supported Not Supported Error message telling users more than one required form field has not been entered is  detected
3.3.3 required-fields-new-test-file.pdf PDF 22: Indicating when user input falls outside the required format or values in PDF forms Supported Supported Supported Supported Supported Supported Not Supported Not Supported Error message "Invalid date/time: Please ensure that the date time exists." is detected
4.1.2 form.pdf PDF 10: Providing labels for interactive form controls in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Name, value, and role is available for form controls (text field, checkbox and button)
4.1.2 form.pdf PDF 12: Providing name, role, value information for form fields in PDF documents Supported Supported Supported Supported Not Supported Not Supported Not Supported Not Supported Name, value, and role is available for form controls (text field and checkbox)
Table 7. Full test results against WCAG 2.0 Success Criteria and Test Suite for Mobile Screen Readers commonly used in Australia
WCAG 2.0Success CriteriaTest FilePDF TechniqueVoice Over 10.6 (iOS 7)TalkBack (Android 4.3)Desired Results
1.1.1 alt-entry-to-an-image.pdf PDF 1: Applying text alternatives to images with the Alt entry in PDF documents Not Supported Not Supported Image alt must be read by speech AT
1.1.1 decorative-image.pdf PDF 4: Hiding decorative images with the Artefact tag in PDF documents Supported Not Supported No indication of the decorative image should be announced
1.3.1 table-example-repaired-new-test-file.pdf PDF 6: Using table elements for table markup in PDF Documents Not Supported Not Supported Name, value, and role is available for table
1.3.1 cooking.pdf PDF 9: Providing headings by marking content with heading tags in PDF documents Not Supported Not Supported Headings are identified by speech AT
1.3.1 form.pdf PDF 10: Providing labels for interactive form controls in PDF documents Not Supported Not Supported Text field controls are correctly identified by labels
1.3.1 links-new-test-file.pdf PDF 11: Providing links and link text using the /Link structure element in PDF documents Not Supported Not Supported Name, value, and role is available for links
1.3.1 form.pdf PDF 12: Providing name, role, value information for form fields in PDF documents Not Supported Not Supported Name, value, and role is available for form controls (text field and checkbox)
1.3.1 page-numbers.pdf PDF 17: Specifying consistent page numbering for PDF documents Not Supported Not Supported Pagination is identified in "Page Thumbnails"
1.3.1 table-new-test-file.pdf PDF 20: Using Adobe Acrobat Pro's Table Editor to repair mistagged tables Not Supported Not Supported Name, value, and role is available for nested table
1.3.1 lists.pdf PDF 21: Using List tags for lists in PDF documents Not Supported Not Supported Name, value, and role is available for lists
1.3.2 reading-order-2cols-word.pdf PDF 3: Ensuring correct tab and reading order in PDF documents Supported Not Supported Document is read in a logical order
1.4.5 ocr-example-tagged.pdf PDF 7: Performing OCR on a scanned PDF document to provide actual text Supported Not Supported Visually rendered text is presented in such a manner that it can be perceived without its visual presentation interfering with its readability
2.1.1 reading-order.pdf PDF 3: Ensuring correct tab and reading order in PDF documents Not Supported Not Supported Form controls  are keyboard accessible
2.1.1 links-new-test-file.pdf PDF 11: Providing links and link text using the /Link structure element in PDF documents Not Supported Not Supported Links controls  are keyboard accessible
2.1.1 form-fields-keybd.pdf PDF 23: Providing interactive form controls in PDF documents Not Supported Not Supported Form controls  are keyboard accessible
2.1.2 reading-order.pdf N/A Supported Not Supported No keyboard trap
2.4.1 cooking.pdf PDF 9: Providing headings by marking content with heading tags in PDF documents Not Supported Not Supported Headings allow skipping around within document
2.4.2 title-bar.pdf PDF 18: Specifying the document title using the Title entry in the document information dictionary of a PDF document Not Supported Not Supported PDF document is titled
2.4.3 reading-order.pdf PDF 3: Ensuring correct tab and reading order in PDF documents Not Supported Not Supported Document text and control order is correct when tabbing in sequential document
2.4.4 links-new-test-file.pdf PDF 11: Providing links and link text using the /Link structure element in PDF documents Not Supported Not Supported Name, value, and role is available for links
2.4.4 link-text-oo-new-test-file.pdf PDF 13: Providing replacement text using the /Alt entry for links in PDF documents Not Supported Not Supported Alternate text is detected for links
2.4.5 bookmarks.pdf PDF 2: Creating bookmarks in PDF documents Not Supported Not Supported Bookmarks allow skipping around via keyboard
3.1.1 language-en.pdf PDF 16: Setting the default language using the /Lang entry in the document catalog of a PDF document Supported Not Supported The language of the document is identified
3.1.2 lang-of-phrase-new-test-file.pdf PDF 19: Specifying the language for a passage or phrase with the Lang entry in PDF documents Not Supported Not Supported The language of part of the document is identified
3.1.2 lang-of-phrase-new-test-file.pdf PDF 19: Specifying the language for a passage or phrase with the Lang entry in PDF documents Not Supported Not Supported The language of part of the document is identified
3.2.2 submit-button-js-new-test-file.pdf PDF 15: Providing submit buttons with the submit-form action in PDF forms Not Supported Not Supported Name, value, and role is available for submit button
3.2.3 headers-footers-word.pdf PDF 14: Providing running headers and footers in PDF documents Not Supported Not Supported Header and Footer artefact is detected
3.2.3 page-numbers.pdf PDF 17: Specifying consistent page numbering for PDF documents Not Supported Not Supported Pagination is identified in "Page Thumbnails"
3.3.1 required-fields.pdf PDF 5: Indicating required form controls in PDF forms Not Supported Not Supported Error message telling users more than one required form field has not been entered is  detected
3.3.1 required-fields-new-test-file.pdf PDF 22: Indicating when user input falls outside the required format or values in PDF forms Not Supported Not Supported Input error is identified and automatically changed
3.3.2 required-fields.pdf PDF 5: Indicating required form controls in PDF forms Not Supported Not Supported Error message telling users more than one required form field has not been entered is  detected
3.3.2 form.pdf PDF 10: Providing labels for interactive form controls in PDF documents Not Supported Not Supported Text field controls are correctly identified by labels
3.3.3 required-fields.pdf PDF 5: Indicating required form controls in PDF forms Not Supported Not Supported Error message telling users more than one required form field has not been entered is  detected
3.3.3 required-fields-new-test-file.pdf PDF 22: Indicating when user input falls outside the required format or values in PDF forms Not Supported Not Supported Error message "Invalid date/time: Please ensure that the date time exists." is detected
4.1.2 form.pdf PDF 10: Providing labels for interactive form controls in PDF documents Supported Not Supported Name, value, and role is available for form controls (text field, checkbox and button)
4.1.2 form.pdf PDF 12: Providing name, role, value information for form fields in PDF documents Not Supported Not Supported Name, value, and role is available for form controls (text field and checkbox)

Appendix A

Table 8. JAWS 14
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Pass As expected  
1.1.1 Non-text Content A PDF 4 Pass As expected  
1.3.1 Info and Relationships A PDF 6 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Pass As expected  
1.3.1 Info and Relationships A PDF 10 Pass As expected  
1.3.1 Info and Relationships A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Pass As expected  
1.3.1 Info and Relationships A PDF 17 Pass

JAWS reads all pages within Adobe Reader right panel as "i"

Page numbering can be accessed via “Go to page”

Ctrl + Shift + N

Passed as page numbering can be accessed via “Go to page”

Short-cut keystroke: Ctrl + Shift + N.
1.3.1 Info and Relationships A PDF 20 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 21 Pass As expected  
1.3.2 Meaningful Sequence A PDF 3 Pass As expected  
1.4.5 Images of text AA PDF 7 Pass As expected  
2.1.1 Keyboard A PDF 3 Pass As expected  
2.1.1 Keyboard A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Pass As expected  
2.1.2 No Keyboard Trap A N/A Pass As expected  
2.4.1 Bypass Blocks A PDF 9 Pass As expected  
2.4.2 Page Titled A PDF 18 Pass As expected  
2.4.3 Focus Order A PDF 3 Pass As expected  
2.4.4 Link Purpose (In Context) A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Pass As expected A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Pass

JAWS does not anchor to location selected in bookmark panel.

However, strictly against the WCAG 2.0 criteria this passes because:

The "Table of Contents" is supported

Search feature in JAWS and Reader
Fails PDF Sufficient Technique but passes WCAG 2.0 Success Criteria.
2.4.7 Focus Visible AA N/A Pass In standard and high contrast mode.  
3.1.1 Language of page A PDF 16 Pass

JAWS announces content as follows:

This is page "i"

This is page "ie"

This is page "ee"
 
3.1.1 Language of page A PDF 19 Pass As expected A new test file was created. Refer to Appendix C.
3.1.2 Language of parts AA PDF 19 Pass As expected A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Pass As expected A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Pass JAWS does not read headers and footers by simply using the down key and there is no hotkey to access this information within the "JAWS commands for Acrobat/Reader" dialog.

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag.

However, the information contained within this element is also available from the title page of the document. Also, JAWS 14 provides functionality to announce the page number. Therefore the impact of this issue on the end user is marginal.
3.2.3 Consistent Navigation AA PDF 17 Pass

JAWS reads all pages within Adobe Reader right panel as "i"

Page numbering can be accessed via "Go to page" Ctrl + Shift + N
 
3.3.1 Error Identification A PDF 5 Pass An error message telling users more than one required form field has not been entered appears and is detected by the screen reader.  
3.3.1 Error Identification A PDF 22 Pass As expected A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Pass An error message telling users more than one required form field has not been entered appears and is detected by the screen reader.  
3.3.2 Labels or Instructions A PDF 10 Pass As expected  
3.3.3 Error Suggestion AA PDF 5 Pass As expected  
3.3.3 Error Suggestion AA PDF 22 Pass As expected A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Pass As expected  
4.1.2 Name, Role, Value A PDF 12 Pass As expected  
Table 9. JAWS 11
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Pass As expected  
1.1.1 Non-text Content A PDF 4 Pass As expected  
1.3.1 Info and Relationships A PDF 6 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Pass As expected  
1.3.1 Info and Relationships A PDF 10 Pass As expected  
1.3.1 Info and Relationships A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Pass As expected  
1.3.1 Info and Relationships A PDF 17 Pass

JAWS reads all pages within Adobe Reader right panel as "i"

Page numbering can be accessed via “Go to page”

Ctrl + Shift + N

Passed as page numbering can be accessed via “Go to page”

Short-cut keystroke: Ctrl + Shift + N.
1.3.1 Info and Relationships A PDF 20 Fail

After JAWS announces "Results" it announces "Blank" only and focus is thrown back to the first table header, "Disability Category".

"Accuracy" and "Time to Complete" are eventually announced at the end of the table header repetition.
The screen reader does not read primary and secondary tables well.

A new test file was created. Refer to Appendix C.

The ability to detect structured table headers only is not supported in JAWS 11.
1.3.1 Info and Relationships A PDF 21 Pass As expected  
1.3.2 Meaningful Sequence A PDF 3 Pass As expected  
1.4.5 Images of text AA PDF 7 Pass As expected  
2.1.1 Keyboard A PDF 3 Pass As expected  
2.1.1 Keyboard A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Pass As expected  
2.1.2 No Keyboard Trap A N/A Pass As expected  
2.4.1 Bypass Blocks A PDF 9 Pass As expected  
2.4.2 Page Titled A PDF 18 Pass As expected  
2.4.3 Focus Order A PDF 3 Pass As expected  
2.4.4 Link Purpose (In Context) A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Pass As expected A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Pass

JAWS does not anchor to location selected in bookmark panel.

However strictly against the WCAG 2.0 criteria this passes because:

The "Table of Contents" is supported.

Search feature in JAWS and Reader
Fails PDF Sufficient Technique but passes WCAG 2.0 Success Criteria.
3.1.1 Language of page A PDF 16 Pass

JAWS announces content as follows:

This is page "i"

This is page "ie"

This is page "ee"
 
3.1.1 Language of page A PDF 19 Pass As expected  
3.1.2 Language of parts AA PDF 19 Pass As expected A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Pass As expected A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Fail JAWS does not read headers and footers by simply using the down key and there is no hotkey to access this information within the "JAWS commands for Acrobat/Reader" dialog.

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag.

However, the information contained within this element is also available from the title page of the document. Also, JAWS 11 provides functionality to announce the page number. Therefore the impact of this issue on the end user is marginal.
3.2.3 Consistent Navigation AA PDF 17 Pass

JAWS reads all pages within Adobe Reader right panel as "i"

Page numbering can be accessed via "Go to page" Ctrl + Shift + N
 
3.3.1 Error Identification A PDF 5 Pass An error message telling users more than one required form field has not been entered appears and is detected by the screen reader.  
3.3.1 Error Identification A PDF 22 Pass As expected A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Pass An error message telling users more than one required form field has not been entered appears and is detected by the screen reader.  
3.3.2 Labels or Instructions A PDF 10 Pass As expected  
3.3.3 Error Suggestion AA PDF 5 Pass An error message telling users more than one required form field has not been entered appears and is detected by the screen reader.  
3.3.3 Error Suggestion AA PDF 22 Pass As expected A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Pass As expected  
4.1.2 Name, Role, Value A PDF 12 Pass As expected  
Table 10. NVDA 2013
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Pass As expected  
1.1.1 Non-text Content A PDF 4 Pass As expected  
1.3.1 Info and Relationships A PDF 6 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Pass As expected  
1.3.1 Info and Relationships A PDF 10 Pass As expected  
1.3.1 Info and Relationships A PDF 11 Pass The system does not stop on the link within a paragraph. However, the links can be activated in "link list" mode. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Pass As expected  
1.3.1 Info and Relationships A PDF 17 Pass

NVDA does not announce the pages within the Adobe Acrobat left tool bar at all.

Go to page functionality is not available in NVDA 2013 and 2012.

Although when each page is read the page number is announced before the content. For example, "Page i" [Text] This is page i, "Page Roman 2" [Text] This is page Roman 2". The page numbering is consistent as required.

Note: You cannot use NVDA find to jump to the page (Ctrl + Insert + F)

Passed as page numbering is announced by the screen reader when each page is encountered.  The page numbering is consistent as required. 

1.3.1 Info and Relationships A PDF 20 Pass

As expected

A new test file was created. Refer to Appendix C.

1.3.1 Info and Relationships A PDF 21 Pass As expected  
1.3.2 Meaningful Sequence A PDF 3 Pass As expected  
1.4.5 Images of text AA PDF 7 Pass As expected  
2.1.1 Keyboard A PDF 3 Pass As expected  
2.1.1 Keyboard A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Pass As expected  
2.1.2 No Keyboard Trap A N/A Pass As expected  
2.4.1 Bypass Blocks A PDF 9 Pass As expected  
2.4.2 Page Titled A PDF 18 Pass As expected  
2.4.3 Focus Order A PDF 3 Pass As expected  
2.4.4 Link Purpose (In Context) A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Pass As expected A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Pass

NVDA anchors to content in main page when Bookmark is selected

 
3.1.1 Language of page A PDF 16 Pass

NVDA announces content as follows:

This is page "i"

This is page "Roman 2"

This is page "Roman 3"
 
3.1.1 Language of page A PDF 19 Pass Retested in new PDF test file. A new test file was created. Refer to Appendix C.
3.1.2 Language of parts AA PDF 19 Pass Retested in new PDF test file. A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Pass As expected A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Fail NVDA does not read headers and footers.

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag.

However, the information contained within this element is also available from the title page of the document. Also, NVDA 2013 announces the page number when each page is encountered. Therefore the impact of this issue on the end user is marginal.
3.2.3 Consistent Navigation AA PDF 17 Pass

As expected

 
3.3.1 Error Identification A PDF 5 Pass As expected  
3.3.1 Error Identification A PDF 22 Pass As expected A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Pass As expected  
3.3.2 Labels or Instructions A PDF 10 Pass As expected  
3.3.3 Error Suggestion AA PDF 5 Pass As expected  
3.3.3 Error Suggestion AA PDF 22 Pass As expected A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Pass As expected  
4.1.2 Name, Role, Value A PDF 12 Pass As expected  
Table 11. NVDA 2012
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Pass As expected  
1.1.1 Non-text Content A PDF 4 Pass As expected  
1.3.1 Info and Relationships A PDF 6 Pass Table headers are not associated with cell data when the hot key is selected. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Pass As expected  
1.3.1 Info and Relationships A PDF 10 Pass As expected  
1.3.1 Info and Relationships A PDF 11 Pass The system does not stop on the link within a paragraph. However, the links can be activated in "link list" mode. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Pass As expected  
1.3.1 Info and Relationships A PDF 17 Pass

NVDA does not announce the pages within the Adobe Acrobat left tool bar at all.

Go to page functionality is not available in NVDA 2013 and 2012.

Although when each page is read the page number is announced before the content. For example, "Page i" [Text] This is page i, "Page Roman 2" [Text] This is page Roman 2". The page numbering is consistent as required. 

Note: You cannot use NVDA find to jump to the page (Ctrl + Insert + F).

Passed as page numbering is announced by the screen reader when each page is encountered.  The page numbering is consistent as required. 

1.3.1 Info and Relationships A PDF 20 Fail

The headers are announced in a logical sequence however "Accuracy" is read as "Column 2 Row 1" and "Time to complete" is read as "Row 2". This means that the 'true' row 2 is read as row 3.

A new test file was created. Refer to Appendix C.

1.3.1 Info and Relationships A PDF 21 Pass As expected  
1.3.2 Meaningful Sequence A PDF 3 Pass As expected  
1.4.5 Images of text AA PDF 7 Pass As expected  
2.1.1 Keyboard A PDF 3 Pass As expected  
2.1.1 Keyboard A PDF 11 Pass The system does not stop on the link within a paragraph. However, the links can be activated in "link list" mode. A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Pass As expected  
2.1.2 No Keyboard Trap A N/A Pass NVDA + Space exits forms mode and user can exit the form.  
2.4.1 Bypass Blocks A PDF 9 Pass As expected  
2.4.2 Page Titled A PDF 18 Pass As expected  
2.4.3 Focus Order A PDF 3 Pass The focus order is correct.  
2.4.4 Link Purpose (In Context) A PDF 11 Pass The system does no stop on the link within a paragraph. However, the links can be activated in "link list" mode. A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Pass As expected A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Pass

NVDA anchors to content in main page when Bookmark is selected

 
3.1.1 Language of page A PDF 16 Pass

NVDA announces content as follows:

This is page "i"

This is page "Roman 2"

This is page "Roman 3"
Passed as page numbering is announced by the screen reader when each page is encountered.  The page numbering is consistent as required. 
3.1.1 Language of page A PDF 19 Pass Retested in new PDF test file. A new test file was created. Refer to Appendix C.
3.1.2 Language of parts AA PDF 19 Pass Retested in new PDF test file. A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Pass As expected A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Fail NVDA does not read headers and footers.

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag.

However, the information contained within this element is also available from the title page of the document. Also, NVDA 2013 announces the page number when each page is encountered. Therefore the impact of this issue on the end user is marginal.
3.2.3 Consistent Navigation AA PDF 17 Pass

As expected

 
3.3.1 Error Identification A PDF 5 Pass An error message telling users "more than one required form field has not been entered" appears and is detected by the screen reader.  
3.3.1 Error Identification A PDF 22 Pass As expected. Date automatically changes to required format. A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Pass An error message telling users "more than one required form field has not been entered" appears and is detected by the screen reader.  
3.3.2 Labels or Instructions A PDF 10 Pass As expected  
3.3.3 Error Suggestion AA PDF 5 Pass An error message telling users "more than one required form field has not been entered" appears and is detected by the screen reader.  
3.3.3 Error Suggestion AA PDF 22 Pass As expected. NVDA detects and reads the alert message "Invalid date/time: Please ensure that the date time exists." A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Pass As expected  
4.1.2 Name, Role, Value A PDF 12 Pass As expected  
Table 12. Window – Eyes 8.2
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Pass As expected  
1.1.1 Non-text Content A PDF 4 Pass As expected  
1.3.1 Info and Relationships A PDF 6 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Fail Headings are not detected by Window-Eyes.  
1.3.1 Info and Relationships A PDF 10 Fail All labels except for the "JAWS user" are detected. Form controls can be accessed once the Enter key has been pressed (forms mode in version 7.5). "Forms Interaction" (Control + Slash) does not allow the user to access the form controls. Form controls can only be accessed by selecting the "enter" key. This is entering "forms mode" in version 7.5.
1.3.1 Info and Relationships A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Fail Window-Eyes does not announce that the checkbox is checked once the user has selected the "space bar" and vice versa. Also, the tool tip assigned to the checkbox is not announced by the screen reader. The screen reader does announce that the checkbox is unchecked on initial focus.
1.3.1 Info and Relationships A PDF 17 Fail

Window-Eyes does not announce the page numbers in the left panel.

There is no "Go to page" functionality.

Page numbers are not announced when page is encountered.

 

1.3.1 Info and Relationships A PDF 20 Fail

Table headers are read in a logical manner. For example, "Results", "Accuracy", and "Time to Complete".

However the "Accuracy” and "Time to Complete" headers are ignored when the hotkey to hear the cell with its header is activated. Also the 2nd last column of data cells is read with the "Results" header only. The last column of data cells is read with no table header.
A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 21 Fail Lists are not detected by Window-Eyes  
1.3.2 Meaningful Sequence A PDF 3 Pass As expected  
1.4.5 Images of text AA PDF 7 Pass As expected  
2.1.1 Keyboard A PDF 3 Pass As expected  
2.1.1 Keyboard A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Pass As expected  
2.1.2 No Keyboard Trap A N/A Fail Once "forms mode (version 7.5)" has been inactivated (by pressing the enter key) the system does not detect the document. "Forms mode" is not required when interacting with a form within a website.  More info: Keyboard trap occurs in reading-order.pdf. User should be able to toggle "forms mode" to exit the form and read the rest of the document. The user cannot read the rest of the document.
2.4.1 Bypass Blocks A PDF 9 Fail Window-Eyes 8.2 does not detect heading structure.  
2.4.2 Page Titled A PDF 18 Pass As expected  
2.4.3 Focus Order A PDF 3 Pass As expected  
2.4.4 Link Purpose (In Context) A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Pass As expected A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Fail

The table of content links are read with the (…….) as "period", one at a time. The user would have to hear a lot of the term "period" before they reach the page number.

When a link in the table of contents is selected it does not anchor to the appropriate place in the document. Instead on selecting the down key the next link within the table of contents is read.

The screen reader does not anchor to the bookmark location once F6 takes the user back to the main page.
 
3.1.1 Language of page A PDF 16 Pass

Window-Eyes announces content as follows:

This is page "i"

This is page "ie"

This is page "ee"
 
3.1.1 Language of page A PDF 19 Fail Window-Eyes does not announce a Spanish accent. A new test file was created. Refer to Appendix C.
3.1.2 Language of parts AA PDF 19 Fail Window-Eyes does not announce a Spanish accent. A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Pass As expected A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Fail Window-Eyes does not read headers and footers.

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag. 

3.2.3 Consistent Navigation AA PDF 17 Fail

Window-Eyes does not announce the page numbers in the left panel. There is no "Go to page" functionality.

 
3.3.1 Error Identification A PDF 5 Pass An error message telling users "more than one required form field has not been entered" appears and is detected by the screen reader.  
3.3.1 Error Identification A PDF 22 Pass As expected. A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Fail Window-Eyes does not announce that the checkbox is checked once the user has selected the "space bar" and vice versa. Also, the tool tip assigned to the checkbox is not announced by the screen reader.  
3.3.2 Labels or Instructions A PDF 10 Fail The label for the checkbox "JAWS user" is not detected.  
3.3.3 Error Suggestion AA PDF 5 Pass An error message telling users "more than one required form field has not been entered" appears and is detected by the screen reader.  
3.3.3 Error Suggestion AA PDF 22 Pass Form field auto corrects as expected. A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Fail Window-Eyes does not announce that the checkbox is checked once the user has selected the "space bar" and vice versa. Also, the tool tip assigned to the checkbox is not announced by the screen reader.  
4.1.2 Name, Role, Value A PDF 12 Fail Window-Eyes does not announce that the checkbox is checked once the user has selected the "space bar" and vice versa. Also, the tool tip assigned to the checkbox is not announced by the screen reader.  
Table 13. Window – Eyes 7.5
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Pass As expected  
1.1.1 Non-text Content A PDF 4 Pass As expected  
1.3.1 Info and Relationships A PDF 6 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Fail Headings are not detected by Window-Eyes.  
1.3.1 Info and Relationships A PDF 10 Fail Checkbox tool tip is not detected. Current state of checkbox is announced initially however after checkbox is checked the screen reader does not announce checkbox current state. All labels except for the "JAWS user" are detected. Form controls can be accessed once the Enter key has been pressed (forms mode in version 7.5). "Forms Interaction" (Control + Slash) does not allow the user to access the form controls.
1.3.1 Info and Relationships A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Fail Checkbox tool tip is not detected. Current state of checkbox is announced initially however after checkbox is checked the screen reader does not announce checkbox current state.  
1.3.1 Info and Relationships A PDF 17 Fail

Window-Eyes does not announce the page numbers in the left panel.

There is no "Go to page" functionality.

Page numbers are not announced when page is encountered.

 

1.3.1 Info and Relationships A PDF 20 Fail

Table headers are read without any redundant content and in a logical manner. For example, "Results", "Accuracy", and "Time to Complete". However the "Accuracy” and "Time to Complete" headers are ignored when the hotkey to hear the cell with its header is activated. Also the 2nd last column of data cells is read with the "Results" header only. The last column of data cells is read with no header.

A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 21 Fail Lists are not detected by Window-Eyes  
1.3.2 Meaningful Sequence A PDF 3 Pass As expected  
1.4.5 Images of text AA PDF 7 Pass As expected  
2.1.1 Keyboard A PDF 3 Pass As expected  
2.1.1 Keyboard A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Pass Form is keyboard accessible.  
2.1.2 No Keyboard Trap A N/A Fail Once "forms mode (version 7.5)" has been inactivated (by pressing the enter key) the system does not detect the document. "Forms mode" is not required when interacting with a form within a website.  More info: Keyboard trap occurs in reading-order.pdf. User should be able to toggle "forms mode" to exit the form and read the rest of the document. The user cannot read the rest of the document.
2.4.1 Bypass Blocks A PDF 9 Fail Headings are not detected by Window-Eyes.  
2.4.2 Page Titled A PDF 18 Pass As expected  
2.4.3 Focus Order A PDF 3 Pass As expected  
2.4.4 Link Purpose (In Context) A PDF 11 Pass As expected A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Pass As expected A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Fail

The table of content links are read with the (…….) as "period", one at a time. The user would have to hear a lot of the term "period" before they reach the page number.

Bookmarks are accessible however the screen reader reads the page title "Bookmarks.pdf-Adobe Reader" over and over again unless the user selects the down key. Then it will announce the bookmark for example, "Header Four" and start reading the page title "Bookmarks.pdf-Adobe Reader" over and over again until the next book mark is selected etc.

Links within the "Table of Contents" do not activate.

The bookmark is visually anchored to however when the screen reader anchors back to the document it reads from the top of the page not from where the bookmark has been selected.
 
3.1.1 Language of page A PDF 16 Pass

Window-Eyes announces content as follows:

This is page "i"

This is page "ie"

This is page "ee"
 
3.1.1 Language of page A PDF 19 Fail Window-Eyes does not announce a Spanish accent. A new test file was created. Refer to Appendix C.
3.1.2 Language of parts AA PDF 19 Fail Window-Eyes does not announce a Spanish accent. A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Pass As expected A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Fail Window-Eyes does not read headers and footers.

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag. 

3.2.3 Consistent Navigation AA PDF 17 Fail

Window-Eyes does not announce the page numbers in the left panel. There is no "Go to page" functionality.

 
3.3.1 Error Identification A PDF 5 Pass As expected.  
3.3.1 Error Identification A PDF 22 Pass As expected. A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Fail Checkbox tool tip is not detected. Current state of checkbox is announced initially however after checkbox is checked the screen reader does not announce checkbox current state.  
3.3.2 Labels or Instructions A PDF 10 Fail Checkbox tool tip is not detected. Current state of checkbox is announced initially however after checkbox is checked the screen reader does not announce checkbox current state.  
3.3.3 Error Suggestion AA PDF 5 Pass As expected  
3.3.3 Error Suggestion AA PDF 22 Pass As expected A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Fail Checkbox tool tip is not detected. Current state of checkbox is announced initially however after checkbox is checked the screen reader does not announce checkbox current state.  
4.1.2 Name, Role, Value A PDF 12 Fail Checkbox tool tip is not detected. Current state of checkbox is announced initially however after checkbox is checked the screen reader does not announce checkbox current state.  
Table 14. VoiceOver 10.8
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Fail VoiceOver does not detect the image.  
1.1.1 Non-text Content A PDF 4 Pass As expected  
1.3.1 Info and Relationships A PDF 6 Fail Table structure is not detected. All cells and header data is read as plain text. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Fail Headings structure is not detected. All text read as plain text.  
1.3.1 Info and Relationships A PDF 10 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore there is no tooltip. The textual labels are read as plain text.  
1.3.1 Info and Relationships A PDF 11 Fail Link structure is not detected. All text is announced as plain text. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore name, role, value are not detected by VoiceOver.  
1.3.1 Info and Relationships A PDF 17 Pass

VoiceOver reads the same page numbering in the viewer page controls as in the document.

 

1.3.1 Info and Relationships A PDF 20 Fail

Table not detected by VoiceOver. "Table not found". Header content announced in illogical order. "Results", "Ballots", "Incomplete/", "Terminated", "Disability", Category".

A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 21 Fail List structure is not detected by VoiceOver.  
1.3.2 Meaningful Sequence A PDF 3 Pass As expected  
1.4.5 Images of text AA PDF 7 Pass As expected  
2.1.1 Keyboard A PDF 3 Fail Textboxes do not render in preview. The cursor cannot anchor on the section read as "underline, underline, underline".  
2.1.1 Keyboard A PDF 11 Fail Link structure is not detected by VoiceOver. A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Fail Form controls do not render in preview. The cursor cannot anchor on the section read as "underline, underline, underline". Checkbox is not anchored on, detected or announced by screen reader.  
2.1.2 No Keyboard Trap A N/A Pass As expected  
2.4.1 Bypass Blocks A PDF 9 Fail VoiceOver does not detect headings.  
2.4.2 Page Titled A PDF 18 Fail Title is rendered and read as "ZqVsOL-title-bar.pdf"  
2.4.3 Focus Order A PDF 3 Fail Textboxes do not render in preview. The cursor cannot anchor on the section read as "underline, underline, underline". Therefore "Focus Order" cannot be tested.  
2.4.4 Link Purpose (In Context) A PDF 11 Fail Link structure is not detected by VoiceOver. A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Fail Alternate text for link is not announced. A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Fail

Voiceover does not anchor to the bookmark selected in Previews "Table of Contents" when the user toggles from the right panel to the main document.

 
3.1.1 Language of page A PDF 16 Pass

VoiceOver reads as:

This is page "i"

This is page "i, i"

This is page "i, i, i"
 
3.1.1 Language of page A PDF 19 Fail VoiceOver does not announce Spanish accent. A new test file was created. Refer to Appendix C.
3.1.2 Language of parts AA PDF 19 Fail VoiceOver does not announce Spanish accent. A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Fail VoiceOver does not detect the button at all. A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Fail Headers and footer text is detected as plain text. The header and footer structure is not communicated to the user. 

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag. 

3.2.3 Consistent Navigation AA PDF 17 Pass

VoiceOver reads the same page numbering in the viewer page controls as in the document.

 
3.3.1 Error Identification A PDF 5 Fail Submit button is not anchored to, detected, or announced by VoiceOver. Error message cannot be activated.  
3.3.1 Error Identification A PDF 22 Fail Form controls are not rendered or detected by VoiceOver in preview. Therefore users cannot access the form controls. A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore there is no tooltip. The textual labels are read as plain text.  
3.3.2 Labels or Instructions A PDF 10 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore there is no tooltip. The textual labels are read as plain text.  
3.3.3 Error Suggestion AA PDF 5 Fail Form controls are not rendered or detected by VoiceOver in preview. Therefore users cannot access the form controls.  
3.3.3 Error Suggestion AA PDF 22 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore users cannot access the form controls. A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore name, role, value are not detected by VoiceOver.  
4.1.2 Name, Role, Value A PDF 12 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore name, role, value are not detected by VoiceOver.  
Table 15. VoiceOver 10.6
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Fail VoiceOver does not detect the image.  
1.1.1 Non-text Content A PDF 4 Pass As expected  
1.3.1 Info and Relationships A PDF 6 Fail Table structure is not detected. All cells and header data is read as plain text. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Fail Headings structure is not detected. All text read as plain text.  
1.3.1 Info and Relationships A PDF 10 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore there is no tooltip. The textual labels are read as plain text.  
1.3.1 Info and Relationships A PDF 11 Fail Link structure is not detected. All text is announced as plain text. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore name, role, value are not detected by VoiceOver.  
1.3.1 Info and Relationships A PDF 17 Fail

VoiceOver reads page "i" as page-numbers.pdf image one of four

"ii" is read as two image two of four

"iii" is read as three image three of four

 

1.3.1 Info and Relationships A PDF 20 Fail

Table not detected by VoiceOver. "Table not found". Header content announced in illogical order.

A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 21 Fail List structure is not detected by VoiceOver.  
1.3.2 Meaningful Sequence A PDF 3 Pass As expected  
1.4.5 Images of text AA PDF 7 Pass As expected  
2.1.1 Keyboard A PDF 3 Fail Textboxes do not render in preview. The cursor cannot anchor on the section read as "underline, underline, underline".  
2.1.1 Keyboard A PDF 11 Fail Link structure is not detected by VoiceOver. A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Fail Form controls do not render in preview. The cursor cannot anchor on the section read as "underline, underline, underline". Checkbox is not anchored on, detected or announced by screen reader.  
2.1.2 No Keyboard Trap A N/A Pass As expected  
2.4.1 Bypass Blocks A PDF 9 Fail VoiceOver does not detect headings.  
2.4.2 Page Titled A PDF 18 Fail Title is rendered and read as "title-bar.pdf"  
2.4.3 Focus Order A PDF 3 Fail Textboxes do not render in preview. The cursor cannot anchor on the section read as "underline, underline, underline". Therefore "Focus Order" cannot be tested.  
2.4.4 Link Purpose (In Context) A PDF 11 Fail Link structure is not detected by VoiceOver. A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Fail Alternate text for link is not announced. A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Fail

The system does not anchor to the bookmark selected in Previews "bookmarks" when VoiceOver toggles from the right panel to the main document.

 
3.1.1 Language of page A PDF 16 Pass

VoiceOver reads as:

This is page "i"

This is page "two"

This is page "three"
 
3.1.1 Language of page A PDF 19 Fail VoiceOver does not read in Spanish accent. A new test file was created. Refer to Appendix C.
3.1.2 Language of parts AA PDF 19 Fail VoiceOver does not read in Spanish accent. A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Fail VoiceOver does not detect the button at all. A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Fail Headers and footer text is detected as plain text. The header and footer structure is not communicated to the user. 

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag.

3.2.3 Consistent Navigation AA PDF 17 Fail

VoiceOver reads viewer page controls as:

"language-en.pdf image one of four"

"two image two of four"

"three image three of four"

"one image four of four"
 
3.3.1 Error Identification A PDF 5 Fail Submit button is not anchored to, detected, or announced by VoiceOver. Error message cannot be activated.  
3.3.1 Error Identification A PDF 22 Fail Form controls are not rendered or detected by VoiceOver in preview. Therefore users cannot access the form controls. A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore there is no tooltip. The textual labels are read as plain text.  
3.3.2 Labels or Instructions A PDF 10 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore there is no tooltip. The textual labels are read as plain text.  
3.3.3 Error Suggestion AA PDF 5 Fail Form controls are not rendered or detected by VoiceOver in preview. Therefore users cannot access the form controls.  
3.3.3 Error Suggestion AA PDF 22 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore users cannot access the form controls. A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore name, role, value are not detected by VoiceOver.  
4.1.2 Name, Role, Value A PDF 12 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore name, role, value are not detected by VoiceOver.  
Table 16. VoiceOver iOS 7
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Fail VoiceOver does not detect the image.  
1.1.1 Non-text Content A PDF 4 Pass As expected  
1.3.1 Info and Relationships A PDF 6 Fail Table structure is not detected. All cells and header data is read as plain text. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Fail Headings structure is not detected. All text read as plain text.  
1.3.1 Info and Relationships A PDF 10 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore there is no tooltip. The textual labels are read as plain text.  
1.3.1 Info and Relationships A PDF 11 Fail Link structure is not detected. All text is announced as plain text. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore name, role, value are not detected by VoiceOver.  
1.3.1 Info and Relationships A PDF 17 Fail

When navigating through the document using “two finger swipe down” VoiceOver reads :
page "i" as page “i”
page "ii" is read as page “ii”
page "iii" is read as page “ii”
page “1”  is read as page “1”
However when the “Page User” is used to navigate pages within the document VoiceOver reads:
page "i" as page “1”
page "ii" is read as page “2”
page "iii" is read as page “3”
page “1”  is read as page “4”

 

1.3.1 Info and Relationships A PDF 20 Fail

Table not detected by VoiceOver. "Table not found". Header content announced in illogical order.

A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 21 Fail List structure is not detected by VoiceOver.  
1.3.2 Meaningful Sequence A PDF 3 Pass As expected  
1.4.5 Images of text AA PDF 7 Pass As expected  
2.1.1 Keyboard A PDF 3 Fail Textboxes do not render in preview. The cursor cannot anchor on the section read as "underline, underline, underline".  
2.1.1 Keyboard A PDF 11 Fail Link structure is not detected by VoiceOver. A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Fail Form controls do not render in preview. The cursor cannot anchor on the section read as "underline, underline, underline". Checkbox is not anchored on, detected or announced by screen reader.  
2.1.2 No Keyboard Trap A N/A Pass As expected  
2.4.1 Bypass Blocks A PDF 9 Fail VoiceOver does not detect headings.  
2.4.2 Page Titled A PDF 18 Fail Title is rendered and read as "title-bar.pdf"  
2.4.3 Focus Order A PDF 3 Fail Textboxes do not render in preview. The cursor cannot anchor on the section read as "underline, underline, underline". Therefore "Focus Order" cannot be tested.  
2.4.4 Link Purpose (In Context) A PDF 11 Fail Link structure is not detected by VoiceOver. A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Fail Alternate text for link is not announced. A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Fail

The system does not detect any bookmarks.

 
3.1.1 Language of page A PDF 16 Pass

VoiceOver reads as:
This is page "i"
This is page "ii"
This is page "iii"

 
3.1.1 Language of page A PDF 19 Fail VoiceOver does not read in Spanish accent. A new test file was created. Refer to Appendix C.
3.1.2 Language of parts AA PDF 19 Fail VoiceOver does not read in Spanish accent. A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Fail Submit button is not rendered. A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Fail Headers and footer text is detected as plain text. The header and footer structure is not communicated to the user. 

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag.

3.2.3 Consistent Navigation AA PDF 17 Fail

When navigating through the document using “two finger swipe down” VoiceOver reads :
page "i" as page “i”
page "ii" is read as page “ii”
page "iii" is read as page “ii”
page “1”  is read as page “1”
However when the “Page User” is used to navigate pages within the document VoiceOver reads:
page "i" as page “1”
page "ii" is read as page “2”
page "iii" is read as page “3”
page “1”  is read as page “4”

 
3.3.1 Error Identification A PDF 5 Fail Submit button is not rendered.  
3.3.1 Error Identification A PDF 22 Fail Form controls are not rendered or detected by VoiceOver in preview. Therefore users cannot access the form controls. A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore there is no tooltip. The textual labels are read as plain text.  
3.3.2 Labels or Instructions A PDF 10 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore there is no tooltip. The textual labels are read as plain text.  
3.3.3 Error Suggestion AA PDF 5 Fail Form controls are not rendered or detected by VoiceOver in preview. Therefore users cannot access the form controls.  
3.3.3 Error Suggestion AA PDF 22 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore users cannot access the form controls. A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore name, role, value are not detected by VoiceOver.  
4.1.2 Name, Role, Value A PDF 12 Fail Form controls are not rendered or detected by VoiceOver in preview.  Therefore name, role, value are not detected by VoiceOver.  
Table 17. TalkBack Android 4.3 (Jelly Bean)
Success CritLeveleriaLevelTechniquesPass / FailBehaviourComments
1.1.1 Non-text Content A PDF 1 Fail PDF is inaccessible. No element is detected.  
1.1.1 Non-text Content A PDF 4 Fail PDF is inaccessible. No element is detected.  
1.3.1 Info and Relationships A PDF 6 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 9 Fail PDF is inaccessible. No element is detected.  
1.3.1 Info and Relationships A PDF 10 Fail PDF is inaccessible. No element is detected.  
1.3.1 Info and Relationships A PDF 11 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 12 Fail PDF is inaccessible. No element is detected.  
1.3.1 Info and Relationships A PDF 17 Fail PDF is inaccessible. No element is detected.

 

1.3.1 Info and Relationships A PDF 20 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
1.3.1 Info and Relationships A PDF 21 Fail PDF is inaccessible. No element is detected.  
1.3.2 Meaningful Sequence A PDF 3 Fail PDF is inaccessible. No element is detected.  
1.4.5 Images of text AA PDF 7 Fail PDF is inaccessible. No element is detected.  
2.1.1 Keyboard A PDF 3 Fail PDF is inaccessible. No element is detected.  
2.1.1 Keyboard A PDF 11 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
2.1.1 Keyboard A PDF 23 Fail PDF is inaccessible. No element is detected.  
2.1.2 No Keyboard Trap A N/A Fail PDF is inaccessible. No element is detected.  
2.4.1 Bypass Blocks A PDF 9 Fail PDF is inaccessible. No element is detected.  
2.4.2 Page Titled A PDF 18 Fail PDF is inaccessible. No element is detected.  
2.4.3 Focus Order A PDF 3 Fail PDF is inaccessible. No element is detected.  
2.4.4 Link Purpose (In Context) A PDF 11 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
2.4.4 Link Purpose (In Context) A PDF 13 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
2.4.5 Multiple ways AA PDF 2 Fail PDF is inaccessible. No element is detected.  
3.1.1 Language of page A PDF 16 Fail PDF is inaccessible. No element is detected.  
3.1.1 Language of page A PDF 19 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
3.1.2 Language of parts AA PDF 19 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
3.2.2 On Input A PDF 15 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
3.2.3 Consistent Navigation AA PDF14 Fail PDF is inaccessible. No element is detected.

Headers and footers are automatically implemented as an Artifact by Adobe. Thus the element has no tag.

3.2.3 Consistent Navigation AA PDF 17 Fail PDF is inaccessible. No element is detected.  
3.3.1 Error Identification A PDF 5 Fail PDF is inaccessible. No element is detected.  
3.3.1 Error Identification A PDF 22 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
3.3.2 Labels or Instructions A PDF 5 Fail PDF is inaccessible. No element is detected.  
3.3.2 Labels or Instructions A PDF 10 Fail PDF is inaccessible. No element is detected.  
3.3.3 Error Suggestion AA PDF 5 Fail PDF is inaccessible. No element is detected.  
3.3.3 Error Suggestion AA PDF 22 Fail PDF is inaccessible. No element is detected. A new test file was created. Refer to Appendix C.
4.1.2 Name, Role, Value A PDF 10 Fail PDF is inaccessible. No element is detected.  
4.1.2 Name, Role, Value A PDF 12 Fail PDF is inaccessible. No element is detected.  

Appendix B

Table 18. Statistics provided by screen reader vendors
VendorScreen ReaderLicenses / Seats or Downloads
Freedom Scientific JAWS 11 - 14

Approximately 5000 – 6000 seats

Note: numerous ‘seats’ are provided by multi user licenses.
NV Access NVDA 2012 - 2013

On average 169 Australians using NVDA daily. 838 downloads of the latest release from Australia.

Note: this number does not discount multiple downloads and doesn't account for anyone who got the software via another means.
GM Micro Window Eyes 7.5 – 8.2 GW Micro could not provide the number of Window-Eyes copies in use.
Apple VoiceOver 10.6 – 10.8 There is no public information available as VoiceOver is a built in system feature. I.e. It is difficult to know whether or not an individual turns VoiceOver on and uses it.
Apple VoiceOver iOS There is no public information available as VoiceOver is a built in system feature. I.e. It is difficult to know whether or not an individual turns VoiceOver on and uses it.
Eyes-Free Google TalkBack Android There is no public information available as TalkBack is a built in system feature. I.e. It is difficult to know whether or not an individual turns TalkBack on and uses it.
Table 19. Statistics provided by Equipment Solutions Vision Australia
Screen ReaderEnquiries in FY13
JAWS 11 - 14 451
NVDA 2012 - 2013 173
Window Eyes 7.5 – 8.2 21
VoiceOver 10.6 – 10.8 Mac OS X 53
VoiceOver iOS 982
TalkBack Android 4

Appendix C

Table 20. Test Files used per WCAG 2.0 Success Criteria and PDF Technique.
Success CriteriaLevelTechniquesFilenameTest File Created by W3C or Vision Australia
1.1.1 Non-text Content A PDF 1 alt-entry-to-an-image.pdf W3C
1.1.1 Non-text Content A PDF 4 decorative-image.pdf W3C
1.3.1 Info and Relationships A PDF 6 table-example-repaired-new-test-file.pdf Vision Australia
1.3.1 Info and Relationships A PDF 9 cooking.pdf W3C
1.3.1 Info and Relationships A PDF 10 form.pdf W3C
1.3.1 Info and Relationships A PDF 11 links-new-test-file.pdf Vision Australia
1.3.1 Info and Relationships A PDF 12 form.pdf W3C
1.3.1 Info and Relationships A PDF 17 page-numbers.pdf W3C
1.3.1 Info and Relationships A PDF 20 table-new-test-file.pdf Vision Australia
1.3.1 Info and Relationships A PDF 21 lists.pdf W3C
1.3.2 Meaningful Sequence A PDF 3 reading-order-2cols-word.pdf W3C
1.4.5 Images of text AA PDF 7 ocr-example-tagged.pdf W3C
2.1.1 Keyboard A PDF 3 reading-order.pdf W3C
2.1.1 Keyboard A PDF 11 links-new-test-file.pdf Vision Australia
2.1.1 Keyboard A PDF 23 form-fields-keybd.pdf W3C
2.1.2 No Keyboard Trap A N/A reading-order.pdf W3C
2.4.1 Bypass Blocks A PDF 9 cooking.pdf W3C
2.4.2 Page Titled A PDF 18 title-bar.pdf W3C
2.4.3 Focus Order A PDF 3 reading-order.pdf W3C
2.4.4 Link Purpose (In Context) A PDF 11 links-new-test-file.pdf Vision Australia
2.4.4 Link Purpose (In Context) A PDF 13 link-text-oo-new-test-file.pdf Vision Australia
2.4.5 Multiple ways AA PDF 2 bookmarks.pdf W3C
3.1.1 Language of page A PDF 16 language-en.pdf W3C
3.1.1 Language of page A PDF 19 lang-of-phrase-new-test-file.pdf Vision Australia
3.1.2 Language of parts AA PDF 19 lang-of-phrase-new-test-file.pdf Vision Australia
3.2.2 On Input A PDF 15 submit-button-js-new-test-file.pdf Vision Australia
3.2.3 Consistent Navigation AA PDF 14 headers-footers-word.pdf W3C
3.2.3 Consistent Navigation AA PDF 17 page-numbers.pdf W3C
3.3.1 Error Identification A PDF 5 required-fields.pdf W3C
3.3.1 Error Identification A PDF 22 required-fields-new-test-file.pdf Vision Australia
3.3.2 Labels or Instructions A PDF 5 required-fields.pdf W3C
3.3.2 Labels or Instructions A PDF 10 form.pdf W3C
3.3.3 Error Suggestion A PDF 5 required-fields.pdf W3C
3.3.3 Error Suggestion A PDF 22 required-fields-new-test-file.pdf Vision Australia
4.1.2 Name, Role, Value A PDF 10 form.pdf W3C
4.1.2 Name, Role, Value A PDF 12 form.pdf W3C

Digital Access at Vision Australia

Date: December 2013

Prepared for:
Australian Government Information Management Office
Department of Finance
John Gorton Building
King Edward Terrace, Parkes, ACT 2600

Contact Details

Leona Zumbo
Digital Accessibility Consultant
P: 02 9334 3522
E: leona.zumbo@visionaustralia.org

Neil King
National Manager Digital Access
P: 02 9334 3547
M: 0438 511 761
E: neil.king@visionaustralia.org

Registered Office
Vision Australia
454 Glenferrie Road
Kooyong
Victoria 3144

Mailing Address
Vision Australia
4 Mitchell Street
Enfield
NSW 2136

ABN: 67 108 391 831
ACN: 108 391 831

Last updated: 26 November 2014