PDF's

[ThomasFSeeger]

Story

As a content manager
I want to know what content is appropriate to post as a pdf, and what content is not appropriate
So that I provide accessible, timely, authoritative information to the public

Acceptance Criteria

Given preconditions of a system
When some event occurs
Then some event or behavior occurs

Resources

• https://digital.gov/2013/12/06/step-away-from-the-pdfs/
• https://digital.gov/2015/07/23/pdfs-a-digital-content-detour/
• https://www.epa.gov/web-policies-and-procedures/web-standard-pdf-accessibility-requirements
• https://gds.blog.gov.uk/2018/07/16/why-gov-uk-content-should-be-published-in-html-and-not-pdf/
• https://phescreening.blog.gov.uk/2016/11/18/bye-bye-pdf-hello-html/

[ryanwoldatwork]

What content "needs to be" published as a .pdf? Or, is better to publish as such?

https://gds.blog.gov.uk/2018/07/16/why-gov-uk-content-should-be-published-in-html-and-not-pdf/

[ADean27]

as a person making business decisions i need to understand the pros and cons of PDFs and similar formats so i can ensure that those that need the information can access it AND so i can make smart business decisions around info delivery

[ryanwoldatwork]

https://digital.gov/2015/07/23/pdfs-a-digital-content-detour/

[ryanwoldatwork]

Is it possible/valuable to re-frame this as:

Content should be published as HTML by default unless certain exceptions that we can define below:

• a digital process that requires (per law/policy/statute) that a paper process must be available
• etc, etc

[ADean27]

Yes, I think having some succinct and clear guidelines to reference around PDFs would help. Communicating our forms requirements/options to a larger audience could get this info to people before they create, which could steer us more toward accessible HTML than remediated-but-still-complicated PDFs.

…

On Thu, Oct 27, 2022 at 6:00 PM Ryan Wold ***@***.***> wrote: Is it possible/valuable to re-frame this as: Content should be published as HTML by default unless certain exceptions that we can define below: - a digital process that requires (per law/policy/statute) that a paper process must be available - etc, etc — Reply to this email directly, view it on GitHub <#46 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANTW6YIWA6M2YSHD7O4WJS3WFL3NLANCNFSM5F3DBDPQ> . You are receiving this because you commented.Message ID: ***@***.***>

[ryanwoldatwork]

• https://digital.gov/2013/12/06/step-away-from-the-pdfs/

• https://digital.gov/2015/07/23/pdfs-a-digital-content-detour/

• https://gds.blog.gov.uk/2018/07/16/why-gov-uk-content-should-be-published-in-html-and-not-pdf/

• https://phescreening.blog.gov.uk/2016/11/18/bye-bye-pdf-hello-html/

Added these to the main issue as well.

[ryanwoldatwork]

https://www.epa.gov/web-policies-and-procedures/web-standard-pdf-accessibility-requirements

[ryanwoldatwork]

This command can be used via google to get a list of .pdfs

Search using: filetype:pdf site:example.gov