WCAG2ICT Task Force Teleconference -- 06 Jul 2012

<trackbot> Date: 06 July 2012

<scribe> scribe: Andi

Action items review <http://www.w3.org/WAI/GL/WCAG2ICT-TF/track/>

action-22?

<trackbot> ACTION-22 -- Gregg Vanderheiden to work with Pierce, Al, David, Loïc, Alex to draft proposal for 2.4.5 -- due 2012-07-06 -- OPEN

<trackbot> http://www.w3.org/WAI/GL/WCAG2ICT-TF/track/actions/22

<scribe> no progress on action-22 yet

action-23?

<trackbot> ACTION-23 -- Gregg Vanderheiden to ask WCAG WG to modify intent for 1.3.1 per proposal #2 -- due 2012-07-06 -- OPEN

<trackbot> http://www.w3.org/WAI/GL/WCAG2ICT-TF/track/actions/23

AS: WCAG did agree to modify intent although slightly differently than we proposed
... Andi will get the resolution from the WCAG minutes and include it in the action

action-24?

<trackbot> ACTION-24 -- Gregg Vanderheiden to work Loïc, Mike, David, Andi to work on definition of "interaction context" -- due 2012-07-06 -- OPEN

<trackbot> http://www.w3.org/WAI/GL/WCAG2ICT-TF/track/actions/24

<MichaelC> action-23: see http://www.w3.org/2012/07/05-wai-wcag-minutes.html#item02

<trackbot> ACTION-23 Ask WCAG WG to modify intent for 1.3.1 per proposal #2 notes added

<Loic> https://sites.google.com/site/wcag2ict/home/introduction-to-wcag2ict-application-note/context-of-interaction

LM: group has had many e-mails - seems to be converging on a definition
... haven't yet officially agreed - not yet sure it has resolved all of the issues

PK: comments to group working on "interaction context" definition - make sure it covers toolbar windows which behave a little differently

action-26?

<trackbot> ACTION-26 -- Peter Korn to draft new proposal for 2.4.2 to try to address Loic's suggestion -- due 2012-07-10 -- OPEN

<trackbot> http://www.w3.org/WAI/GL/WCAG2ICT-TF/track/actions/26

<korn> https://sites.google.com/site/wcag2ict/home/2-operable/24-provide-ways-to-help-users-navigate-find-content-and-determine-where-they-are/242-page-titled

PK: have a proposal ready for survey (#4)

Survey for 6th July <https://www.w3.org/2002/09/wbs/55145/JUL062012/results>

Frontmatter for WCAG2ICT

JB: to Bruce's comment about linking to editor's draft of "Understanding WCAG 2.0" - will be adding more links, including this one
... think we should accept Peter's suggested changes to the TOC
... to Alex's comment, "reinterpreting" might be out of scope per our charter

PK: agree with the point Alex is making, think we should take this, and a few other issues that have come up, to WCAG and ask for a change to our task force statement

MP: have several cases where we have not been able to see how something would apply

AS: +1 to PK's comment

JB: recommend going with Peter's suggested re-wording

RESOLUTION: accept grammatical edits and Peter's edit to Frontmatter

AL: request proposed language about "reinterpreting WCAG" be sent to WCAG working group

PK: think language needs work, think it would be more effective if we collect all of the issues before going to WCAG WG

JB: think the proposal would change the meaning significantly - like the idea of batching potential work statement changes together

AL: okay if we can keep it on the table as something to be surveyed at a later point in time

MP: suggest a page on the wiki to collect the items

PK: suggest a page on "potential issues with the WCAG2ICT TF work statement to bring to WCAG working group" ahead of the project plan

Meaningful Sequence (1.3.2)

PK: do like the shorter text proposed by Loïc
... think we should hold off on a final defintion of "content" because it's so cross-cutting
... use what's been suggested here with a note to ourselves to come back and revisit this one once we have a definition of content

PC: in documents, vital information is often presented in a place that is not in the focus order (example, watermark that says "Do not redistribute")
... other issue is how to deal with headers and footers - are they allowed to interrupt the flow of the page text, etc.

PK: think this is better addressed by a modification to WCAG 2.0 intent
... the reading sequence has to cover everything

<scribe> ACTION: Pierce to work with Peter to draft proposal for modification to 1.3.2 intent to cover the issue of content that is not read automatically [recorded in http://www.w3.org/2012/07/06-wcag2ict-minutes.html#action01]

<trackbot> Created ACTION-27 - Work with Peter to draft proposal for modification to 1.3.2 intent to cover the issue of content that is not read automatically [on Pierce Crowell - due 2012-07-13].

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) where content is interpreted to mean "information and sensory experience to be communicated to the user by means of ICT"

RESOLUTION: Accept 1.3.2 as amended 'This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) where content is interpreted to mean "information and sensory experience to be communicated to the user by means of ICT" ' and including the three note bullets proposed by Gregg.

Audio Control (1.4.2)

MP: notes Andi's proposal to address the issues

LM: would like to see this split into separate sentences for electronic documents and software user interface
... really like the "software user interface" words

AS: if we separate them, we have to define the terms and so far we have not been able to agree on that - suggest keeping them together for now and revisiting definitions later

PK: agree but for a different reason - this applies everywhere so keeping them together reenforces that point

BB: Access Board tried to separate these in 2010 ANPRM with no luck

'This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "web page" with "electronic document or software user interface" and " any content" with " any part of an electronic document or software user interface".'

RESOLUTION: Accept 1.4.2 as amended: 'This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "web page" with "electronic document or software user interface" and " any content" with " any part of an electronic document or software user interface".'

<Zakim> BBailey, you wanted to remind folks that Access Board tried this with 2010 ANPRM

LM: prefer "software user interface" to other "software" terms we have used for other SC

AL: assumption of multi-tasking environment with a screen reader - not the case in all ICT

AS: to Loïc's point about replacing all variations of "software something" with "software user interface", agree that we need to re-examine and consider whether it's appropriate to do that

PK: +1 to Andi's comment but think it would be okay to publish with different terms with an editorial note - perhaps get feedback
... also think we need a note on this and some other SC about platforms that automatically do this for built-in AT

JS: disagrees that there are cases where the audio should not have to be paused

AL: example of PA system with audio announcement to evacuate the building

MP: addressed in M376 - closed products - emergency situation

JB: to Peter's suggestion about not unifying terms for this first public draft - concern that it will affect understanding - prefer that we try to unify before publishing

PK: as time goes on, we are coming up with language we like better - should continue to do this until we get to the end of the SC before we go back and revisit any SC

MP: M376 has used "software that has a user interface" - so this might be one we could go ahead and look at

PK: suggest a bulleted list of the tasks we need to do before publish July draft and put this one on it

<scribe> ACTION: Andi to start a list of tasks that have to be done prior to publication [recorded in http://www.w3.org/2012/07/06-wcag2ict-minutes.html#action02]

<trackbot> Created ACTION-28 - Start a list of tasks that have to be done prior to publication [on Andi Snow-Weaver - due 2012-07-13].

Bypass Blocks (2.4.1)

MP: defer this one for now due to high number of "do not accept" responses

Focus Order (2.4.3)

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) where "Web Page" is interpreted to mean "Electronic Document or Software User Interface"

LM: +1 to Andi's edit

AS: also keep the Note with three bullets

RESOLUTION: Accept 2.4.3 as amended: 'This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "web page" with "electronic document or software user interface".'

Consistent Navigation (3.2.3)

MP: defer this one for now due to high number of "do not accept" responses

PK: encourage people who wanted to accept to consider Peter's edit

Consistent Identification (3.2.4)

PK: +1 to Andi's text - but think it works fine in this case

LM: substitute "a set of web pages" with "an electronic document or a softare user interface"

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) with “electronic document or software user interface” substituted for "set of Web Pages".

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) with " an electronic document or a software user interface" substituted for "a set of Web Pages".

<korn> Success Criteria 3.2.4: Components that have the same functionality within [an electronic document or software user interface] are identified consistently.

RESOLUTION: Accept 3.2.4 as amended: This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) with " an electronic document or a software user interface" substituted for "a set of Web Pages".

<korn> https://sites.google.com/site/wcag2ict/home/2-operable/24-provide-ways-to-help-users-navigate-find-content-and-determine-where-they-are/242-page-titled

- DRAFT -

WCAG2ICT Task Force Teleconference

06 Jul 2012

Attendees

Contents