[oplinwebkits] Understanding options for library newsletters

[Laura Solomon]

Hello folks,

I had a couple of questions about this just this morning. I typed up a
response and realized the information might be useful to any library
currently seeking an alternative to PDF newsletters.

*My response:*

*It's important to understand that PDFs are inherently inaccessible.  As a
format, they should really be discontinued entirely, especially by public
entities. They also create a usability burden for mobile users, making the
argument to stop using them even more compelling. *

*Let me preface the rest of this with "I am not a lawyer."  That said, I
have discussed this with a specialist at the Department of Justice.  Here's
a summary: In theory, you could send out a PDF without hosting it on a
public website.  That would force users with disabilities to specifically
request an accessible alternative.  Then what? You need to provide an
accessible alternative. Your library will need to prepare for that. *

*My own thoughts:  *

   - *It also creates additional friction specifically for users with
   disabilities, which is not a great public relations move for a library. If
   you must have an accessible alternative anyway, I would recommend just
   using that from the start rather than inviting potential controversy or
   Department of Justice complaints.*
   - *Third-party products may be better alternatives, but it's critical
   that your library ask the vendor for a VPAT/ACR and get a specific timeline
   for when the vendor plans to remediate any WCAG failures (just getting the
   VPAT/ACR is not enough!). Anecdotally, I just looked at a Patron Point
   newsletter from a WebKit library yesterday and the accessibility results
   were, unfortunately, very poor. The problem is that I have no way to know
   if this result stems from the actual Patron Point product or from how the
   library built the newsletter. This is why it's so important to look at a
   vendor's accessibility documentation and communicate with them directly.*
   - *So, where does that leave libraries?  If an accessible third-party
   product is not an option, I recommend making newsletter content available
   on the website.  Medina County <https://www.mcdl.info/SpringLL> has made
   the content of their newsletter available directly on their website. You
   could easily use a similar format and even still add images. *

Let me know if you have other questions,

-- 
*Laura Solomon,  CPAAC, MCIW, MLS *(She/her)
*Library Services Manager,* Ohio Public Library Information Network (OPLIN)
(614) 752-0792 (voice) | (614) 728-5256 (fax)
laura at oplin.ohio.gov | https://oplin.ohio.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oplin.org/pipermail/oplinwebkits/attachments/20260430/0f2cfadb/attachment.htm>