zakkinsey
commented
5 years ago Comment created by @:
{color:#000000}Evaluation with Acrobat and JAWS {color}
{color:#000000} {color}
{color:#000000}Adobe Acrobat DC (19.010.10059){color}
{color:#000000}JAWS Version 2018.1811.2 ILM{color}
{color:#000000}Windows 10{color}
{color:#000000} {color}
JAWS reads the footers and headers:
1.3.1 Info and Relationships | Structure element: Artifact | non-compliant What is “tagged PDF”? PDF was originally designed to provide accurate, reliable on screen and printed results for page based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Logo PDF Techniques Accesssiblity Summit | organized by PDF Association Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). What is PDF/UA? PDF/UA is the commonly accepted name for ISO 14289, an international standard defining the correct use of PDF tagging for accessibility purposes. A highly technical specification, PDF/UA identifies the components and properties of PDF technology which are relevant to accessibility, and provides requirements and restrictions on their use. History of PDF/UA Since 2004, AIIM’s PDF/UA Committee has collected stake-holders from throughout the industry to explore and develop technical requirements for accessible PDF technology. Following the publication of PDF 1.7 as ISO 32000-1 in 2008, PDF/UA was re-developed to become an ISO standard. ISO 14289-1 (PDF/UA) was first published in 2012. How PDF/UA makes the world a better place? Establishes technical requirements necessary to document creation, viewing and AT software that can provide high quality access to PDF content Provides an International Standard to guide software procurement and development Provides a technically-specific road map to conformance with WCAG 2.0 in PDF content Works with PDF/A, the ISO standard for archival PDF documents Improves customer service and employee relations Reduces liability exposure and minimizes legal uncertainty Why does the world need PDF/UA? PDF is all about reliability. For accessibility needs, however, the core PDF language provides the mechanism but not the technical requirements necessary to ensure accessibility. Tagged PDF first entered the market in 2001, but even today a substantial number of PDF documents produced on desk-top computers are untagged, and many tagged PDF documents are substandard. PDF Association Page 1 PDF Techniques for WCAG 2.1 | Example Files Consequently, most users who rely on assistive technology to read have learned to dislike PDF files for the unreliable, disjointed and grossly unsatisfactory experience they’ve so often received. PDF/UA adoption fixes this problem. Read more: https://www.pdfa.org/ PDF was originally designed to provide accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF was originally designed to provide accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF was originally designed to provide accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF was originally designed to provide accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF was originally designed to provide accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF was originally designed to provide accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF was originally designed to provide accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF was originally designed to provide accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF was originally designed to provide PDF Association Page 2 PDF Techniques for WCAG 2.1 | Example Files accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF was originally designed to provide accurate, reliable on-screen and printed results for page-based content. Accessibility was not a consideration. Tagged PDF, the mechanism which enables accessibility via logical structure and semantic mechanisms was added to PDF in 2001. Tagged PDF made it possible to represent content independent of its static visual presentation, allowing any end user to access PDF content through mechanisms such as text reflow or text to speech, or via a preferred Assistive Technology (AT). PDF Association Page 3
Jira issue originally created by user @MarkusErle:
This example describes a failure that occurs when running headers and / or footers repeat the identical content and are part of the structure tree.