Accessibility By Roles - Interaction Design / Usability

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 interaction design / usability function covers tasks and related quality control normally associated with the planning of web interfaces, content changes, interactivity and other interface-related contents of the pages.

Principles Applicable Success Criteria
A AA AAA
Perceivable 1.3.1, 1.3.3, 1.4.1, 1.4.2 1.4.4 1.4.7, 1.4.8
Operable 2.1.1, 2.1.2, 2.2.1, 2.2.2, 2.3.1, 2.4.4 2.4.5, 2.4.6 2.1.3, 2.2.3, 2.2.4, 2.2.5, 2.3.2, 2.4.8, 2.4.9
Understandable 3.2.1, 3.2.2, 3.3.1, 3.3.2 3.2.3, 3.2.4, 3.3.3, 3.3.4 3.1.3, 3.1.5, 3.2.5, 3.3.5, 3.3.6
Robust 4.1.2 -- --
Total (36) 15 7 14


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