Accessibility Responsibility Breakdown - Analysis
@@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)
Contents
Applicable WCAG 2.0 Success Criteria
Analysis
The analysis function covers the tasks normally associated with analysis of the project’s strategic orientations, analysis of the options for technology platforms, or functional analysis of Web interfaces.
Principles | Applicable Success Criteria | ||
---|---|---|---|
A | AA | AAA | |
Perceivable | -- | -- | -- |
Operable | -- | -- | 2.2.3, 2.2.4, 2.2.5 |
Understandable | 3.2.1, 3.3.1 | 3.3.3, 3.3.4 | 3.3.5, 3.3.6 |
Robust | -- | -- | -- |
Total (9) | 2 | 2 | 5 |
The applicable success criteria relevant to the Analysis role are organized by principles (perceivable, operable, understanding, robust) below.
Perceivable
No success criteria applicable for the Analysis role as of yet.
@@Editor's note: Maybe add a note about potential relevant SC that could apply form this principle. (dboudreau, 2012/05/04)
Operable
Success Criteria | Description | Specific Benefits | Sufficient Techniques |
---|---|---|---|
2.2.3 No Timing (AAA) | Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. |
|
Techniques for SC 2.2.3 |
2.2.4 Interruptions (AAA) | Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. |
|
Techniques for SC 2.2.4 |
2.2.5 Re-authenticating (AAA) | When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. |
|
Techniques for SC 2.2.5 |
Understandable
Success Criteria | Description | Specific Benefits | Sufficient Techniques |
---|---|---|---|
3.2.1 On Focus (A) | When any component receives focus, it does not initiate a change of context. |
|
Techniques for SC 3.2.1 |
3.3.1 Error Identification (A) | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. |
|
Techniques for SC 3.3.1 |
3.3.3 Error Suggestion (AA) | If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. |
|
Techniques for SC 3.3.3 |
3.3.4 Error Prevention (Legal, Financial, Data) (AA) | For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:
|
|
Techniques for SC 3.3.4 |
3.3.5 Help (AAA) | Context-sensitive help is available. |
|
Techniques for SC 3.3.5 |
3.3.6 Error Prevention (All) (AAA) | For Web pages that require the user to submit information, at least one of the following is true:
|
|
Techniques for SC 3.3.6 |
Robust
No success criteria applicable for the Analysis role as of yet.
@@Editor's note: Maybe add a note about potential relevant SC that could apply form this principle. (dboudreau, 2012/05/04)