From WAI-Engage: Web Accessibility Community Group
« Return to WAI-Engage Wiki Home « Return to main ARB page
@@Editor's note: This document is a work in progress meant to be built collaboratively and commented by the WAI-Engage community. Every member of this community is welcomed to either send comments directly to the editor through email at dboudreau [at] accessibiliteweb [dot] com or by editing the content below using the wiki. In order to keep track of all modifications, please provide a summary of all the changes brought to the document within the wiki interface and check if this is a minor edit or not. Thank you. (dboudreau, 2012/04/13)
Applicable WCAG 2.0 Success Criteria
The content strategy function covers tasks and related quality control normally associated with producing the site’s textual contents, equivalent alternative for non-text content and other general text elements presented in the pages.
| Principles
| Applicable Success Criteria
|
| A
| AA
| AAA
|
| Perceivable
| 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3.1, 1.3.3
| 1.2.5
| 1.2.7, 1.2.8
|
| Operable
| 2.1.1, 2.1.2, 2.4.2, 2.4.4
| 2.4.6
| 2.4.9
|
| Understandable
| 3.3.1
| 3.1.2
| 3.1.3, 3.1.4, 3.1.5, 3.1.6
|
| Robust
| --
| --
| --
|
| Total (21)
| 11
| 3
| 7
|
Applicable Success Criteria by Principles
The applicable success criteria relevant to the Architcture role are organized by principles (perceivable, operable, understanding, robust) below.
Perceivable
| Success Criteria
| Description
| Specific Benefits
| Sufficient Techniques
|
| ---
| ---
| ---
| ---
|
| ---
| ---
| ---
| ---
|
Operable
| Success Criteria
| Description
| Specific Benefits
| Sufficient Techniques
|
| ---
| ---
| ---
| ---
|
| ---
| ---
| ---
| ---
|
Understandable
| Success Criteria
| Description
| Specific Benefits
| Sufficient Techniques
|
| ---
| ---
| ---
| ---
|
| ---
| ---
| ---
| ---
|
Robust
| Success Criteria
| Description
| Specific Benefits
| Sufficient Techniques
|
| ---
| ---
| ---
| ---
|
| ---
| ---
| ---
| ---
|
