W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2010

Minutes: User Agent Teleconference for 4 February 2010

From: Greg Lowney <gcl-0039@access-research.org>
Date: Thu, 04 Feb 2010 11:51:08 -0800
Message-ID: <4B6B252C.6020403@access-research.org>
To: WAI-UA list <w3c-wai-ua@w3.org>
http://www.w3.org/2010/02/04-ua-minutes.html

W3C <http://www.w3.org/>


  - DRAFT -


  User Agent Accessibility Guidelines Working Group Teleconference


    04 Feb 2010

See also: IRC log <http://www.w3.org/2010/02/04-ua-irc>


    Attendees

Present
    allanj, Jeanne, [Microsoft], Bim, Greg, sharper, +1.617.435.aaaa,
    Kim, Markku_Hakkinen
Regrets
Chair
    Jim_allan, Kelly_Ford
Scribe
    Greg


    Contents

    * Topics <http://www.w3.org/2010/02/04-ua-minutes.html#agenda>
         1. Review Action Items -
            http://www.w3.org/WAI/UA/tracker/actions/open
            <http://www.w3.org/2010/02/04-ua-minutes.html#item01>
         2. F2F - 2/24-26 -
            http://www.w3.org/2002/09/wbs/36791/20100119/
            <http://www.w3.org/2010/02/04-ua-minutes.html#item02>
         3. 3.1 & 4.9 brainstorming
            <http://www.w3.org/2010/02/04-ua-minutes.html#item03>
    * Summary of Action Items
      <http://www.w3.org/2010/02/04-ua-minutes.html#ActionSummary>

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

<trackbot> Date: 04 February 2010


      Review Action Items - http://www.w3.org/WAI/UA/tracker/actions/open


      F2F - 2/24-26 - http://www.w3.org/2002/09/wbs/36791/20100119/

So far Jim, Greg, Jeanne, and Kelly have signed up to attend in person.

So far, Patrick is signed up to attend remotely.

<jeanne> *ACTION:* JS to set up a conference bridge for F2F for 3 
[recorded in http://www.w3.org/2010/02/04-ua-minutes.html#action01]

<trackbot> Created ACTION-276 - Set up a conference bridge for F2F for 3 
[on Jeanne Spellman - due 2010-02-11].

Jim will look into arranging a get together with other accessibility 
people in the Austin area, perhaps on Thursday evening.


      3.1 & 4.9 brainstorming

Patrick gave an overview of the proposed changes to 3.1.1 - 3.1.5 that 
he sent in email.

<kford> On first read this sounds pretty good to me.

Greg suggested removing the bit about mechanism to display alternative 
content from the example of discoverability, as it's more appropriate to 
3.1.3.

Discussion of pros and cons of terms "notification" vs. "discoverability".

How about "Indicating Available Alternative Content"?

<kford> /me are we using the queue at all?

<patrickhlauke> oops soz

Kelly queries whether we should explicitly say "visual or audible" 
queues, or leave it more general.

<AllanJ> +1

<AllanJ> +1 to putting the information (visual, etc) in the techniques

<AllanJ> + 1 'indicating' or 'indicate'

Agreed to title like "Indicate available alternative content".

<patrickhlauke> 3.1.1 Indicate Alternative Content: Provide a global 
option for the user to receive cues in the presence of alternatives to 
rendered content (e.g. visual icons rendered in proximity of content 
which has short text alternatives, long descriptions, captions).

<kford> Good here.

<jeanne> *ACTION:* JS to update document with new 3.1.1 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action02]

<trackbot> Created ACTION-277 - Update document with new 3.1.1 [on 
Jeanne Spellman - due 2010-02-11].

<kford> 3.1.2 good here too.

Agreed on Patrick's proposed version of 3.1.2 Configurable Default 
Rendering: Provide the user with the global

option to set which type of alternative to render by default and, in 
cases where the alternative content has different dimensions than the 
original content, how the layout/reflow of the document should be 
handled. (Level A)

<jeanne> *ACTION:* JS to update document with new 3.1.2 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action03]

<trackbot> Created ACTION-278 - Update document with new 3.1.2 [on 
Jeanne Spellman - due 2010-02-11].

<AllanJ> GL: what is difference between 3.1.2 and 3.1.3

<AllanJ> ... one is about defaults globally, one is about overiding 
default rendering on case by case basis

<patrickhlauke> how about:

<patrickhlauke> 3.1.3 Browse and Render: The user can browse the 
alternatives, switch between them, and render them according to the 
following (Level A):

Re 3.1.3, Jim discussed the concept of an alternatives stack, meaning 
that there can be several alternatives for a given piece of content, and 
notes that original image becomes alternative content to the alt text 
when the latter is displayed.

<AllanJ> 3.1.3 Browse and Render: The user can browse the alternatives, 
switch between them, and render them according to the following (Level A):

<AllanJ> (a) synchronized alternatives for time-based media (e.g., 
captions, audio descriptions, sign language) can be rendered at the same 
time as their associated audio tracks and visual tracks, and

<AllanJ> (b) non-synchronized alternatives (e.g., short text 
alternatives, long

<AllanJ> descriptions) can be rendered as replacements for the original 
rendered content.

<jeanne> *ACTION:* JS to update document with revised 3.1.3 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action04]

<trackbot> Created ACTION-279 - Update document with revised 3.1.3 [on 
Jeanne Spellman - due 2010-02-11].

<AllanJ> Include "If the new item has different dimensions, then a user 
option controls whether the dimensions of the original content are used 
***(including an indication of, and accessible scrolling or expansion 
mechanism for, alternative content in cases where the alternatives 
exceed these original dimensions) *** or the dimensions of the new 
content, which will cause the document to reflow...

<AllanJ> ...accordingly."

Re 3.1.4, suggest we replace it with a Note referring the reader to 
2.1.2, in the section on programmatic access, which could be modified to 
more explicitly include alternative content. For example: 2.1.2 Name, 
Role, State, Value, Description: For all user interface components 
including the user interface, rendered content, and alternative content, 
make available the name, role, state,...

scribe: value, and description via an platform accessibility 
architecture. (Level A)

<AllanJ> *ACTION:* Jallan to write flash or canvas fallback content use 
case for intent for GL3 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action05]

<trackbot> Created ACTION-280 - Write flash or canvas fallback content 
use case for intent for GL3 [on Jim Allan - due 2010-02-11].

(The only change in that version is replacing "user interface and 
rendered content" with "user interface, rendered content, and 
alternative content.")

<patrickhlauke> +1

<AllanJ> new 2.1.2 language: 2.1.2 Name, Role, State, Value, 
Description: For all user interface components including the user 
interface, rendered content, and alternative content, make available the 
name, role, state,...

<AllanJ> ...value, and description via an platform accessibility 
architecture. (Level A)

<jeanne> *ACTION:* JS to update the document with new language for 
2.1.1, remove 3.1.4 and refer it to 2.1.1 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action06]

<trackbot> Created ACTION-281 - Update the document with new language 
for 2.1.1, remove 3.1.4 and refer it to 2.1.1 [on Jeanne Spellman - due 
2010-02-11].

Suggested combining 3.1.5 into 3.1.2 by replacing "type of alternative" 
with "types of alternatives".

<AllanJ> *ACTION:* jallan create a list of alternatives available for 
content for inclusion in the techniques [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action07]

<trackbot> Created ACTION-282 - Create a list of alternatives available 
for content for inclusion in the techniques [on Jim Allan - due 2010-02-11].

We do need to examine whether current user agents support 3.1.2 as 
written (singular) and as proposed (plural).

<AllanJ> 3.1.2 Configurable Default Rendering: Provide the user with the 
global option to set which types of alternative to render by default 
and, in cases where the alternative content has different dimensions 
than the original content, how the layout/reflow of the document should 
be handled. (Level A)

<AllanJ> make the simultaneous rendering an AA or AAA and model on 
current 3.1.5

Patrick is in favor of having 3.1.2 requiring display of one alternative 
at Level A and separately 3.1.5 recommending allowing display of 
multiple alternatives at Level AA.

Patrick will continue discussion of 3.1 offline.

rsagent, create minutes


    Summary of Action Items

*[NEW]* *ACTION:* jallan create a list of alternatives available for 
content for inclusion in the techniques [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action07]
*[NEW]* *ACTION:* Jallan to write flash or canvas fallback content use 
case for intent for GL3 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action05]
*[NEW]* *ACTION:* JS to set up a conference bridge for F2F for 3 
[recorded in http://www.w3.org/2010/02/04-ua-minutes.html#action01]
*[NEW]* *ACTION:* JS to update document with new 3.1.1 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action02]
*[NEW]* *ACTION:* JS to update document with new 3.1.2 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action03]
*[NEW]* *ACTION:* JS to update document with revised 3.1.3 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action04]
*[NEW]* *ACTION:* JS to update the document with new language for 2.1.1, 
remove 3.1.4 and refer it to 2.1.1 [recorded in 
http://www.w3.org/2010/02/04-ua-minutes.html#action06]
 
[End of minutes]
Received on Thursday, 4 February 2010 19:53:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 4 February 2010 19:53:15 GMT