|Possible 2.2||Short Name||Text||Issue||TF||New|
Barrier for PWD
|Yes||Text Colors||Users 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.||74||LVTF||A||User Agent issue, SC don't reference users||Yes||Yes||Yes||Yes||Yes|
|Yes||Font Family||The user can change the font family to any available to the user agent.||78||LVTF||AA||Not Mature User Agent||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Erich Manser|
|Reflow||57||LVTF||Was combined with zoom and eventually reintegrated as 320 px not character length of lines.|
|Yes||Notificaiton of busy||Could be part of status messages||3||MATF|
|Concurrent input mechanisms||All functionality can be operated when a user switches between input mechanisms||64||MATF||AA||Hard to test||Yes||Yes||Yes||Yes||Yes||Yes|
|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.||62||MATF||AA||Already required 2.1 + Conformance||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Marc Johlic|
|Device sensors||All 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.||67||MATF||A||Mature||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||PASS||Jon Avila|
|Pointer inputs with additional sensors||All 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).||66||MATF||A||Mature||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||PASS||Jon Avila?|
|Speech Input||All functionality of the content does not obstruct a user’s ability to access the commands through speech input. (Level A)||68||Not Mature. Would be difficult to test.||Yes||Yes||Yes||Yes||Yes||Yes||A||MATF|
|Non-interference of AT||Content 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.||71||Not Mature hard to test already covered substantially under Conformance Requirement 5 https://www.w3.org/TR/2008/REC-WCAG20-20081211/#cc5||Yes||Yes||Yes||Yes||Yes||Yes||A||MATF||Joshue O'Conner|
|Change on Request||Changes 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)@@||48||COGA||AA||"Easily"||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||AAA|
|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.
|28||COGA||AA||This is acheivable. "Same type of information" would need to be carefully defined. It is fairly broad and subjective currently||134||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||No||AA||COGA 29|
|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.||29||COGA||AA||This is within reach. The word "common" needs to be tightened up or defined. "Control elements" seems ambiguous.||122||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||No||AA||COGA 28|
|Critical features||Critical features and important information are above the fold and are accentuated in the main modality of the content.||39||COGA||95||Yes||Yes||Yes||Yes||Yes|
|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@@
|Labels or Instructions||Labels 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.@@.
|MetaData||Accessibility 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.||82||DPUB||AAA||142||Yes||Yes||Yes||Yes||Yes||Yes||Yes|
|Name, Role,@@ State,@@ Value||For 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.
|Clear structure and relationships||26||COGA||AA||Yes||Yes||Yes||Yes|
|Extra Help advanced||45||COGA||AAA||Yes||Yes||Yes||Yes||Yes||Yes|
|Familiar Design Enhanced||35||COGA||AA||121||Yes||Yes||Yes||Yes||Yes|
|Feedback||54||COGA||AA||Clearly, rapid feedback, primary modality, non-AT Audio feedback||108||Yes||Yes||Yes||Yes||Yes||2|
|Finding Help||43||COGA||AA||See Paciello comments||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes|
|Plain language all content||41||COGA||AA||107||Yes||Yes||Yes||Yes||Yes||Yes|
|Plain language enhanced||42||COGA||AAA||105||Yes||Yes||Yes||Yes||Yes||Yes|
|Return||53||COGA||AA||Yes||Yes||Yes||Yes||Yes||Yes||COGA 38, MATF 65|
|Minimize user errors (AAA)||13||COGA||y-Almost||AAA||COGA 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.||272||240||202||223||211||97||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||PASS||Yes||No||A||3.3.3|
|Plain language (enhanced)||41||COGA||Momentum||AAA||Many 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||266||236||197||210||179||211||177||149||209||245||135||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes|
|Meaningful Set||312||ePub||SomeInterest||A||This was sitting as an issue 162 for a long time, but didn't have a champion to field it to the group.||313||Yes||Yes||Yes||Yes||Yes||Yes||Pass|
|Support Personalization (AAA)||COGA||SomeInterest||AA|
|Provide Support (AAA)||32||COGA||SomeInterest||AAA||COGA is presenting it as AAA to get it in, based on oposition at higher levels. Mixed, some didn't want it included||274||242||204||224||211||129||Yes||Yes||Yes||Yes||Yes||Yes||Yes||AAA||3.3.5|
|Familiar Design (Minimum)||49||COGA||Low Activty||A||Most comments suggest to not include in WCAG or consider only at AAA||270||239||200||211||121||Yes||Yes||Yes||Yes||Yes||Yes|
|Manageable blocks||24||COGA||Low Activity||AA||Mixed, some didn't want it included||267||247||198||211||178||Yes||Yes||Yes||Yes||Yes||Yes||Yes|
|Pointer inputs with additional sensors||66||MATF||Yes||Momentum||A||Mature, comments addressed, hasn't gone to larger group yet||262||194||144||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||PASS|
|Linearization||58||LVTF||Yes||SomeInterest||A||Significant 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 SC||249||213||184||171||160||159||89||Yes||Yes||Yes||Yes||Yes||Yes||Yes?||Yes||COGA 51 LVTF 77|
|Plain language (Miniumum)||30||COGA||Yes||Momentum||AAA||Many 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.||266||236||197||210||179||211||177||149||209||245||135||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes|
|Extra Help||32||COGA||XTRA||AAA||"Easily Available"||Yes||Yes||Yes||Yes||Yes|
|Extra Symbols (AAA)||50||COGA||XTRA||Momentum||AAA||COGA 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.||268||237||211||115||Yes||Yes||Yes||Yes|
|Error Prevention (Legal, Financial, Data)||33||COGA||Yes||Momentum||A||Reduced to requiring a read only summary to financial or legal, so basically 3.3.4 with the extra summary|
|Printing - Pending||76||AAA||Edit||View||disussion ongoing||252||215||185||176||173||216||141||Yes||Yes||Yes||Yes|
|Undo - pending||38||AAA||Edit||View||Mixed, some didn't want it included, discussion about whether it should be scoped to data entry and steps in a process||273||241||203||224||211||163||Yes||Yes||Yes||Yes||Yes|
|Interruptions (minimum)||47||AA||Edit||View||The 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.||353||259||182||211||206||231||283||443||444||445||446||447||474||493||98||Yes||Yes||Yes||Yes||Yes||Yes||Yes||2.2.2 Pause stop hide (A)||2.2.4 Interuptions|