Open zakkinsey opened 5 years ago
Comment created by Andres Gonzalez <andgonza@adobe.com>
:
Evaluation with Acrobat and JAWS
Adobe Acrobat DC (19.010.10059)
JAWS Version 2018.1811.2 ILM
Windows 10
JAWS reads:
based content. Accessibility was not a consideration. Ta gged PDF, the mechanism which enables accessibility via logical structure and semantic mecha nisms 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).
Comment created by @MarkusErle:
Suptype Footer and Header is missing
Peter Spraul <p.spraul@axes4.com>
assigned issue to self
Comment created by Peter Spraul <p.spraul@axes4.com>
:
Attached PDF was changed to an atomic example: document with 2 pages, each with header and footer which were artifacted
Comment created by @MarkusErle:
We need 2 examples: (1) header and footer is artifacted starting from the 2 instance on
(2) header and footer is artifacted starting from the 1 instance on
Add subtype
Comment created by @pkopicar:
Try reusing existing pdf sample from #32
Comment created by @MarkusErle:
Add in description:
Emphasize that it is related to a section / chapter
Comment created by @calanca2:
LWG Meeting Notes
3 alt. techniques:
Technique A
PAC3-View is presented
Technique B1:
B2.
Concerns? *Technique per document or for document part?* *A.: It is related to the section - explain more?**
Comment created by @pkopicar:
Cleaned up
@willkil changed assignee from Peter Spraul <p.spraul@axes4.com>
to self
@willkil added a link to #211: This issue relates to #211
@willkil added a link to #212: This issue relates to #212
@willkil added a link to #32: This issue relates to #32
Comment created by @willkil:
To follow the rule of one JIRA issue per sample file, I moved the B1 example to #211 and the B2 example to #212
@willkil unassigned issue from self
@calanca2 assigned issue to @MarkusErle
Comment created by @PaulRayius:
Metadata Committee - 12/22/2021 - Updated Matterhorn and WCAG - determined to not be a WCAG fail for 1.3.1 but does apply to 1.3.2 - Meaningful Sequence. IF the header or footer was tagged, it would cause a fail for 1.3.2 (in documents with multiple pages).
Comment created by @calanca2:
add page numbers as in 32!
Comment created by @calanca2:
re-check metadata after changing the example
metadata working group is taking care of this
Comment created by @PaulRayius:
Metadata has been rechecked and is good. Jan. 26, 2022.
Comment created by @MarkusErle:
Added page numbers to the example.
File has to be cleaned up still.
Comment created by @PaulRayius:
Metadata committee checked - the PDF does not look like the Pagination artifacts, or header/footer subtype, has been set. Please recheck the file.
It's our opinion that there are no WCAG Success Criteria that are relevant to this example.
@zakkinsey unassigned issue from @MarkusErle as part of jira->github migration
Jira issue originally created by user @MarkusErle:
The objective of this technique is to show how to handle running headers and footers.