PDF Accessibility Checker (PAC 3)

I&IT ACOE
29 Apr 202004:43

Summary

TLDRThe video from the I&IT Accessibility Centre of Excellence (ACOE) introduces PAC 3, a free automated tool for assessing PDF document accessibility. It guides users through the process of uploading a PDF for testing, which results in a summary report of compliance, errors, and warnings. The report is divided into sections including a summary, detailed results, screen reader preview, document statistics, PDF export, and logical structure analysis. The video emphasizes that while PAC 3 is a valuable tool, it should be complemented with manual checks and assistive technology testing, such as using NVDA, a free open-source screen reader, to ensure a comprehensive evaluation of accessibility. The video concludes by encouraging viewers to explore more accessibility tips and to reach out for further information or assistance.

Takeaways

  • πŸ“š **PDF Accessibility Checker (PAC 3)**: A free automated tool for testing PDF documents' accessibility.
  • πŸ” **Requesting PAC 3**: It can be requested through SODO and is used to identify errors and warnings in PDFs.
  • πŸ“ **Selecting a PDF File**: To use PAC 3, select the 'Select PDF File' button and upload the document for testing.
  • βœ… **Compliance Check**: PAC 3 automatically checks if the document is compliant with PDF/UA standards.
  • πŸ“Š **Results Overview**: The Summary Report provides a quick view of passed, warned, and failed checkpoints.
  • πŸ”Ž **Detailed Results**: Expandable options allow for a closer look at specific errors and their locations in the document.
  • πŸ” **Screen Reader Preview**: A feature to visually check logical tag structures and heading levels.
  • πŸ“ˆ **Document Statistics**: Provides information on the document's structure and the frequency of each element or annotation.
  • πŸ“„ **Exporting Reports**: The Summary Report can be exported as a PDF for sharing, but lacks detailed remediation info.
  • πŸ“‹ **Logical Structure View**: Allows inspection of Structure Elements and Artifacts within the document.
  • πŸ€– **Complementing Automated Tools**: Manual and assistive technology testing should be used alongside PAC 3 for a more comprehensive review.
  • πŸ“’ **NVDA Screen Reader**: A recommended free open-source tool for simulating the experience of a screen reader user.
  • πŸ“ **Additional Resources**: For more information or questions, visit ontario.ca/ITaccessibility or use the Advice Request Form.

Q & A

  • What is the full form of PAC 3?

    -PAC 3 stands for PDF Accessibility Checker, which is an automated testing tool used to evaluate the accessibility of PDF documents.

  • How can one obtain the PAC 3 tool?

    -PAC 3 can be requested through SODO, which is a platform for accessing various tools and resources.

  • What does the 'Select PDF File' button look like in PAC 3?

    -The 'Select PDF File' button in PAC 3 is represented by an icon that looks like a cursor over a document.

  • What does the Summary Report in PAC 3 display?

    -The Summary Report in PAC 3 provides a summary view of the document's passed, warned, and failed checkpoints, using symbols like a check mark, gray circle-backslash, yellow triangle with an exclamation point, and a red X.

  • How can one view specific errors or warnings in PAC 3?

    -To view specific errors or warnings, one can select the 'Results in Detail' option, which opens a dialog box that breaks down the checkpoints into specific error types and their locations within the document.

  • What is the purpose of the 'Screen Reader Preview' in PAC 3?

    -The 'Screen Reader Preview' is used to visually check the logical tag structure of the document, verify the order of heading levels, and ensure that the correct tags have been used for the document's content.

  • Is the 'Screen Reader Preview' a substitute for assistive technology testing?

    -No, the 'Screen Reader Preview' should not replace assistive technology testing. It is recommended to use assistive technology like NVDA, a screen reader, to simulate the experience of an assistive technology user.

  • What information can be found in the 'Document Statistics' view of PAC 3?

    -The 'Document Statistics' view provides information about the document structure, broken down by Structure Element and Annotation, indicating how many times each particular element or annotation has been used.

  • How can one share the Summary Report results with others?

    -The 'Summary Report as PDF' feature allows users to export the Summary Report results, which can then be shared with others for review or further analysis.

  • What does the 'Logical Structure' view in PAC 3 show?

    -The 'Logical Structure' view in PAC 3 is used to view the structure of Structure Elements and Artifacts within the document, including their Properties, Page View, and Rolemap.

  • Why is it important to combine automated tools like PAC 3 with manual and assistive technology testing?

    -Automated tools like PAC 3 are only one part of the testing process. Manual and assistive technology testing should also be completed to apply human judgment, identify issues that might be missed by automated tools, and simulate the experience of a screen reader user.

  • How can one request the NVDA screen reader?

    -NVDA, a free open-source screen reader, can be requested through SODO, similar to how PAC 3 is obtained.

  • Where can one find more information or ask additional questions about PDF accessibility?

    -For more information or additional questions, one can visit ontario.ca/ITaccessibility, complete the Advice Request Form, or email [email protected].

Outlines

00:00

πŸ“š Introduction to PDF Accessibility and PAC 3

This paragraph introduces the video series on PDF accessibility, presented by the I&IT Accessibility Centre of Excellence (ACOE). It focuses on the PDF Accessibility Checker (PAC 3), a free automated tool available through SODO, designed to assess the accessibility of PDF documents. The video demonstrates how to use PAC 3, explaining the process from selecting a PDF file to reviewing the accessibility results. The paragraph emphasizes the ease of use and the importance of testing documents for compliance with PDF/UA standards.

πŸ“Š Understanding PAC 3 Results and Reports

The paragraph delves into the results and reporting features of PAC 3. It outlines the six sections of the PDF results, including the Summary Report, which provides an overview of passed, warned, and failed checkpoints. The Results in Detail section is highlighted for its ability to break down specific error types and their locations within the document. The paragraph also mentions the Screen Reader Preview for logical tag structure verification, Document Statistics for structural information, the Summary Report as PDF for sharing purposes, and the Logical Structure view for examining document elements and their properties.

πŸ” Remediation and Additional Testing with Assistive Technology

This section emphasizes that automated tools like PAC 3 are only part of the testing process. It advises on the necessity of manual and assistive technology testing to catch issues that automated tools might miss. The paragraph specifically recommends using NVDA, a free open-source screen reader, to simulate the experience of a screen reader user. It also provides guidance on where to find resources for fixing common PAC 3 errors and warnings, and how to reach out for more information or assistance.

Mindmap

Keywords

πŸ’‘PDF Accessibility

PDF Accessibility refers to the practice of ensuring that PDF documents are accessible to all users, including those with disabilities. This concept is central to the video as it discusses how to use the PAC 3 tool to test PDF documents for compliance with accessibility standards. The tool checks for various accessibility errors and provides feedback on passed, warned, and failed checkpoints, which are crucial for making PDFs accessible to users with disabilities such as visual impairments.

πŸ’‘PAC 3

PAC 3, or the PDF Accessibility Checker version 3, is a free automated tool highlighted in the video for testing the accessibility of PDF files. It evaluates PDFs to determine if they meet PDF/UA compliance, highlighting the accessibility status of documents through a detailed analysis of errors and warnings. The tool's easy-to-use interface and automated testing capabilities are demonstrated in the video, making it a pivotal resource for creators looking to ensure their PDFs are accessible.

πŸ’‘SODO

SODO is mentioned in the video as the platform through which PAC 3 can be requested. While not detailed in the script, it is implied to be a resource or service management platform that provides access to various tools, including PAC 3. This indicates a structured approach to accessing software tools within the organization or community focused on IT and accessibility.

πŸ’‘Screen Reader Preview

The Screen Reader Preview is a feature of PAC 3 described in the video. It allows users to visually check the logical structure of a PDF document to ensure it is correctly tagged for screen readers. This feature helps in verifying the order of heading levels and the appropriate tagging of document elements, which is crucial for screen reader users. The video notes that this should complement, not replace, testing with actual assistive technologies.

πŸ’‘Logical Structure

Logical Structure refers to the way elements within a PDF are organized and tagged to convey their meaning and order, which is essential for accessibility. The video discusses how PAC 3 allows users to view the structure of structure elements and artifacts within the document. This view helps in understanding how different parts of the document are perceived by assistive technologies and is key to ensuring the content is navigable and understandable.

πŸ’‘Manual Testing

Manual testing is discussed in the video as an essential complement to automated tools like PAC 3. It involves human judgment to identify accessibility issues that automated tools might miss, such as the appropriateness of alternative text for images. The video stresses that while tools like PAC 3 are useful, they do not capture all potential accessibility issues, making manual testing indispensable.

πŸ’‘NVDA

NVDA (NonVisual Desktop Access) is mentioned in the video as a free, open-source screen reader that can be requested through SODO. The video recommends using NVDA to simulate the experience of a screen reader user, emphasizing its importance in the accessibility testing process to ensure PDF documents are navigable and usable by individuals who rely on this technology.

πŸ’‘Checkpoints

Checkpoints in the context of the video refer to specific criteria used by PAC 3 to evaluate the accessibility of PDF documents. These checkpoints can pass, warn, or fail, indicating the compliance level of the document with accessibility standards. Each checkpoint relates to different elements of the document, such as text, images, and structure, and helps identify specific areas needing improvement.

πŸ’‘Summary Report

The Summary Report is a feature within PAC 3 described in the video. It provides an overview of the document's accessibility status, summarizing the passed, warned, and failed checkpoints. This report is crucial for quickly assessing the accessibility level of a document and is available for export as a PDF to share with others, though it does not include detailed results needed for remediation.

πŸ’‘Document Statistics

Document Statistics is a view within PAC 3 that provides information about the structure of the document, as mentioned in the video. It breaks down the usage of various structure elements and annotations within the PDF, offering insights into the complexity and detailing of the document's layout. This feature helps in understanding the document's composition, which can influence its accessibility.

Highlights

PAC 3 is a free, automated testing tool for PDF document accessibility.

It can be requested through SODO and outlines various errors and warnings.

The PAC 3 Checker is user-friendly, allowing easy testing of PDF documents for accessibility.

The tool automatically tests documents and provides a compliance status.

Results are categorized into six sections: Summary, Report, Results in Detail, Screen Reader Preview, Document Statistics, Summary Report as PDF, and Logical Structure.

The Summary Report provides a quick view of passed, warned, and failed checkpoints.

Results in Detail offers specific error types and locations within the document.

The Screen Reader Preview helps verify logical tag structure and heading levels.

Document Statistics view provides information on document structure elements and annotations.

Summary Report as PDF allows exporting of results for sharing without detailed remediation information.

Logical Structure view helps examine the document's structure elements and their properties.

Automated tools like PAC 3 are only part of the testing process; manual and assistive technology testing is also crucial.

Manual testing applies human judgment to identify issues that automated tools might miss.

Assistive technology testing, such as with NVDA, simulates the experience of a screen reader user.

NVDA is a free, open-source screen reader available through SODO.

The video provides a demonstration on how to use PAC 3 and interpret the results.

ACOE's Intranet resource offers guidance on fixing common PAC 3 errors and warnings.

For more information or questions, viewers can visit ontario.ca/ITaccessibility or email [email protected].

Transcripts

play00:00

Hi and welcome to our Accessibility Exploration video series on PDF

play00:04

accessibility, brought to you by the I&IT Accessibility Centre of Excellence,

play00:08

or ACOE for short. In this video, we'll be discussing the PDF Accessibility

play00:14

Checker, also known as PAC 3. PAC 3 is a free, automated testing tool that can be

play00:20

requested through SODO. It is used to test PDF documents for accessibility and

play00:24

outlines a variety of errors and warnings.

play00:27

Demo. The PAC 3 Checker is easy

play00:29

to use to test your PDF documents for accessibility. In this demonstration, I

play00:34

will show you how to use PAC 3 to test your document and obtain your

play00:37

accessibility results. To use, navigate to and select the 'Select PDF File' button,

play00:44

which looks like a cursor over a document. From the dialog box that opens,

play00:48

navigate to and select the PDF file you would like tested. Then, select 'Open'. Once

play00:56

the PDF file has been uploaded into PAC 3, the 'Select PDF File' button will be

play01:01

replaced by an image of the first page in your document. PAC 3 will

play01:05

automatically test the document and indicate whether the document is PDF/UA

play01:08

compliant, outline passed, warned, and failed checkpoints, and more. It's that easy!

play01:16

Now let's take a closer look at the

play01:18

results in PAC 3. The PDF results are broken into six sections: the Summary

play01:23

Report, Results in Detail, Screen Reader Preview, Document Statistics, Summary

play01:31

Report as PDF, and Logical Structure. The first is the 'Summary Report'. The Summary

play01:38

Report is exactly that - it's a summary view of the document's

play01:41

passed, warned, and failed checkpoints. A check mark will indicate checkpoints

play01:46

with no errors, a gray circle-backslash indicates checkpoints that do not apply

play01:50

to your document, a yellow triangle with an exclamation point indicates warned

play01:55

checkpoints, and a red X indicates failed checkpoints.

play01:59

You can then select the 'Results in Detail' option to open the Report dialog

play02:03

box, which further breaks down the checkpoints into the specific error type and

play02:07

location within the document. You can expand the drop down menu beside each

play02:11

checkpoint's warned or failed icon to view the specific warning or error. Once

play02:16

selected, a preview of the error type and location of the error will be displayed

play02:20

on the right-hand pane. Please review ACOE's Intranet resource

play02:24

on 'How to Fix Common PAC 3 Errors and Warnings' for information on how to

play02:28

remediate these warnings and errors. The next view we will discuss is the 'Screen

play02:33

Reader Preview', which can be used to visually check that there is a logical

play02:37

tag structure. You can verify the order of heading levels and ensure the correct

play02:41

tags have been used for the document's content. In this screenshot example, we

play02:46

can quickly see that the content jumps from a Heading 1 to a Heading 3, which is

play02:50

incorrect. Please note that using this view should not replace your assistive

play02:54

technology testing. It is recommended to use assistive technology, like NVDA

play02:58

screen reader, to simulate the experience of an assistive technology user.

play03:04

The fourth view is the 'Document Statistics', which can be used to view information

play03:07

about the document structure. Information is broken down by Structure Element and

play03:12

Annotation, and it indicates how many times that particular element or

play03:16

annotation has been used. Next is the 'Summary Report as PDF', which can be used

play03:21

to export the 'Summary Report' results to share with others. Please note that this

play03:26

report does not contain the 'Results in Detail' information required for

play03:29

remediation. And finally, 'Logical Structure', which can be used to view the

play03:34

structure of Structure Elements and Artifacts within the document. This view

play03:38

can be used to view the elements' Properties, Page View, and Rolemap.

play03:43

Remember that automated tools, like PAC 3 are only one part of the testing

play03:48

process. Manual and assistive technology testing should also be completed. Manual

play03:53

testing will apply human judgement and identify issues that might be missed or

play03:57

cannot be determined with an automated tool. For example, automated tools cannot

play04:02

determine if alternative text for images is meaningful. Assistive technology

play04:06

testing should also be completed to simulate the experience of a screen

play04:10

reader user. You are encouraged to use NVDA, which is

play04:13

a free open source screen reader that can be requested through SODO.

play04:17

And that's it! You now know how to test your

play04:20

document in PAC 3 and view the results. Thank you

play04:23

for watching and be sure to check out our other videos for more accessibility

play04:26

tips for PDF documents. Want more information? Have additional questions?

play04:31

Visit us at ontario.ca/ITaccessibility or complete our Advice Request Form.

play04:37

You can also reach us by email at [email protected].

Rate This
β˜…
β˜…
β˜…
β˜…
β˜…

5.0 / 5 (0 votes)

Related Tags
PDF AccessibilityPAC 3 ToolAutomated TestingAccessibility StandardsManual AssessmentAssistive TechnologyScreen ReaderNVDA SoftwareDocument ComplianceACOE ResourcesIT Accessibility