"genericizing" our examples and test procedures

• From: Loretta Guarino Reid <lorettaguarino@google.com>
• Date: Thu, 14 Apr 2011 11:18:45 -0700
• To: Andrew Kirkpatrick <akirkpat@adobe.com>, Mary Utt <maryutt@paciellogroup.com>
• Cc: WCAG <w3c-wai-gl@w3.org>
• Message-ID: <BANLkTikkW2he8f8X+FcQGBYSU_FW7HRwQA@mail.gmail.com>

Andrew and Mary,

Could you make a pass over the PDF techniques and apply the following
changes to make them more clearly tool-neutral:

* Put a boilerplate caveat on each example of using a specific
authoring or editing tool (e.g. "This example is shown with Adobe
Acrobat. There are other software products that perform similar
functions. See the list of other software tools [link to appropriate
PDF technology overview section].

* Take the specific Adobe product naming out of the test procedures,
and use the generic terms: PDF creator, PDF converter, PDF editor, or
PDF accessibility checker instead of naming specific Adobe products.

Let us know if you find places where this doesn't work.

Thanks, Loretta

Received on Thursday, 14 April 2011 18:19:09 UTC