- From: White, Jason J <jjwhite@ets.org>
- Date: Wed, 3 Aug 2016 15:23:27 +0000
- To: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <BY2PR0701MB19909569FBCDBBEDFABFBD36AB060@BY2PR0701MB1990.namprd07.prod.outlook.>
From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com] Sent: Wednesday, August 3, 2016 10:28 AM Success Criteria shall: 1. Address a situation where a user with a disability will be disproportionately disadvantaged (as compared to a user without a disability) if the criteria is not met. 2. Be testable through automated or manual processes. [Jason] They should be as reliably testable as possible, while achieving their intended purpose and benefit. 3. Describe the specific condition required to meet the criteria, not the method to address the criteria. 4. Utilize the WCAG 2.0 A/AA/AAA level structure. 5. Ensure for revised Success Criteria that pages that meet the revised guidance continue to meet the corresponding WCAG 2.0 Success Criteria. 6. Apply to all content, unless specific exceptions are included in the success criteria (e.g. "except interruptions involving an emergency"). [Jason] Where a success criterion applies to only some types of content or only under specific conditions, such conditions should be stated explicitly (e.g., “If non-text content is time-based media”). 7. Apply across technologies to the extent possible. (Technology-specific issues should usually be addressed in Techniques.) [Jason] Should read “to the greatest extent possible”. 8. Avoid creating a requirement for something that is already required by an existing Success Criteria. [Jason] Should read “criterion” at the end of the sentence. 9. Have Success Techniques which demonstrate that the Success Criteria is reasonable and implementable, using common formats, user agents, and assistive technologies. [Jason] Should read “the success criterion is”. Success Criteria should: 1. Be as broad as possible, but specific enough not to become a 'catch-all' for any given requirement. 2. Use glossary definitions to simplify and shorten all Success Criteria for shared or ambiguous terms. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Wednesday, 3 August 2016 17:03:33 UTC