[Athen] How do WCAG & PDF/UA authorize removing running headers and footers from PDFs?

[Adina Mulliken]

Hi all,
Apologies for the cross posting.

I’m wondering if anyone could advise me what success criteria or techniques within WCAG you think could most clearly be interpreted to authorize “removing” repetitive headers and footers from PDFs?  I’m aiming to find the most specific criterion or “technique” or “failure” that I can.   Maybe 2.4.1 Bypass blocks?  Or Info and Relationships?  If nothing else, I suppose this could fall under POUR principles.  Or anything within PDF/UA or any other standards you know of?  Maybe this sentence that I found in PDF/UA: “Artifacts shall be marked as such and shall not be tagged in the structure tree.”?

I would also appreciate opinions from any of you all in the accessibility community saying whether you think it’s important to remove repetitive headers and footers that interrupt the flow of text, as that could be helpful for me.

I want to see if I can justify erring on the accessibility side of a possible conflict between copyright/licensing versus accessibility.  (This is a situation where exceptions to copyright for people with disabilities wouldn’t apply.)

Please respond to me directly if you prefer.

Thank you!
Adina

Adina Mulliken
Associate Professor, Librarian Silberman Social Work and Urban Public Health Library
Hunter College, City University of New York
2180 3rd Ave. New York, NY
Phone 212-396-7665
Pronouns she/her
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20230629/bc5c0664/attachment.html>