wendyresolution: adopt Proposed wording for 2.5 Level 3 SC3: Additional context relevant assistance is available for text input. [this replaces the existing 2 level 3 criteria which move to techniques]scribe: andi Andi3.2 Proposal Survey Results http://www.w3.org/2002/09/wbs/35422/consistent-behavior0525/results wendyhttp://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/0717.html * Andi says "hi Joe"joeclark Hola. MichaelircMichael has left wai-wcag Andiresolution: Accepted accepted for GL 3.2 Level 1 SC 1 - "Any extreme change of context is implemented in a manner that can be programmatically determined." with the proviso that we re-write the definition of "extreme change of context" wendyresolution: delete from the benfits of guideline 3.2 "Using captions to note changes in speaker is beneficial for individuals who are deaf or hard of hearing and who may be unable to discern changes in speaker for audio-only presentations." greggircgregg has joined wai-wcag MichaelircMichael has joined wai-wcag Andiresolution: Proposal accepted for GL 3.2 level 2 SC: Components that are repeated on a set of delivery units occur in the same sequence each time they are repeated. wendymichael counter proposal for L2SC2 - Any component that can receive focus does not automatically activate when focus is received. * Andi asks - do I record how concerns are addressed in IRC or in the punch list? wendyfor this one or last one? Andi"for at least one presentation format" removed because it is addressed in conformance.Discussion: should this be Level 3? Resolution wording fixes this. MichaelircMichael has left wai-wcag Andiresolution: Proposal accepted for GL 3.2 Level 2 SC 2 - When any component receives focus it does not cause an extreme change in context. wendycurrent wording/proposed - Changing the setting of any input field should not automatically cause an extreme change in contextthat for l2sc3 Andiresolution: Proposal accepted for GL 3.2 Level 2 SC 3 - Changing the setting of any input field does not automatically cause an extreme change in context. wendyInteractive content that appears in multiple delivered units within the same context is associated with similar functionality wherever it appears.s/delivered/deliveryabove is a counter proposal to, 'Interactive content that appears in multiple delivered units is associated with similar functionality wherever it appears.' Andiresolution: Proposal accepted for GL 3.2 Level 2 SC 4 - Functional components that are repeated on a set of delivery units provide similar functionality wherever they appear. AndiircAndi has left wai-wcag AndiircAndi has joined wai-wcag Andiresolution: Delete GL 3.2 Level 2 SC 6 (The destination of each link is identified through words or phrases that either occur in the link or can be programmatically determined.) and combine the comcepts with the proposal for GL 2.4 Level 2 SC 4. ChristopheircChristophe has left wai-wcag MakotoircMakoto has left wai-wcag ChristopheircChristophe has joined wai-wcag MakotoircMakoto has joined wai-wcag wendyircwendy has left wai-wcag BeckyircBecky has left wai-wcag Andiresolution: Proposal accepted to delete GL 3.2 Level 3 SC 2 (Components that appear visually on multiple pages, such as navigation bars, search forms, and sections within the main content, are displayed in the same location relative to other content on every page or screen where they appear.) and include it appropriately in techniques.resolution: Delete GL 3.2 Level 3 SC 3 (When components such as navigation menus and search forms appear on multiple pages, users can choose to have those elements presented in a different visual position or reading-order.)resolution: Move GL 3.2 Level 3 SC 5 (When content is arranged in a sequence that affects its meaning, that sequence can be determined programmatically.) to 1.3 because using correct semantics fixes this problem. Is there another success criteria that addresses this?resolution: delete two editorial notes for GL 3.2 Level 3 SC