3 ms·
Overall, decisions like this are compromises, with pros and cons: "They’re not designed for reading on screens" That's a subjective distinction. "It’s harder
by Spooky23 8y ago
Overall, decisions like this are compromises, with pros and cons:
"They’re not designed for reading on screens"
That's a subjective distinction.
"It’s harder to track their use"
Not relevant for most .gov use cases. Also, sounds like something that isn't a user problem.
"They cause difficulties for navigation and orientation"
So does responsive design that makes discovery of content difficult in many scenarios, especially atypical scenarios.
"They can be hard for some users to access"
So does HTML where a poor accessibility process is in place.
"They’re less likely to be kept up to date"
Conversely, they more easy for a consumer understand when changes take place, and encourage a stronger release process.
"They’re hard to reuse"
That may or may not be a bad thing.
- allannienhuis 8y agoI think the point is: it's harder to do those things properly in PDF format. Also, I'm not sure how 'not designed for reading on screens' is subjective. PDFs are paper-document oriented and don't display well for reading on anything other than a large size monitor in virtually every case I've seen. When delivering content in a web browser, why on earth would someone prefer to view PDF vs a reasonably well laid out HTML version? I think PDFs are common in gov't websites because much of the internal culture is paper-document centred, and having those nicely printed PDFs solve internal problems for gov't employees, not because they are actually any better for the users of the website. Canadian Gov't websites are full of PDF content too. :(