SC current wording

Level

Proposed 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

Support personalization: Contextual information and author settable properties of regions and elements  are programatically determinable so that personalization and simplification is available.

Where the number of steps in a process can be reduced, allow the user can control the trade off between function and simplification.

Contextual information includes: context of elements; concept and role; relevance and information for simplification; position in a process.

Author settable properties includes: type of distraction, type of help, type of transaction and type of reminder, instructions and status of an element.

Exception: Information does not need to be exposed when there is not a standardized way of  exposing it in the technology or the platform.

Add to befits, rendered 

Done

Timed event are not used except for the situations listed below.

A

merge with change from 2.2.1

Timed event are not used except for the situations listed below.

(See COGA Techniques 2.9.1 )

1. Security Exception:Where security may be at risk a session can time out after half an hour of disuse. Where financial or sensitive information is at risk the time out can be shorter
2. Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
3. Essential Exception: The time limit is essential and extending it would invalidate the activity; or
4. 20 Hour Exception: The time limit is longer than 20 hours of disuse.

Where there is a Security Exception or 20 Hour Exception the content must also conform to all of the bellow:

1. No loss of data: The user can easily return to the same point in a task, without data loss for a period of at least a week:
   1. as the default
   2. via standardized system setting (example the user can set that the data is not stored)
   3. option to set user preference that has a conformant interface and is directly available at each stage of the task.
2. Timing adjustable The function to turn off, adjust or extend the timing are controlled by simple action and labeled with simple text. A user or administrator settable time minimum must be provided to complete any controlling action or the user must be given at least 120 seconds to extend the time limit. The the user is allowed to extend the time limit at least ten times. Note that all user setting must be easy to set and use standardized techniques when available.
3. Awear: The user should be informed of the time out limits, including the length of the warning

Techniques include: Techniques with examples are needed such as a dialog on opening the app that seas do you want your old stuff

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

Safe

Use known techniques to keep the user information safe and warn the user of any known risk.

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

Do not automatically choose options that may disadvantage the user without their approval or add mechanisms that are likely to confuse the user in a way that may do them harm.

------------------

and added to the SC above

Instructions, labels, navigation and important information are provided with:

(For all wording (other then exceptions):

Present simple tense and active voicing. Please refer to the exemptions for changes for a defined scope such as a different location or language.

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)

A and AA

 divide into two:

Understandable language: Provide clear language in instructions, error messages that require a response to continue,  labels, and navigational elements (level A)

For instructions,  labels, and navigational elements:

-Simple tense: Use the present tense and uses active voicing. (See exceptions for different context and language.) 

-Simple and clear words: Use words or phrases that are used more frequently unless this will result in a loss of meaning or clarity. Where word frequencies are known for the context, they can be used.  This includes not using abbreviations words and phrases unless they are the common form to refer to the concept for beginners.

-Double negatives are not used

-Literal text: metaphors and non-literal text are not used or can be automatically replaced via an easy to set user setting. All meaning must be retained when non-literal text are replaced.

Also on controls:

The words on controls and labels  identify the elements  function.

Also on instructions:

Each step in instructions are identified and concrete wording is used.

(tecneques - 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")

falier technequereplacing words with pronowns as this decreases clarity

faluer - requiriring the user to learn new terms or meaning for terms or symbols

)

Exceptions:

• 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.
• There exception  an where present tense and active voicing does not exist or is  not clearer in the language of the content. In this case use the tense and voicing that is clearest for the content.
• 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  a game or literary work or teaching new terms.
• 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 ) 
• There is an exception if this is found in useability tests to make the content harder to understand. 
• 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 CV, dissertation or PhD proposal)

-----------------------------------------------------

 Understandable language: Do require the user to use unusule language and provide clear language in headings, important information that includes: (level AA)

-Simple tense: Use the present tense and uses active voicing. (See exceptions for different context and language.) 

-Simple and clear words: see above

-Double negatives are not used

-Literal text: metaphors and non-literal text are not used or can be automatically replaced via an easy to set user setting. All meaning must be retained when non-literal text are replaced.

Exceptions:

• 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.
• There exception  an where present tense and active voicing does not exist or is  not clearer in the language of the content. In this case use the tense and voicing that is clearest for the content.
• 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  a game or 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 ) 
• There is an exception if this is found in useability tests to make the content harder to understand. 
• 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 CV, dissertation or PhD proposal)

--

add to important information - finacancal

failuer : the wiki rewuiring new mark up

Done

Provide a clear structure and layout (new guideline)

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

AA

Manageable blocks of information: Information is provided in manageable blocks that include:
A single point per paragraph: A paragraph should consist of one or more sentences that deal with a single point.
Short sentences:   Sentence have a maximum of one conjunction and two commas. A sentence should consist of a single point or sub point 
Lists are used appropriately:  When there are three or more consecutive items that  could be considered  a list, a list is used.

For audio or visual media

Manageable segments of audio and visual media: Media is divided into a programmatically determinable and logical sequence. Media segments should be:
Six minutes or less: Media should be divided into segments that are 6 minutes or less in duration.
Programmatically determinable and logical: Media should be presented in a programmatically determinable and logical order.
Navigable: Navigation to each segment and a unique descriptive label is provided for each media segment.

Exception: A specific structure is an essential part of the main function of the site.

Where Usability testing have found a longer sentence to be clearer or easier to understand

(alt wording for 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. 

Additional references

References:
Segmenting video - https://cft.vanderbilt.edu/guides-sub-pages/effective-educational-videos/#seg (Philip Guo, Assistant Professor of Cognitive Science UC San Diego, et al 2014)
Optimal length is 6 minutes or shorter - http://blog.edx.org/optimal-video-length-student-engagement (Analysis by Philip Guo, Assistant Professor of Cognitive Science UC San Diego)

-----------

Done

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

change 

to

add to 

. 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. Component that have same type of information and controls with same functions are styled consistently within a set of web pages in the primary modality of the content.

Exception: If a changing style is an essential part of the main function of the site

(note this is ayelets sc -you do not need to do it)

 (define the primary modality of the content as modalities considored in the design of the content)

3.2.3 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 elements such as navigation, search and controls are have a consistent layout and position within a set of web pages in the primary modality of the content. .

Exception: If an inconsistent layout is an essential part of the main function of the site

define the primary modality of the content as modalities considored in the design of the content

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

SC Text:

clear structure and relationships: Information, structure and relationships conveyed through presentation provide for a clear and unambiguous separation of content and identification of relationships between elements. 

Exception: If a specific structure is an essential part of the main function of the site.

Techneques

• For Paragraphs: Paragraphs are clearly separated (white space in text or by a pause in speech content).
• For sub menues: Each sub menu item is clearly associated with the main menu item under which it falls.
• For search or tool bars: A search box or tool bar is clearly associated with the contents it will search.
• The relationship between a scroll bar and the contents it will scroll is clear and can not be confuced

clear test and voice: Use clear typography (text), punctuation (text) and voice (speech) for readability and comprehension.

Exception: If a specific typography, text or voice is an essential part of the main function of the site.

Techneques 

• Use clean, simple typography with good spacing, appropriate kerning and leading to separate text.
• Use darker weight fonts.
• Avoid using all capital letters. 
• Avoid using figures of speech, jargon and idioms.
• Use appropriate punctuation and spacing when representing numbers and times.

Note: Clear typography (font ), punctuation 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).
• defined by an international standard.

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

clear controls​: Interactive controls are clear or clear controls are easily available though personlization.  Boundaries on a interactive controls and icons should have a sufficient color contrast of 1.5 (visual only) or can be emphasized in the primary modality of the content. Auditory  emphasis can include slightly louder content, a change in the pitch or  a change in the voice . 

Interactive controls are available in  a standard  style that indicates how to interact with them or have clearly labeled instructions that explains their use 

definition: slightly louder is typically 5 db?, but  difference will notice issufficient   

Exemptions:

If the style is an essential part of the main function of the site, such as a for a game

techniques:. buttons that look like buttons. 

Done

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

Familiar layout: Navigation mechanisms and common icons are easily identifiable and available to the user in one or more of the following ways:
-Platform specific: A platform specific user interface design.
-Adaptive: An adaptive user interface design. 
-User interface from a prior version: A user interface design that was used successfully by users in a prior version of the application. 

 (level AA)

(Alternative wording

A familiar  layout of navigational elements and common icons are easily available such as: the standard for the  user platform or,  a previous versions of this product that the user is familiar with and has successfully used.)

ADD also

at level A

Familiar layout: Help, navigation to help and search forms are easily identifiable and available to the user in one or more of the following ways:
-Platform specific: A platform specific user interface design.
-Adaptive: An adaptive user interface design. 
-User interface from a prior version: A user interface design that was used successfully by users in a prior version of the application.

(help includes contact us and the helptypes)

Done

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

1:
Critical features and important information are above the fold and are accentuated in the main modality of the content.

Auditory  emphasis can include slightly louder content, a change in the pitch or  a change in the voice.

define critical features as features that are required to complete the main tasks of the content

define the primary modality of the content as modalities considored in the design of the content

-------------

SC 2:
change the wording of WCAG 2.4.10 and
Upgrade to AA

TO

Section Headings: Section headings are provided that organize the content. (Level AAA)

Add technique to 2.4.10: That the headings can be invisible or hidden by the user and can be included when needed using personalization and semantics. we may need supporting sematics to do that. However this makes the SC widely applicable and able to be level AA (needs to be in the write up)

 (Note that Clear headings are covered by 2.4.6 no changes needed)

----------------

SC 3:

Finding help: Help content, support page or support function is reachable with one user action. When human help is available the correct contact information or help is reachable within one user action for voice menus and a maximum of two user actions in other modalities. 

----------------

SC 4:
Provide a search capability.
An exception is provided for small organizations and organizations with small websites that includes simple links to each page from the home page . Note: A small organization is defined as not more than 50 employees, or a balance sheet total of less than 3.26 million, or the definition within your jurisdiction.

 ---------------

 SC 5: ---leave as pending for now------
Signposts are used for menu items and categories to assist users while navigating a Web page. The signposts are provide a clear navigation path that helps the user understand how content correlates to each signpost. 

--------------

donish

(one pending)

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,

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.

Intent

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.

A

pending

(mike)

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.

note - this should be added to 2.2.4 Interruptions: Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA) and the ,level change to AA

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

 Proposed wording

The success or failure of every user initiated action is clearly indicated to the user by visual, programmatically determinable, rapid feedback. Audio feedback is a user selectable option.

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

pending.

(Katie)

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 technique: 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, types of help, types of  main functions, warnings, key points,errors, system messages, notes, definitions, more information , table of content and site map, file types, search. 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

split into 5

------

change 3.3.5 Help: Context-sensitive help is available. (Level AAA)

to 

3.3.5 Help: (AA)

Provided content and information that help users understand complex information , long documents, numerical information, relative and  cardinal directions, forms and non standard controls. 

Where an understanding of math is not a primary requirement for using this content  reinforce numbers with non-numerical values. 

Simple search forms are excluded.

define: long doctumenets 300 words or more

complex information: something with at least 3  parts where at least 2 of  those parts interact with each other in multiple ways,

(move the rest to tqueques

were suffient techneques can be more then one)

-------------------

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

----------------------------

Consistent cues are provided that identify  different content types and the status of element and regions that help the user understand it's role or state.

definition of content types include:  types of contact information, types of help, types of  functions, warnings, key points, errors, system messages, notes, definitions, more information , table of content and site map, file types, search. required information, errors, opinions,  essential information types of transaction and type of reminder, instructions and status of an element, invalid fields , non native content and sponsored content are clearly marked and visually differentiated by standardized techniques

techneques

Symbols are avalalible that help the user identify key content including: types of contact information, types of help, types of  main functions, warnings, key points, errors, system messages, notes, definitions, more information , table of content and site map, file types, search. required information, errors, opinions,  essential information  invalid fields.

add faluer techneque of adding a star next to non native content, as that does not help the user understand it is non native.

----

level A - provide begginer help or easy access to humen help on forms and interactive controls for critcal services

----------

AA - provide begginer help and easy access to humen help on forms and interactive controls for critcal services

-----------

done

Prevent the user from making errors

In forms

Use known techniques to prevent errors that are relevant to the content.

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

 split into 4

----

change 3.3.3 Error Suggestion:

to

3.3.3 Minamize user errors 

 Identify common input errors​.  If an input error is detected  an automatic correction is made where reilable and possible . Otherwise if suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. 

techquese can be made ally correct known format errors

(confirm that spelling correction is in supported api's)

define common input errors as errors that have been reported or documented more then one time, or have been doumented in the understand the SC section or have supportive  techeques

---------

Change 3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A)

to

3.3.2 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 localsed 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 were to get the required information. An exception is provided where the information is know by the intended audience (such as the users name )

Define: know by the intended audience as participates in a user study that includes some people with memory, language and attention disabilties. 

(techneques 

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)

-----

Identify Charges

All types of charges and condition are identified  at the start of  transaction tasks. When a minimum or typical value is known for a type of charge it must be be made clear at the start of the transaction task. 

------------

notes

moved to mecanisims that may do hard

- D)o not automatically choose options that may disadvantage the user without their approval. (

-

techniques

Graphics with a text alternative may be sufficient) ( A clear instruction or information is on where 99

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)

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 bullet point and change WCAG 3.3.4 to be for important information AND just summary

Time frames for canceling transactions are machien readable.

A

split into 2

--Undo: 

A user can  go back steps  in a process via a clearly labeled action.

The user can repair information via a clearly labeled action and get back to the place they were at, in a clearly labeled action without unwanted loss of data.

(exceptions may be required)

--------

Change

3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitmentsor 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: (Level AA)

1. Reversible: Submissions are reversible.

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 mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

to

3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitmentsor 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: (Level AA)

1. Modify: A simple mechanism is provided to allow the user to asses 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 programiticaly detemined 

done

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

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.

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.

A

Split into three (see bellow)

 add to SC on page pourpose  (DO not make a new SC - STeve will add this...)

In the scope of a task, signposts should include the 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. 

Signposts should not distract the user when they choice to change tasks without the users concent.

define sign post: an immediately perceptible indicator or obvious clue, that gives information

---------------------

Change 2.2.4 Interruptions: Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA)

to 

Interruptions and Media events can be easily  identified, turned off and turned on again, except critical messages and interruptions involving an emergency.  Use standard techniques when availible.

notes

define interruptions,

-------------

Upgrade 3.2.5 Change on Request: Changes of context are initiated only by user request or a mechanism is available to turn off such changes. 

to

Change on Request: Changes of context, functionality, settings and roots are initiated only by user request or an easy to use mechanism is available to turn off such changes. An easy to use mechanism is available to go to the prevoise context. An exception for were it is crucial  to the main usecase of the site (such as a game)

AA

done