Accessibility By Roles - Architecture

From WAI-Engage: Web Accessibility Community Group
Revision as of 17:01, 10 May 2012 by Srush (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

« Return to main 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 architecture function covers tasks and related quality control normally associated with the architecture of the information (Web content) and the architecture of the data.

Principles Applicable Success Criteria
A AA AAA
Perceivable 1.3.1 -- --
Operable 2.4.2 2.4.5, 2.4.6 2.4.8, 2.4.10
Understandable -- 3.1.2 3.1.3, 3.1.4
Robust -- -- --
Total (9) 2 3 4

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
--- --- --- ---
--- --- --- ---