Update PDF techniques

[fstrr]

This branch updates the PDF Techniques for the first time since approximately 2011.

1. Reduced the amount of screen grabs
2. Updated the screen grabs we kept
3. Updated menu commands so that they're up to date with the current versions of apps
4. Updated some working documents
5. Added alt text to numerous images
6. Fixed broken links
7. Removed content related to Adobe LiveCycle, which was EOLd in 2013
8. Fixed several color contrast issues in PDFs
9. Fixed some typos
10. Added more OpenOffice content
11. Added support for syntax highlighting

[bruce-usab]

@fstrr or @mbgower -- can you clue me into the mechanics for generating the GitHack preview for a branch or PR? Or is that exposed automatically and I am not looking in the right place?

My usual reviewing habits will be insufficient for this set of work!

[fstrr]

I don't know if you can do it at a folder level, but here's the pattern for pages:

https://raw.githack.com/[account-name]/[repo-name]/[branch-name]/[folder-structure]/[file-name].html

So:

https://raw.githack.com/w3c/wcag/update-pdf-techniques/techniques/pdf/PDF1.html

Note: I added you and Mike as reviewers yesterday, but then found out that @ljoakley has one more file (PDF21) to work on, so I changed the PR back to a draft. That said, there's plenty of files before that to review before you get to that one.

[bruce-usab]

I added you and Mike as reviewers yesterday

Which is why I asked! No need to preview the whole folder, so thanks very much for the GitHack syntax. This is a lot of work your are doing!

Ping to @DuffJohnson in case he is curious to see where we hope PDFA might pick up.

[fstrr]

I do wish that we'd also updated these to be tool agnostic rather than updating vendors' products. Maybe when the forthcoming PDF Association documents get published it'll be a sensible time to re-visit the techniques.

[DuffJohnson]

Thanks for the pointer; I've forwarded this to the PDF Accessibility LWG for review.

[fstrr]

@bruce-usab It's all done, so I've changed it to ready for review and assigned you.

[mbgower]

@awkawk FYI some updates to the PDF techniques. Willing to review? :)

[awkawk]

@mbgower arranged for Rob on my team to do so

[awkawk]

One note that jumps out is that Livecycle Designer wasn't EOL'd, it was renamed to Adobe AEM Designer. We can get an updated screenshot but the dialog is basically the same. See https://help.adobe.com/en_US/AEMForms/6.1/DesignerHelp/WS92d06802c76abadbe98a8d5129b8b01f08-7fd8.2.html for a reference.

[alastc]

We agreed to merge these, but can take updates if Rob finds anything wrong.

[awkawk]

That's fine. For the future, if planning to approve a set of changes to 23 techniques on Tuesday, asking for review 4 days earlier (and over a weekend) is a little tight.

Also note that the comment that I made 5 days ago was not attended to.