conformance levels

Hi Folks

We need to associate conformance levels  to each success criteria


Guidance can come from  https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-levels-hea 


Taken from there:


First, there are a number of conditions that must be met for a Success Criterion to be included at all. These include:
All Success Criteria must be important access issues for people with disabilities that address problems beyond the usability problems that might be faced by all users. In other words, the access issue must cause a proportionately greater problem for people with disabilities than it causes people without disabilities in order to be considered an accessibility issue (and covered under these accessibility guidelines).

All Success Criteria must also be testable. This is important since otherwise it would not be possible to determine whether a page met or failed to meet the Success Criteria. The Success Criteria can be tested by a combination of machine and human evaluation as long as it is possible to determine whether a Success Criterion has been satisfied with a high level of confidence.

The Success Criteria were assigned to one of the three levels of conformance by the working group after taking into consideration a wide range of interacting issues. Some of the common factors evaluated when setting the level included:
whether the Success Criterion is essential (in other words, if the Success Criterion isn't met, then even assistive technology can't make content accessible)

whether it is possible to satisfy the Success Criterion for all Web sites and types of content that the Success Criteria would apply to (e.g., different topics, types of content, types of Web technology)

whether the Success Criterion requires skills that could reasonably be achieved by the content creators (that is, the knowledge and skill to meet the Success Criteria could be acquired in a week's training or less)

whether the Success Criterion would impose limits on the "look & feel" and/or function of the Web page. (limits on function, presentation, freedom of expression, design or aesthetic that the Success Criteria might place on authors) (Lisa adds  -this is why alternative renderings and personlization is important - anything that could effect the look and feel should be achievable via personlisation as well, so this is not a limitation) 

whether there are no workarounds if the Success Criterion is not met



I suggest the following levels


Importance
 Clarity
 Testability
 User agent support (last)
  
 Use semantics and safe standardized techniques that enable the content to be adapted to the user scenario including enabling additional support and personalization.
 Alt: Expose semantics that enables content adaptation in response to user preferences.
 Alt: Expose contextual information and element types that can be used to enable additional support and personalization, Contextual information includes: context of elements; concept and role; importance; position in a process; information for simplification; type of element (such as type of distraction, type of help, type of transaction and type of reminder). 
  
 AA
 Do not expose user information in a way that can be exploited without informed consent
 Low
 Do not add mechanisms that are likely to confuse the user in a way that may do the user finasial legal or safety  harm and use appropriate  wcag techniques to keep the user safe.
  
 Expose time frame transactions can undone in a matien readable way 
  
 LANG
 Avoid hyphenated words and acronyms should be “Avoid acronyms”
 the meaning of each word should be clear from              the word's context, or programmatically determinable.
 
   
    SC current wording
    Level
    Reword
   
   Use semantics and safe standardized techniques that enable the content to be adapted to the user scenario including enabling additional support and personalization.
    AA
     
   
   Timed event are not used except for the situations listed below.
    A
    Keep as is
   
   Guideline 2.3 "Do not design content in a way that is known to cause seizures" should be changed to: 
 Guideline 2.3 "Do not create mechanisms that are know to potentially harm the user." 
 Exclusion: Mechanisms that are know to potentially harm do not include selling products know to be harmful. 
    NA
    Keep as is
   
   Do not expose user information in a way that can be exploited without informed consent
    AA
 Leave for now
     
   
   Do not add mechanisms that are likely to confuse the user in a way that may do them harm and use known techniques to keep the user safe.
    A
     
   
   Instructions, labels, navigation and important information are provided with a clear writing style that includes:
 (For all wording (other then exceptions): 
 An easy to understand tense and voice. Please refer to the exemptions for changes for a defined scope such as a different location or language. 
 Use short clear sentences with a maximum of one conjunction and two commas. 
 Choose words that are in general use for the context. Use words or phrases that are used more frequently unless this will result in a loss of meaning. There is an exception if this is found in user tests to make the content harder to understand. 
 Avoid hyphenated words and acronyms unless they are the common form to refer to the concept. -http://www.fltr.ucl.ac.be/fltr/germ/etan/bibs/vocab/cup.html
 Double negatives are not used 
 Reduce ambiguities by: 
 metaphors and non-literal text are not used or can be automatically replaced via an easy to set user setting and standardized technique. All meaning must be retained when non-literal text are replaced. 
 the meaning of each word should be clear from the word's context, or programmatically determinable. 
 On controls, links and buttons use words that identify their function. Function can be 
 The default term used for the function on the user platform or 
 The function of the button or link (such as "search" in place of "go") or 
 The destination of a link (such as "home" or "contact us") 
 In menus : 
 The text of each main menu item is easy to understand. 
 Each sub menu item is clearly associated with the main menu item under which it falls (This can be due being an industry or platform default) 
 In instructions
 Identifying each step in instructions, 
 Using specific and concrete wording in instructions, 
 Exemptions:
 There are times when passive voicing or other tense can be clearer. Other voicing may be used when it has been shown via user test to be easier to understand, more friendly or appropriate. 
 The present tense is not required when describing or discussing past or future events. 
 If the writing style is an essential part of the main function of the site, such as a literary work. 
 Where less common words are found in user testing to be easier to understand for the audience (user testing should included people with cognitive disabilities that could e in the target audience - need further definition ) 
 The writing style items may be replaced for a location or type of content were user testing has shown a more effective writing style to aid comprehension for people with cognitive disabilities. Such as for content written in a specific language. 
 The content will be penalized for not conforming to a given writing style (such as a dissertation or PHD proposal) 
    AA
     
   
   Provide a clear structure and layout (new guidline)
    NA
     NA
   
   Information is provided in manageable chunks, that include: 
 One idea per paragraph. (One sentence is enough for a paragraph.) 
 Have one point per sentence. Long sentences can often be broken up into short sentences or lists. If a sentence can use more than two clauses, it typically can be broken up.
 Lists are used appropriately (COGA Techniques 2.1.1) 
 For audio or visual media 
 Media that is over five minuets is divided into programmatically determinable and logical sections. Each section must be navigable to and provided with a unique label that describes the section. (removed For multi media, the user can directly navigate to each section of the content. )
 Exception: If a specific structure is an essential part of the main function of the site. 
    AA
     
   
   Add to WCAG 3.2.4 Consistent styles are used for the same type of information and control (COGA Techniques 2.1.1). (see COGA Techniques 2.4)
 A consistent layout of common elements such as navigational elements, search and controls
 Consistent use of icons and controls such that the same icons and buttons serve the same function. Interactive controls with the same role are consistently presented across a set of web pages 
 ) 
 Exception: If a specific structure is an essential part of the main function of the site. 
    AA
     
   
   The main purpose of each page and section of content is obvious. Extraneous information that is not relevant to the main purpose of each page is separated in the modality of the user and pragmatically determinable. 
    AA
     
   
   Provide a clear and understandable layout that includes:
 Structure and relationships are obvious such that over 95
  of users can immediately identity the structure and relationships (COGA Techniques 2.1.1) 
 Paragraphs are clearly separated (white space in text or by a pause in speech content)
 Check use of appropriate punctuation between numbers when providing times as these may be read inappropriately by text to speech engines. (Example time)
 Provide a clear font or voice. A clear font or voice is one that is: 
 backed up by user research where coga users are part of the user testing or, 
 identified in a known WCAG technique or, 
 identified by the user preferences (preferred). 
 Exception: If a specific structure is an essential part of the main function of the site. 
    AA
     
   
   Interactive controls are visually clear or visually clear controls are easily available that conform to the following:
 Interactive controls are persivable in the modality of the user
 Interactive controls including links are visually discriminable and their boundaries are clear in the modality of the user. Boundaries on interactive controls and boundaries of icons should have a sufficient color contrast of 1.5 (visual only). 
 The qualities or properties of the control define its possible uses. It is clear how it can or should be used and what action it will trigger. Actions and actionable items that can be interacted with should have a clear visual style that indicates how to interact with them e.g. buttons that look like buttons. Visually clear controls can be made easily available though easy to use personlization (when available)
    AA
     
   
   A familiar design, layout and common icons are easily available. 
 A familiar design can be the user platform standard design or the design of a previous versions of this product that the user is familiar with and has successfully used. 
    AA
     
   
   Critical features and important information for the user is easy to find, such that: 
 Critical features and important information can be used without use of a scroll bar. (Example -above the scroll or a clear link to it is above the scroll )
 Critical features and important information to the user are visually differentiated and accentuated or appear before the other main content 
 A clear navigational path is provided to all content such that: 
 Clear headings, menu names and categories are available that signpost information. It should be clear how content correlates to each signpost in its navigation path. 
 Each page can be reached though any high level page that it logically could belong. 
 Help and support page or function should be reachable with one user interaction. When human help is available the correct contact information or mechanism should be reachable within two user interactions. (Removed: Where human help is provided, it is available via one clearly labeled action for each web related modality for which the help is available.)
 Provide a search box. Exception is provided were adding a search box is a significant expense for the site 
 define: content most likely to be important to the user
    A
     
   
   All information is easy to find (AAA )
    AAA
 Leave for now
     
   
   When there is a barrier between the content and the user that requires additional abilities an alternative is provided that does not require additional abilities.
 Additional abilities include cognitive functions that are required, but are not necessary to achieve the main task for which the content was designed. Such as: 
 Capture or security mechanisms that require copying, spelling or memory skills, 
 Interactive communication systems, voice menu systems such as Voice XML automated customer service portals, which require the user to have a good working (transitory) memory. The user needs hold pieces of transitory information in the mind such as the number that is being presented as an option, whilst processing the terms that follow. 
 Hiding of critical features under categories that are hard to understand. Such as a Web Of Things interfaces, that requires the user to understand the word "mode" to get to easy to understand options. 
 Exception: There is an exception when there is a not a known alternative that provides the same main function and does not rely on additional abilities. A known alternative can be a WCAG technique, W3C note, or in the documentation of the platform. 
    A
     
   
   Provide mechanisms that help the user focus and maintain or restore context if the context is lost.
 (Remove uncertainty and help the user maintain context) 
 This includes: 
 Use known techniques that remind the user of the context, including: 
 Signposts to remind the user of the current task and subtask. Signposts should not distract the user when they choice to change tasks without the users concent. 
 In the scope of a task, provide a signposts of broader context. For a non-complicated task, such as reading a home page, clearly identifying the site and it's aim is sufficient. 
 For multi media,  provide a unique label for each section such that the labels can provide an outline of the content. 
    A
     
   
   Where a site may generate interruptions, a clearly labeled mechanism is provide to enable the user to control them,(COGA Techniques 2.11.1) such that: 
 Interruptions can be easily controlled and turned off 
 Secondary content (such as special offers or complementary material) can be easily identified, controlled and turned off. 
 No sudden changes occur on the site. 
 Media events can be easily controlled and turned off. 
 Chat can be easily turned off and on again. 
 Non-critical messages can easily be turned off and on again 
 Where a standard techniques exists for the above it should be used. 
     
     
   
   The success or failure of every action should be clearly indicated to the user and visual rapid feedback should be available. Spoken feedback should be a user selectable option.
  
    AA
     
   
   Support known standardized APIs for tools that help the user understand and use the content. This includes:
 Standardized techniques to support interoperable symbol sets are used when available. 
 Allow reading of long form of acronyms
 Support for text to speech with synchronized highlighting of the phrase being read, and conent simplification 
 Support for retaining content that has already been entered and password management
 Exception: when there is a security or safety requirement to disable these apis for a specific field - such as credit card numbers
    A
     
   
   Provided content and information that help users understand the content
 For icons and jargon
 All icons and jargon have a short explanation available Where a standard mechanism exists for the platform or technologies it should be used.(COGA Techniques 2.7. )(removed to techneque: Short tooltips on all icons and jargon that clarify the meaning are provided.. )
 For content relating to numbers and complex information
 Charts or graphics are provided where they aid the comprehension of complex information (COGA Techniques 2.7.3 ) 
 Tables are provided where they aid the comprehension of information 
 Where an understanding of math is not a primary requirement for using this content. Reinforce numbers with non-numerical values, e.g., Very Cold, Cold, Cool, Mild, Warm, Hot, Very Hot. 
 For content with more then 200 words 
 Provide a summary. For pieces of content with less then 200 words the heading may act as a summary. 
 The content owner identifies at least two keywords that aid comprehension for the user and keywords are programmatic determinable and emphasized in the modality of the user. 
 For key content and call out boxes
 Symbols are provided to help the user identify key content including: types of contact information, main functions, warnings, key points. Where a standard mechanism exists for the platform or technologies it should be used. 
 For events
 Enable the user to set a reminder for date and time sensitive events. Reminders should be set only at the users request and the user should be able to personalize the reminder method. Where a standard mechanism exists for the platform or technologies it should be used
 For forms and non standard controls
 Where a standard mechanism for the platform or technologies exist for context sensitive help it should be used. (Simple search forms are excluded.)
 Instructions should be available for non standard controls 
    AA
     
   
   Prevent the user from making errors
 In forms
 Use known techniques to prevent errors that are relevant to the content. All standard ways of representing information are accepted as input formats, such as different ways of writing a phone number and date formats. 
 Documented common input errors can be corrected automatically. (example spelling mistakes)
 Enable and identify the default format and standards of locale and allow for change of format on labels and user input (removed use the default format and standards of locale and allow for change of format)
 Clear visual indicators are provided that identify what information is essential, and non-essential information is clearly differentiated from essential information. 
 Instructions are provided if there is not a label that fully describe the control or if it is not clear were to get the required information. Instructions should explain the purpose and usage of the control. (Graphics with a text alternative may be sufficient) ( A clear instruction or information is on where 99
  of your target audience understand immediately what to do) 
 For legal and finacial transactions
 Options that may disadvantage the user are only selected at the users specific request. 
 All types of charges must be clear at the start of a transaction task. 
 When a minimum is known for a type of charge it must be be made clear at the start of the transaction task. (from support the user)
 For all content
 Non native content and sponsored content are clearly marked and visually differentiated by standardized techniques 
 Clearly differentiate between facts and less substantiated opinions. Was rewritten from "Clearly differentiate between opinions and facts "
    A
     
   
   Support is provided that help users check their task and repair their work
 A simple mechanism is provided to allow the user to undo mistakes. The user can repair information via a clearly labeled action and get back to the place they were at, in one clearly labeled action with unwanted loss of data. 
 A user can go a step back in a process via one clearly labeled action (exceptions may be required) 
 A summary is provided before submitting important information and the user is notified that they are about to submit the final information. (already in wcag as an option, but this is the best option for coga) -note we could lose this builet point and change WCAG 3.3.4 to be for important information AND just summary
 Time frames for canceling transactions are matien readable. 
    A
     
   
   Provide mechanisms that help the user focus and maintain or restore context if the context is lost.
 (Remove uncertainty and help the user maintain context) 
 This includes: 
 Use known techniques that remind the user of the context, including: 
 Signposts to remind the user of the current task and subtask. Signposts should not distract the user when they choice to change tasks without the users concent. 
 In the scope of a task, provide a signposts of broader context including steps completed, current step and steps pending. For a non-complicated task, such as reading a home page, clearly identifying the site and it's aim is sufficient. 
    A
     
   
   Where a site may generate interruptions, a clearly labeled mechanism is provide to enable the user to control them,(COGA Techniques 2.11.1) such that: 
 Interruptions can be easily controlled and turned off 
 Secondary content (such as special offers or complementary material) can be easily identified, controlled and turned off. 
 No sudden changes occur on the site. 
 Media events can be easily controlled and turned off. 
 Chat can be easily turned off and on again. 
 Non-critical messages can easily be turned off and on again 
 Where a standard techniques exists for the above it should be used. 
    AA
     
   
   



All the best

Lisa Seeman

LinkedIn, Twitter