WCAG Success Criteria Proposals
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAHAIAJAKALAMANAOAPAQARASATAUAV
1
Possible 2.2Short NameTextIssueTFNew
Level
NotesIssuesIssuesIssuesIssuesIssuesIssuesIssuesIssuesIssuesIssuesPR#1
Disproportionate
Barrier for PWD
#2
Testable
#3
Condition
not method
#4
WCAG
Structure
#5
Backward
Compatible
#6
Applies to
all content
#7
All
Technologies
#8
Not
Covered
#9
Implement
able
Pass
ALL
SC
RE
WRITE
Change
Level
Current
Level
Overlap
Issue
Mgr
2
YesText ColorsUsers must be able to change foreground and background colors chosen from the full range of color choices provided by the user agent, without loss of important information.
74LVTFAUser Agent issue, SC don't reference usersYesYesYesYesYes
3
YesFont FamilyThe user can change the font family to any available to the user agent.78LVTFAANot Mature User AgentYesYesYesYesYesYesYesErich Manser
4
Reflow57LVTFWas combined with zoom and eventually reintegrated as 320 px not character length of lines.
5
YesNotificaiton of busyCould be part of status messages3MATF
6
Pointer59MATF
7
Concurrent input mechanismsAll functionality can be operated when a user switches between input mechanisms 64MATFAAHard to testYesYesYesYesYesYes
8
Keyboard with AT (that remaps key input)All functions available by keyboard are still available by keyboard after accessibility-supported assistive technology that remaps keystrokes is turned on. 62MATFAAAlready required 2.1 + Conformance YesYesYesYesYesYesYesYesMarc Johlic
9
Device sensorsAll functionality of the content can be operated without requiring specific device sensor information unless the device sensor is essential for the function and not using it would invalidate the activity. Note 1: device sensor information includes, but is not limited to, additional input values such as tilt, orientation, proximity. 67MATFAMatureYesYesYesYesYesYesYesYesYesPASSJon Avila
10
Pointer inputs with additional sensorsAll functionality can be operated without requiring pointer information beyond screen coordinates. Note 1: Additional sensor information includes pressure (for instance on pressure-sensitive touch screens), tilt or twist (for instance on advanced pen/stylus digitizers). 66MATFAMatureYesYesYesYesYesYesYesYesYesPASSJon Avila?
11
Speech InputAll functionality of the content does not obstruct a user’s ability to access the commands through speech input. (Level A)
68Not Mature. Would be difficult to test.YesYesYesYesYesYesAMATF
12
Non-interference of ATContent does not interfere with the normal operation of the platform assistive technology or a mechanism is available to override the interference, unless the interference is essential for use of the content.71Not Mature hard to test already covered substantially under Conformance Requirement 5 https://www.w3.org/TR/2008/REC-WCAG20-20081211/#cc5YesYesYesYesYesYesAMATFJoshue O'Conner
13
Change on RequestChanges of context, functionality, settings, route and orientation are initiated only by user request or an easily available mechanism is available to turn off such changes. An easily available mechanism is also available to go to previous context, functionality, settings, route and orientation. Exception: The changes are part of an activity where it is essential (e.g. a game)@@48COGAAA"Easily"YesYesYesYesYesYesYesYesAAA
14
Consistent Identification @@and Styles@@: Components that have the same functionality within a set of Web pages are identified consistently. Components that have the same type of information, or have the same function within a set of Web pages, are styled consistently in the primary modality of the content. 
Exception: If a specific structure is an essential part of the main function of the Web page.
28COGAAAThis is acheivable. "Same type of information" would need to be carefully defined. It is fairly broad and subjective currently134YesYesYesYesYesYesYesYesYesNoAACOGA 29
15
Consistent Navigation Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. @@Common navigation, search, and control elements have a consistent position within a set of web pages in the primary modality of the content, unless a change is initiated by the user.29COGAAAThis is within reach. The word "common" needs to be tightened up or defined. "Control elements" seems ambiguous.122YesYesYesYesYesYesYesYesYesNoAACOGA 28
16
Critical featuresCritical features and important information are above the fold and are accentuated in the main modality of the content. 39COGA 95YesYesYesYesYes
17
Error Prevention (Legal, Financial, Data)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, that submit user test responses or submit or store important information each of the following is true:

1. Modify: A simple mechanism is provided to allow the user to assess and correct mistakes, including mistakes that might not be automaticaly identified. The user can repair information via clearly labeled actions and get back to the place they were at, in one clearly labeled action without unwanted loss of data.
2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
3. Confirmed: A summary is provided before submitting important information and the user is notified when they are about to submit the final information.
4. Time frames for cancelling transactions can be programmiticaly determined@@
33COGAA 104YesYesYesYesYesYesYesYesAAA
18
Labels or InstructionsLabels or instructions are provided when content requires user input. Labels and instructions:

• Fully describe the input's function
• Use the default format and standards for localized content in the location of the user and allow for changes of format on labels and user input. An exception is provided where any standard format is accepted.
• Explain where to get the required information. An exception is provided where the information is known by the intended audience.
Note: Information is known by the intended audience includes the user's name, phone number, address, date of birth and other information where user testing has shown that the information is known by the intended audience.@@.
56COGAA YesYesYesYesYesYesNoA
19
MetaDataAccessibility Metadata is provided which describes the accessibility characteristics of the content using an openly published vocabulary. At a minimum this is a machine readable description either on the page or referenced from the set of pages to which it applies. A human readable summary may also be provided.82DPUBAAA142YesYesYesYesYesYesYes
20
Name, Role,@@ State,@@ ValueFor all user interface components (including but not limited to: form elements, links and components generated by scripts)

• the name and role of the component @@can be programmatically determined,
• the @@ states, author-settable properties, and values of the component can be programmatically determined, @@
• states, author-settable properties, and values that can be set by the user can be programmatically set, by user agents, including assistive technologies and
• notification of changes @@to any@@ of these items is available to user agents, including assistive technologies.
22COGAA YesYesYesYesYesYesYesYesYesPASSYesNoA
21
Clear controls36COGAAA 101YesYesYesYesYesYes10
LVTF
22
Clear Purpose55COGAA"clear"103YesYesYesYesYes
23
Clear structure and relationships26COGAAA YesYesYesYes
24
Consistent Cues31COGAAA 108YesYesYesYesYesYes
25
Extra Help advanced45COGAAAA YesYesYesYesYesYes
26
Familiar Design Enhanced35COGAAA 121YesYesYesYesYes
27
Feedback54COGAAAClearly, rapid feedback, primary modality, non-AT Audio feedback108YesYesYesYesYes2
MATF
28
Finding Help43COGAAASee Paciello comments YesYesYesYesYesYesYesYes
29
Identify Charges37COGAA 100YesYesYesYesYesYesYesYes
30
Plain language all content41COGAAA 107YesYesYesYesYesYes
31
Plain language enhanced42COGAAAA 105YesYesYesYesYesYes
32
Reminders34COGAYesYesYesYesYesYesYesAA
33
Return53COGAAA YesYesYesYesYesYesCOGA 38, MATF 65
34
Safety20COGAA YesYesYes
35
Search44COGAAA YesYesYesYesYesYes
36
Section Headings40COGAAAMatureYesYesYesYesYesYesYesYesYesPASSYesYesAAA2.4.10
37
Standardized APIs46COGAA YesYesYesYes
38
Task completion21COGAA YesYesYes
39
User Information25COGAA YesYesYes
40
Visual presentation 51COGAAA113YesYesYesYesYesYesYesYesYesAAA1.4.8
41
Minimize user errors (AAA)13COGAy-AlmostAAACOGA is0submitting it as AAA to get it in, based on oposition at higher levels. Has good momentum since scope was reduced. Questions about separators, and implications of requiring all entry that has less than 31 choices to be choosable from an array.27224020222321197YesYesYesYesYesYesYesYesYesPASSYesNoA3.3.3
42
Plain language (enhanced)41COGAMomentumAAAMany ask how this could apply and be measured across languages. Concerns about testability, and implementability. It's been narrowed. General group desire to find a requirement266236197210179211177149209245135YesYesYesYesYesYesYesYes
43
Meaningful Set312ePubSomeInterestAThis was sitting as an issue 162 for a long time, but didn't have a champion to field it to the group.313YesYesYesYesYesYesPass
44
Support Personalization (AAA)COGASomeInterestAA
45
Provide Support (AAA)32COGASomeInterestAAACOGA is presenting it as AAA to get it in, based on oposition at higher levels. Mixed, some didn't want it included274242204224211129YesYesYesYesYesYesYesAAA3.3.5
46
Familiar Design (Minimum)49COGALow ActivtyAMost comments suggest to not include in WCAG or consider only at AAA270239200211121YesYesYesYesYesYes
47
Manageable blocks24COGALow ActivityAAMixed, some didn't want it included267247198211178YesYesYesYesYesYesYes
48
Pointer inputs with additional sensors66MATFYesMomentumAMature, comments addressed, hasn't gone to larger group yet262194144YesYesYesYesYesYesYesYesYesPASS
49
Linearization58LVTFYesSomeInterestASignificant objections on Github. which may be addressed by reducing scope from "content" to "running text", however, it is unclear how that would differ from resize text. If 400% zoom Sc goes through we should probably defer this SC24921318417116015989YesYesYesYesYesYesYes?YesCOGA 51 LVTF 77
50
Plain language (Miniumum)30COGAYesMomentumAAAMany ask how this could apply and be measured across languages. Concerns about testability, and implementability. It's been narrowed. General group desire to find a requirement. COGA is presenting it as AAA to get it in, based on oposition at higher levels.266236197210179211177149209245135YesYesYesYesYesYesYesYes
51
Extra Help32COGAXTRAAAA"Easily Available"YesYesYesYesYes
52
Extra Symbols (AAA)50COGAXTRAMomentumAAACOGA is presenting it as AAA to get it in, based on oposition at higher levels. Mixed, some momentum but questions about execution and scope, incoporates attributes etc that don't yet exist. Seems to be getting rolled into personalization. Proposed now at AAA.268237211115YesYesYesYes
53
Error Prevention (Legal, Financial, Data)33COGAYesMomentumAReduced to requiring a read only summary to financial or legal, so basically 3.3.4 with the extra summary
54
Printing - Pending76AAAEditViewdisussion ongoing252215185176173216141YesYesYesYes
55
Undo - pending38AAAEditViewMixed, some didn't want it included, discussion about whether it should be scoped to data entry and steps in a process273241203224211163YesYesYesYesYes
56
Accessible Authentication23AEditViewCOGA354325440473YesYesYesYesYes?
57
Interruptions (minimum)47AAEditViewThe term "easily available" is not testable. Suppressing interuptions AND changes in content is a big ask. Interuptions could be handled by not overriding popup blockers.35325918221120623128344344444544644747449398YesYesYesYesYesYesYes2.2.2 Pause stop hide (A)2.2.4 Interuptions
58
59
60
61
Loading...
Main menu