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

Minutes of UAWG non-F2F Video conference of 9 November

From: Jeanne Spellman <jeanne@w3.org>
Date: Tue, 09 Nov 2010 16:54:59 -0500
Message-ID: <4CD9C333.8020601@w3.org>
To: UAWG <w3c-wai-ua@w3.org>
Minutes: http://www.w3.org/2010/11/09-ua-minutes.html

Summary of Action Items

    [NEW] ACTION: Greg figure out and or create SC for content reflow.
    [recorded in
    [37]http://www.w3.org/2010/11/09-ua-minutes.html#action01]
    [NEW] ACTION: JS to review document with Kim to adjust all verb
    tenses to present tense. [recorded in
    [38]http://www.w3.org/2010/11/09-ua-minutes.html#action04]
    [NEW] ACTION: JS to review document with Kim to insure that scope of
    Global vs. individual is correct for each SC. [recorded in
    [39]http://www.w3.org/2010/11/09-ua-minutes.html#action02]
    [NEW] ACTION: kford to ensure implementing doc addresses currency
    for 1.6.4. [recorded in
    [40]http://www.w3.org/2010/11/09-ua-minutes.html#action03]


Text of Minutes:
    [1]W3C

       [1] http://www.w3.org/

                                - DRAFT -

    User Agent Accessibility Guidelines Working Group Teleconference

09 Nov 2010

    See also: [2]IRC log

       [2] http://www.w3.org/2010/11/09-ua-irc

Attendees

    Present
           Greg, Jim, Jan, Jeanne, Kelly, Kim, Mark, Simon

    Regrets
    Chair
           KFord, JAllan

    Scribe
           jallan

Contents

      * [3]Topics
          1. [4]1.2.2 Repair Empty Alternatives
          2. [5]1.31 Highlighted items: The user has the option to
             highlight the following classes of information so that each
             is uniquely distinguished. (Level A)
          3. [6]1.3.2 Highlighting options: The highlighting options
             (with the same configurable range as the operating
             environment's conventional selection utilities) include at
             least (Level A):
          4. [7]1.4.1 (former 3.6.1) Configure Text: The user can
             globally set the following characteristics of visually
             rendered text content, overriding any specified by the
             author or user agent defaults (Level A):
          5. [8]1.4.2 Preserve Distinctions: The user can preserve
             distinctions in the size of rendered text when that text is
             rescaled (e.g. headers continue to be larger than body
             text) within absolute limitations imposed by the platform.
             (Level A)
          6. [9]1.5.1 Global Volume: The user can independently adjust
             the volume of all audio tracks the user agent renders,
             relative to the global volume level set through operating
             environment mechanisms. However, if audio is muted at the
             global level the user agent should not override this unless
             the behavior is optional, not enabled by default, and the
             user is cautioned as to its implications....
          7. [10]1.6.1 Speech Rate and Volume: The user can set in
             synthesized speech, overriding any values specified by the
             author (Level A):
          8. [11]1.6.4 The following speech features are provided (Level
             AA): (a) user-defined extensions to the synthesized speech
             dictionary, (b) "spell-out", where text is spelled one
             character at a time, or according to language-dependent
             pronunciation rules, (c) at least two ways of speaking
             numerals: one where numerals are spoken as individual
             digits and punctuation (e.g. "one two zero three...
          9. [12]1.6.4
         10. [13]1.7.1 Author Style Sheets: If the author has supplied
             one or more style sheets, the user has the following
             options (Level A):
         11. [14]1.8.1 Highlight Viewport: The viewport with the input
             focus (including nested viewports and their containers) is
             highlighted, and the user is able to customize attributes
             of the highlighted mechanism, including, but not limited
             to, shape, size, stroke width, color, and blink rate (if
             any). (Level A)
         12. [15]1.8.2 Move Viewport to Selection and Focus: When a
             viewport's selection or input focus changes, the viewport
             moves as necessary to ensure that the new selection or
             input focus location is at least partially in the viewport.
             (Level A)
         13. [16]1.8.3 Resizable: The user has the option to make
             graphical viewports resizable, within the limits of the
             display, overriding any values specified by the author.
         14. [17]1.8.4 Scrollbars: Graphical viewports include
             scrollbars if the rendered content (including after user
             preferences have been applied) extends beyond the viewport
             dimensions, overriding any values specified by the author.
         15. [18]1.8.5 Viewport History: If the user agent maintains a
             viewport history mechanism (e.g., via the "back button")
             that stores previous "viable" states (i.e., that have not
             been negated by the content, user agent settings or user
             agent extensions). It maintains information about the page
             and embedded controls, including viewport scrolling,
             selection and keyboard focus. It restores the...
      * [19]Summary of Action Items
      _________________________________________________________

    <trackbot> Date: 09 November 2010

    <kford> We believe we are placing the call now.

    <kford> we hear you and see you.

    <kford> Hey, do you have us muted?

    <kford> Do hyou have us muted?

    back in 15

    <kford> We don't see you any more

    <kford> We are going to reboot.

    <kford> We are probably 15 minutes ffrom being ready, apologies.

    <kford> We are calling again.

    <kford> just a second

    <kford> What kind of unit do youhave?

    <jeanne> tandberg

    <jeanne> zakim is confused because there are two UAAG calls at this
    time

    <jeanne> [20]http://www.w3.org/WAI/UA/2010/ED-UAAG20-20101105/

      [20] http://www.w3.org/WAI/UA/2010/ED-UAAG20-20101105/

    <Kim> Kelly: start with principle 1.1, provide access to alternative
    content -- look through subpoints

    <Kim> JR: too many examples -- as a general rule we should have as
    few examples as possible -- so it's not longer than the success
    criteria

    <Kim> GL: shorter and more conversational -- icons next to content
    with text alternatives or captions -- would that be short enough

    +1 to shorter

    <Jan> Idea: Identify Presence of Alternative Content: The user has
    the option of having indicators displayed with rendered elements
    that have alternative content (e.g. images with short text
    alternatives indicated with an icon)

    [21]http://irc.w3.org/

      [21] http://irc.w3.org/

    [22]http://irc.w3.org/

      [22] http://irc.w3.org/

    <Jan> Or shorter: Identify Presence of Alternative Content: The user
    has the option of having indicators displayed with content that has
    alternative content (e.g. an icon to indicate an image has a short
    text alternatives)

    do we really need an example in the SC??

    +1

    <Kim> 1.1.2

    <jeanne> Resolved: Renumber 1.1.2 & 3 to come before 1.1.1

    <Kim> GL: not sure we need globally

    the user can specify which types of content to render by default

    <Kim> 1.1 .3

    <Kim> KF: the user can browse the alternative -- the alternatives of
    what

    <Kim> GL: the user can browse for a rendered element

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

    <Kim> KF: it's got to be a plural

    <Greg> "For any rendered element, the user can browse..."

    <Kim> JA: must be associated with each piece of content

    <Kim> GL: what did we come up with for a summary

    <Kim> GL: I find the bold items difficult to read

    upshots
    [23]http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0007.h
    tml

      [23] 
http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0007.html

    Upshot: Let users see at a glance which pieces of content have
    alternatives like alt text or longdesc (3.1.1) and click on an item
    to see its available alternatives (3.3.3); they can also choose at
    least one alternative like alt text to be always displayed (3.1.2),
    but it's recommended that they also be able to specify a cascade,
    like alt text if it's there, otherwise longdesc, otherwise,...
    ... filename, etc.

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

    <Greg> "non-synchronized alternatives can be rendered as
    replacements for the original rendered content (e.g., short text
    alternatives or long descriptions for images)"

    <Greg> So the entire thing now would be be: "For any rendered
    element, the user can browse the alternatives, switch between them,
    and render them according to the following (Level A): * synchronized
    alternatives for time-based media can be rendered at the same time
    as their associated audio and visual tracks (e.g., captions, audio
    descriptions, or sign language for video or audio)* non-synchronized
    alternatives can be rendered as replacements for the original
    rendered cont

    <Greg> ""For any rendered element, the user can browse the
    alternatives, and choose at least one to be rendered according to
    the following ..."

    <Greg> The question is, do we want to require the user be able to
    see more than one alternative at the same time?

    <Jan> When a rendered element has alternatives, the user can control
    rendering of the alternatives according to the following:

    <Kim> KF: for any rendered element with alternatives

    <Greg> Could shorten the second clause to be "the user can control
    which are rendered", as we've already said we're talking about
    alternatives.

    <Kim> GL: still need to decide whether we want to explicitly require
    whether the user can see more than one at the same time

    <Greg> Another slight, shorter variation on Jan's wording: "For any
    rendered element, the user can control rendering of the
    alternatives"

    <Jan> For any rendered element, the user can control rendering ofany
    alternatives

    <Jan> For any rendered element, the user can control rendering of
    the alternative content

    <Kim> When a rendered element has alternatives, the user can control
    the alternatives according to the following:

    <Jan> When a rendered element has alternative content, the user can
    control the alternatives according to the following:

    +1

    <Jan> +1

    <Greg> "can have alternatives rendered according to the following"?

    <Greg> Just because "control" is a bit broad.

    <Kim> JR: long descriptions should be replaced, but for synchronized
    time-based media they can play at the same time

    <Kim> JA: different depending on the media type

    <Greg> So this only requires text alternatives *replace* images, not
    supplement images. Is there something else that requires or
    recommends the ability to have alternatives supplement the images?

    <Kim> JR: it does say can

    <Kim> JR: because only available through alternate screen readers
    they can be put on the screen -- particular use case we want to see
    although others are possible

    <Kim> GL: no mention of at the same time

    <Kim> JS: intent is clear -- doesn't mention

    <Kim> KF: Greg has raised an issue worth exploring, but not in this
    guideline perhaps. Do we want to encourage the display of all text
    and the image

    <Kim> KF: this was an option in a browser it might make people
    realize how crappy some of their alternate text is

    <kford> Issue: Do we need to encourage display of alt text and
    images at the same time.

    <trackbot> Created ISSUE-76 - Do we need to encourage display of alt
    text and images at the same time. ; please complete additional
    details at [24]http://www.w3.org/WAI/UA/tracker/issues/76/edit .

      [24] http://www.w3.org/WAI/UA/tracker/issues/76/edit

    <Kim> KF: 1.1.4

    <Kim> KF: cascade of types of alternatives is wordy

    <Jan> The user specify a preferred order of content alternatives to
    render by default. If the alternative content has a different height
    or width, the user agent will reflow the viewpor

    <Jan> The user can specify a preferred order of content alternatives
    to render by default. If the alternative content has a different
    height or width, the user agent will reflow the viewport.

    <Kim> KF: misses the point -- this is about making sure that it
    falls back when the first ones not there

    <Jan> The user can specify the fallback order in which to render
    content alternatives.

    <Jan> Maybe we should move "If the alternative content has a
    different height or width, the user agent will reflow the viewport"
    to the defn?

    <Greg> I think the instructions on reflowing are general and not
    repeated everywhere.

    <Jan> The user can specify the fallback order in which to render
    alternative content.

    <kford> ACTION: Greg figure out and or create SC for content reflow.
    [recorded in
    [25]http://www.w3.org/2010/11/09-ua-minutes.html#action01]

    <trackbot> Created ACTION-463 - Figure out and or create SC for
    content reflow. [on Greg Lowney - due 2010-11-16].

    <Greg> I'd still prefer "different types of alternative content" but
    I'll yield to the majoriyity.

    <Kim> KF: back to 1.11

    <Kim> 1.1.1

    <Jan> The user can have indicators rendered along with rendered
    elements that have alternative content (e.g. visual icons rendered
    in proximity of content that has short text alternatives, long
    descriptions, or captions).

    <jeanne> The user can specify which types of alternative content to
    render by default. (Level A)

    <Kim> The user can specify that indicators be rendered...

    The user can have indicators of alternative content rendered along
    with elements that have alternative content

    <Greg> Jan's most recent before that was "Identify Presence of
    Alternative Content: The user has the option of having indicators
    displayed with content that has alternative content (e.g. an icon to
    indicate an image has a short text alternatives)"

    <Kim> The user can specify that alternative content indicators be
    rendered...

    <Jan> The user can have indicators of alternative content rendered
    along with elements that have alternative content (e.g. an icon to
    indicate an image has a short text alternatives)

    <Greg> That sounds really repetitive, with "alternatve content"
    twice.

    <Jan> The user can specify that indicators be rendered along with
    elements that have alternative content (e.g. an icon to indicate an
    image has a short text alternatives)

    <Jan> The user can specify that indicators be rendered along with
    elements that have alternative content (e.g. an icon to indicate an
    image has a short text alternative)

    <Jan> The user can specify that elements that have alternative
    content be highlighted (e.g. an icon to indicate an image has a
    short text alternative)

    <Greg> We could use the term "highlight" which is defined as
    including both supplemental icons as well as outlines and other
    forms of visually distinguishing pieces of content.

    <Jan> The user can specify that elements with alternative content be
    highlighted (e.g. an icon to indicate an image has a short text
    alternative)

    <Greg> "The user can have elements highlighted to indicate that they
    have alternative content"

    The user can have indicators of alternative content rendered along
    with elements that have alternative content

    <Kim> The user can specify that alternative content indicators be
    rendered along with elements that have alternative content (e.g. an
    icon to indicate an image has a short text alternative)

    +1

    <kford> +1

    <jeanne> +1

    <sharper> +1

    <Jan> +1

    <Greg> I dislike it but OK

    greag meant to say ~1

    <Greg> -1

    <Greg> I can say -1 since you don't need consensus :-)

    <Kim> 1.2.1

    [26]http://www.w3.org/WAI/UA/2010/ED-UAAG20-20101105/

      [26] http://www.w3.org/WAI/UA/2010/ED-UAAG20-20101105/

    <Greg> We don't say "receive" anywhere else in the document.
    Elsewhere we always talk about having things rendered.

    <jeanne> Repair Missing Alternatives: The user can receive generated
    repair text when the user agent recognizes that the author has not
    provided alternative content required by the technology
    specification (e.g. short text alternative for an image). (Level A)

    <Kim> JR: we don't define how it should be repaired

    <Greg> We also want to the user to be able to say they don't want
    generated repair text.

    <Greg> "The user can specify whether or not they want the user agent
    to generate and render repair text when it recognizes that the has
    not provided alternative content required by the technology
    specification (e.g. short text alternative for an image). (Level A)"

    <Kim> SH: not specific enough

    <Greg> "The user can specify whether or not the user agent should
    generate and render repair text when it recognizes that author has
    not provided alternative content required by the technology
    specification (e.g. short text alternative for an image). (Level A)"

    <Kim> JS: should the file name for an image

    <Greg> "The user can specify whether or not the user agent should
    generate and render repair text (e.g. file name) when it recognizes
    that author has not provided alternative content required by the
    technology specification. (Level A)"

    <Greg> So in response to Simon's concern, we could change it to:
    "The user can specify whether or not the user agent should generate
    and render repair text (e.g. file name) when it recognizes that
    author has not provided alternative content supported by the
    technology specification. (Level A)"

    <Greg> That is, "supported by the technology specification" instead
    of "required by"

    <jeanne> The user can specify whether or not the user agent should
    generate and render repair text (e.g. file name) when it recognizes
    that author has not provided alternative content. (Level A)

    <Kim> JR: what is it asking the user agent to do -- have the
    capacity to generate and repair text and under what circumstances

    <Greg> My only worry with that is that it might be too broad, e.g.
    forcing repair text for things (e.g. text) that normally have no
    defined alternatives.

    <Kim> JA: it can't give you things it doesn't know about

    <Kim> JA: if you do generate repair techs allow the user to turn it
    on and off -- that could be a level a thing

    <Kim> GL: it's not hard to generate repair text

    <Kim> JA: the file name is always given as an example, it's not what
    we are talking about exactly

    <Kim> GL: specification on repair text from one of the other working
    groups?

    <Kim> JR: repair text has to be human authored -- they should be
    providing all of this

    <Greg> Filenames and the like could be considered an attributes of
    an element rather than alternative content for it.

    <Greg> The user could ask the user agent to render some attributes
    of an element as repair text.

    <Greg> That takes care of Simon's concern that the repair text might
    be generic and not actually relevant or useful to the user.

    <Kim> SH: definition -- in good faith, maybe that's all we can do

    <Greg> Maybe not *entirely*, but at least partially.

    <Kim> JR: tools do need to provide a repair capacity, repair techs
    needs to do something at least as smart as providing the name of the
    resource file, end-users need to be able to turn it on and off
    because they may not find it useful

    <Kim> repair text

    <Greg> I note the definition of repair content says "UAAG 2.0 does
    not require user agents to include repair content in the document
    object." which seems a problem for assistive technology

    ***short break for lunch****

    <scribe> scribe: jallan

    gl: concerned about removing the caveat, and forcing UA to create
    alternative content for text

    <Greg> That is by removing the phrase "when it recognizes that
    author has not provided alternative content supported by the
    technology specification."

    previously, The user can specify whether or not the user agent
    should generate and render repair text (e.g. file name) when it
    recognizes that author has not provided alternative content
    supported by the technology specification. (Level A)

    The user can specify whether or not the user agent should generate
    and render repair text (e.g. file name) when it recognizes that
    author has not provided alternative content. (Level A)

    <jeanne> Repair Missing Alternatives: The user can specify whether
    or not the user agent should generate and render repair text (e.g.
    file name) when it recognizes that author has not provided
    alternative content. (Level A)

    gl: does this require alternative for text.
    ... with no clause, then everything needs an alternative

    <jeanne> repair content, repair text

    <jeanne> Content generated by the user agent to correct an error
    condition. "Repair text" refers to the text portion of repair
    content. Error conditions that may lead to the generation of repair
    content include: Erroneous or incomplete content (e.g., ill-formed
    markup, invalid markup, or missing alternative content that is
    required by format specification);

    <jeanne> Missing resources for handling or rendering content (e.g.,
    the user agent lacks a font family to display some characters, or
    the user agent does not implement a particular scripting language).

    <jeanne> UAAG 2.0 does not require user agents to include repair
    content in the document object. Repair content inserted in the
    document object should conform to the Web Content Accessibility
    Guidelines 1.0 [WCAG10]. For more information about repair
    techniques for Web content and software, refer to "Techniques for
    Authoring Tool Accessibility Guidelines 1.0" [ATAG10-TECHS].

    <jeanne> script

    kf: need to scope this to the technology specification. leave it in.
    ... there are only certain element that have alternative content
    (and something can be used to generate repair text)

    sh: what is difference between required and supported

    in HTML5 can have legend for figure, fall back text, and
    aria-described by, how does UA know what is missing.

    JS: that is covered by 1.1.x

    ja: what is use case?

    resolved: revisit repair text 1.2.1

    issue: revisit repair text 1.2.1 (minutes 9nov2010)

    <trackbot> Created ISSUE-77 - Revisit repair text 1.2.1 (minutes
    9nov2010) ; please complete additional details at
    [27]http://www.w3.org/WAI/UA/tracker/issues/77/edit .

      [27] http://www.w3.org/WAI/UA/tracker/issues/77/edit

1.2.2 Repair Empty Alternatives

    The user has the option of receiving generated repair text when the
    user agent recognizes that the author has provided empty alternative
    content. (Level AA)

    gl: change 'receiving generated repair..." to "can specify whether
    or not to receive..."

    <Greg> "The user can specify whether or not the user agent should
    generate and render repair text (e.g. file name) when it recognizes
    that author has provided empty alternative content. (Level AA)"

    js +1

    kp +1

    <kford> +1

    <Jan> The user can specify whether or not the user agent should
    generate and render repair text (e.g. file name) when it recognizes
    that the author has provided empty alternative content. (Level AA

    <Greg> +1

    <sharper> +1

    +1

    <Jan> +1

    <Kim> +1

1.31 Highlighted items: The user has the option to highlight the
following classes of information so that each is uniquely
distinguished. (Level A)

    <Kim> the user can specify that the following classes of information
    be highlighted so that each is uniquely distinguished

    +1

    kf +1

    <Jan> The user can specify that the following be highlighted so that
    each is uniquely distinguishable

    <Jan> The user can specify that the following be highlighted so that
    each is uniquely distinguished

    <Greg> +1

    +1

    <Kim> +1

    sh: what if we add another item - presence of alternative content

    that would be item (e)

    kf: seems to muddy the water.

    gl: not that much different.

    js: only the presence of alternative content, not the actual
    alternative content

    ja: add to doc and see if we get any comments.

    <Greg> If we go with that approach make it "elements with
    alternative content" "elements with recognized alternative content"

    kf: add to document.

    all agree.

    <Greg> I'm not entirely happy with having it in two places, but if
    you want to.

    jr: what is unique about enabled elements (1.3.1.c)
    ... it makes sense

1.3.2 Highlighting options: The highlighting options (with the same
configurable range as the operating environment's conventional
selection utilities) include at least (Level A):

    kp: the user can specify highlighting options...

    <Kim> The user can specify highlighting options (in the same
    configurable range as the operating environment's73 conventional
    selection utilities) that include at least (Level A):

    ja: perhaps add parenthetical as a (d) item

    sh: what about icons or earcons

    jr: include (in the same configurable range as the operating
    environment's73 conventional selection utilities) as a note before
    the list, but after the SC
    ... not sure about icons/earcons...the SC already says 'at least'
    which leaves door open for other highlighting

    kf: if 1.3.2 is how to comply with 1.3.1 then including an icon may
    be necessary.

    <jeanne> For those who want to check on the updates - here is the
    latest master document.
    [28]http://www.w3.org/WAI/UA/2010/ED-UAAG20-20101109/MasterUAAG20101
    109.html

      [28] 
http://www.w3.org/WAI/UA/2010/ED-UAAG20-20101109/MasterUAAG20101109.html

    gl: need to be careful about what we require. the list is a
    requirement...'at least' these listed items, could be more but...

    kp: put the parenthetical note after the list so it doesn't break up
    the reading.

    gl: perhaps create a different SC about how to highlight different
    types of information

    <Jan> The user can specify highlighting options that include at
    least (Level A)

    jr: input focus should be 'outline'
    ... 'c' should be outline (css selector)

    <Jan> (a) foreground colors, (b) background colors, and (c) outline

    <jeanne> outline (block or text with configurable color and width)

    gl: need to be technology neutral, no mention of CSS.

    say border with configurable color, thichness (not width), and style
    (dotted, dashed,etc.)

    ja: how is dotted vs dashed outline programmatically determinable?

    gl: list includes...foreground color, background color, outline
    (configurable color & thickness)

    <jeanne> (a) foreground colors,

    <jeanne> (b) background colors, and

    <jeanne> (c) border (configurable color, style, and thickness)

    gl: these are the minimum. in the implementation include annimation
    if user can turn it off, or an icon to follow content focus

    sh: when OS changes its cursor does the UA change also

    jr: would like to drop the (with the same configurable range as the
    operating environment's conventional selection utilities). seems
    like overkill

    js and kp disagree

    gl: there needs to be a meaningful selection of choices. tho, there
    are some OS that do not provide options

    kp: leave it out\

    js: leave it out

    gl: what about flash, they don't have the same configuration
    ability.
    ... are we talking about the user interface as well as content

    kp: how big a hole is this?

    all: leave out the clause.

    gl: put note in implementation to provide more than 2 options of
    highlighting options

1.4.1 (former 3.6.1) Configure Text: The user can globally set the
following characteristics of visually rendered text content, overriding
any specified by the author or user agent defaults (Level A):

    gl: 1.3.1 globally seem optional, but in 1.4.1 globally seems
    required

    kf: assume all user configurations are global, exceptions are called
    out

    gl: needs to be clear when taken out of context, could be all text
    in a given viewport

    kp: leave it the way it is.

    <jeanne> ACTION: JS to review document with Kim to insure that scope
    of Global vs. individual is correct for each SC. [recorded in
    [29]http://www.w3.org/2010/11/09-ua-minutes.html#action02]

    <trackbot> Created ACTION-464 - Review document with Kim to insure
    that scope of Global vs. individual is correct for each SC. [on
    Jeanne Spellman - due 2010-11-16].

    kf: listed 3 things to specify. are we missing anything?

    Resolution: the following are now completed--all of GL1.1, SC 1.2.1,
    all of GL 1.3, and SC 1.4.1

1.4.2 Preserve Distinctions: The user can preserve distinctions in the
size of rendered text when that text is rescaled (e.g. headers continue
to be larger than body text) within absolute limitations imposed by the
platform. (Level A)

    gl: "within absolute limitations imposed by the platform" is to
    cover text only browsers

    <jeanne> Meeting: UAWG Video Conference

    if too complex or should be assumed could move to implementing

    kf: would like to move platform statement to implementing document

    ja: +1

    gl: ok with moving it

    1.4.2 Preserve Distinctions: The user can preserve distinctions in
    the size of rendered text when that text is rescaled (e.g. headers
    continue to be larger than body text)

    <jeanne> Preserve Distinctions: The user can specify that
    distinctions in the size of rendered text be preserved when that
    text is rescaled (e.g. headers continue to be larger than body text)
    within absolute limitations imposed by the platform. (Level A)

    ja: use case of person with low vision to need base font large, but
    if distinction scale with the base text, then the heading become too
    large. uses a different mechanism to render distinctions

    <Kim> The user can specify whether or not distinctions in the size
    of rendered text be resized when that text is rescaled (e.g. headers
    continue to be larger than body text)

    <jeanne> 1.4.2 (former 3.6.2) Preserving Size Distinctions: The user
    can specify that distinctions in the size of rendered text be
    preserved when that text is rescaled (e.g. headers continue to be
    larger than body text) within absolute limitations imposed by the
    platform. (Level A)

    The user can specify whether or not distinctions in the size of
    rendered text are preserved when that text is rescaled (e.g. headers
    continue to be larger than body text)

    <jeanne> 1.4.2 (former 3.6.2) Preserving Size Distinctions: The user
    can specify whether or not distinctions in the size of rendered text
    are preserved when that text is rescaled (e.g. headers continue to
    be larger than body text). (Level A)

    <kford> rrs agent, make minutes

    Resolution: 1.4.2 is completed!!

1.5.1 Global Volume: The user can independently adjust the volume of
all audio tracks the user agent renders, relative to the global volume
level set through operating environment mechanisms. However, if audio
is muted at the global level the user agent should not override this
unless the behavior is optional, not enabled by default, and the user
is cautioned as to its implications....

    UNKNOWN_SPEAKER: (e.g. the alarm clock application on a mobile
    device has an option to play the alarm even if the system is muted,
    provided the check box is normally unchecked and is accompanied by
    text cautioning the user about this behavior. (Level A)

    ja: seems a bunch of this should be in implementing.

    js: this is an open action, is a combining of old 3.7.1 and .2

    <jeanne> However, if audio is

    <jeanne> <jeanne> muted as the global level the user agent should
    not override

    <jeanne> this unless the behavior is optional, not enabled by
    default, and the

    <jeanne> user is cautioned as to its implications. (e.g. the alarm
    clock

    <jeanne> application on a mobile device has an option to play the
    alarm even if

    <jeanne> the system is muted

    kp: do we have to say "user agent renders"

    jr: +1

    <Jan> However, user agent should only override a global mute when
    the user has explitly requested this and has been cautioned about
    the implications.

    <Kim> The user can independently adjust the volume of all audio
    tracks relative to the global volume level set through operating
    environment mechanisms. However, if audio is muted at the global
    level the user agent should not override this unless the behavior is
    optional, not enabled by default, and the user is cautioned as to
    its implications. (e.g. the alarm clock application on a mobile
    device...

    <Kim> ...has an option to play the alarm even if the system is
    muted.)

    <Jan> However, the user agent may only override a global mute when
    on explicit user requested has the user has been cautioned about the
    implication.

    <Jan> However, the user agent may only override a global mute on
    explicit user request and the user has been cautioned about the
    implication.

    The user can independently adjust the volume of all audio tracks
    relative to the global volume level set through operating
    environment mechanisms. However, the user agent may only override a
    global mute on explicit user request and the user has been cautioned
    about the implication.

    <sharper> +1

    +1

    <Jan> However, the user agent may only override a global mute on
    explicit user request and if the user has been cautioned about the
    implication.

    <Kim> +1

    <kford> +1

    The user can independently adjust the volume of all audio tracks
    relative to the global volume level set through operating
    environment mechanisms. However, the user agent may only override a
    global mute on explicit user request and if the user has been
    cautioned about the implication.

    Resolution: GL 1.5 is completed!!

    <jeanne>
    [30]http://www.w3.org/WAI/UA/2010/ED-UAAG20-20101109/MasterUAAG20101
    109.html

      [30] 
http://www.w3.org/WAI/UA/2010/ED-UAAG20-20101109/MasterUAAG20101109.html

1.6.1 Speech Rate and Volume: The user can set in synthesized speech,
overriding any values specified by the author (Level A):

    for synthesized speech The user can set, overriding any values
    specified by the author

    jr: applicability notes, yes the author can override author
    settings.
    ... a section at the start of the document, (WCAG conditions of
    conformance), things that apply to all guidelines.

    kp: 'the user can set
    ... implies overriding

    kf: why is this here, for talking browsers?
    ... author does not set this, how can a user override it

    jr: for speech this is like changing text scale

    the user can set the following for synthesized speech

    resolution: 1.6.1, 1.6.2, 1.6.3 are completed!!!

1.6.4 The following speech features are provided (Level AA): (a)
user-defined extensions to the synthesized speech dictionary, (b)
"spell-out", where text is spelled one character at a time, or
according to language-dependent pronunciation rules, (c) at least two
ways of speaking numerals: one where numerals are spoken as individual
digits and punctuation (e.g. "one two zero three...

    UNKNOWN_SPEAKER: point five" for 1203.5 or "one comma two zero three
    point five" for 1,203.5), and and one where full number are spoken
    (e.g. "one thousand, two hundred and three point five"). (d) at
    least two ways of speaking punctuation: one where punctuation is
    spoken literally, and one where punctuation is rendered as natural
    pauses.

    jr: questions the usecase, implementation of these

    kp: why 2 ways of reading numbers
    ... user should specify the way it can read numbers.

    kf: assume talking browser...

    kp: oh, thinking speech out vs speech in

    *** 10 min break ***

1.6.4

    <jeanne> 1.6.4 (former 3.8.4) Speech Features: The following text to
    speech features are provided: (Level AA)

    <jeanne> 1.6.4 (former 3.8.4) Text to Speech Features: The following
    features are provided: (Level AA)

    <jeanne> 1.6.4 (former 3.8.4) Synthesized Speech Features: For
    synthesized speech, the following features are provided: (Level AA)

    editors note about treatment of currency

    <kford> ACTION: kford to ensure implementing doc addresses currency
    for 1.6.4. [recorded in
    [31]http://www.w3.org/2010/11/09-ua-minutes.html#action03]

    <trackbot> Sorry, couldn't find user - kford

    ja: is number speaking hard coded in the synthesizer.

    <jeanne> +1

    Resolution: 1.6.4 is complete, all of GL 1.6 is completed!!

1.7.1 Author Style Sheets: If the author has supplied one or more style
sheets, the user has the following options (Level A):

    if one or more author style sheets are supplied....

    <jeanne> ACTION: JS to review document with Kim to adjust all verb
    tenses to present tense. [recorded in
    [32]http://www.w3.org/2010/11/09-ua-minutes.html#action04]

    <trackbot> Created ACTION-465 - Review document with Kim to adjust
    all verb tenses to present tense. [on Jeanne Spellman - due
    2010-11-16].

    1.7.1 if one or more author style sheets are supplied the user has
    the following options:

    kf +1

    ja +1

    <Greg> Should "select a style sheet" be "select a style sheet to be
    applied"?

    select and apply a style sheet

    start at 11 eastern

    gl: can the user apply more that one style sheet simultaneously

    kp: for accessibility may want more than one.

    <Greg> Consider saying something like "if..." the user has the
    option to select none, one or more style sheets to be applied", e.g.
    one user style sheet that makes all text large, another that
    highlights the active element, etc.

    kf: most people don't know that style sheets exist

    kp: select and apply 1 or more style sheets

    <jeanne> (a) select and apply one or more style sheets, or

    kf: should be in best practices or implementation document

    +1

    <Greg> I think we want to move to the future where people can create
    and distribute special-purpose user style sheets, and they can be
    used together.

    kp: like defined vs supplied

    <jeanne> +1

    1.7.1 if one or more author style sheets are defined the user has
    the following options:

    a. select and apply one or more style sheets

    b. turn off style sheets

    <mhakkinen> viewport or output medium?

    gl: wants user to be able to use print style sheet on the screen

    kf: current browsers allow user to select from all available.

    <Greg> I think the wording does not require the user agent to allow
    the user to select a style sheet for a different output medium (e.g.
    using a print style sheet on the screen); it could just let the user
    select from style sheets for the current medium. Is that
    intentional?

    [33]http://www.jimthatcher.com/

      [33] http://www.jimthatcher.com/

    <Greg> A solution might be "a) select and apply one from all
    available style sheets". Not great but close.

    <mhakkinen> suggestion: select and apply one or more available
    styles available for the current viewport.

    <Greg> Another example is where today you sometimes can't take
    advantage of a simplified presentation on the screen, only in print.

    use case: cognitive issues. want to print the page with out the
    print style sheet. if print style sheet is used the paper copy looks
    different from the screen copy and I am confused

    <Greg> Another wording option would be "a) select and apply one or
    more available style sheets, regardless of target medium"

    <Greg> Style sheets for another medium might be better as lower
    priority.

    FF shows style sheets in form <link rel...> but does not show
    @import style sheets to the user

    1.7.1 if one or more author style sheets are defined the user has
    the following options: a. select and apply one or more style sheets
    b. turn off style sheets

    <Greg> Should be "b) turn off author style sheets"

    +1

    <Kim> +1

    1.7.1 if one or more author style sheets are defined the user has
    the following options: a. select and apply one or more style sheets
    b) turn off author style sheets

    <Greg> I don't like but can live with the (a).

    <jeanne> a) select and apply one or more available style sheets,
    regardless of target medium"

    <jeanne> User Style Sheets: If one or more user style sheets are
    defined, the user has the following options: (Level A)

    <jeanne> (a) select a style sheet, or

    <jeanne> (b) turn off user style sheets.

    <Greg> Except aren't we making the same as 1.7.1, "select and apply
    on user style sheet"?

    <jeanne> select and apply one or more style sheets, or

    resolution: 1.7.1 and 1.7.2 are completed!!!

    <jeanne> 1.7.1 (former 3.9.1) Author Style Sheets: If one or more
    author style sheets are defined, the user has the following options:
    (Level A)

    <jeanne> (a) select and apply one or more author style sheets, or

    <jeanne> (b) turn off author style sheets.

    <jeanne> 1.7.2 (former 3.9.2) User Style Sheets: If one or more user
    style sheets are defined, the user has the following options: (Level
    A)

    <mhakkinen> Finland signing off... see you tomorrow.

    <jeanne> (a) select and apply one or more user style sheets, or

    <jeanne> (b) turn off user style sheets.

1.8.1 Highlight Viewport: The viewport with the input focus (including
nested viewports and their containers) is highlighted, and the user is
able to customize attributes of the highlighted mechanism, including,
but not limited to, shape, size, stroke width, color, and blink rate
(if any). (Level A)

    kf: if the SC are individually testable, why do we have 'and' in
    them. that is 2 items to test

    gl: earlier suggested combining where possible. but easier to test
    if no 'and'
    ... then SC have to cross reference each other which makes reading
    difficult to parse.

    <jeanne> 1.8.1 needs attention

    resolution: 1.8.1 needs attention - needs rewording

    <jeanne> issue: 1.8.1 needs attention - confusing and meaning is
    unclear.

    <trackbot> Created ISSUE-78 - 1.8.1 needs attention - confusing and
    meaning is unclear. ; please complete additional details at
    [34]http://www.w3.org/WAI/UA/tracker/issues/78/edit .

      [34] http://www.w3.org/WAI/UA/tracker/issues/78/edit

1.8.2 Move Viewport to Selection and Focus: When a viewport's selection
or input focus changes, the viewport moves as necessary to ensure that
the new selection or input focus location is at least partially in the
viewport. (Level A)

    <Greg> Technically "in the viewport" should be "in the visible
    portion of the viewport"

    <Greg> I wish there was a concise term for "the visible portion of
    the viewport".

    <kford> Issue: Need a consise term forvisible portion of viewport.

    <trackbot> Created ISSUE-79 - Need a consise term forvisible portion
    of viewport. ; please complete additional details at
    [35]http://www.w3.org/WAI/UA/tracker/issues/79/edit .

      [35] http://www.w3.org/WAI/UA/tracker/issues/79/edit

    Move Viewport to Selection and Focus: When a viewport's selection or
    input focus changes, the viewport moves as necessary to ensure that
    the new selection or input focus location is at least partially in
    the visible portion of the viewport.

    <Greg> Similarly, there's the question of whether "the viewport
    moves" means "the viewport pans or scrolls" or "the visible portion
    of the viewport is moved".

    Resolution: 1.8.2 is completed!!

1.8.3 Resizable: The user has the option to make graphical viewports
resizable, within the limits of the display, overriding any values
specified by the author.

    <Greg> Should "within the limits of the display" be "up to the size
    of the display"?

    kf: graphical viewport seems odd, do we use it anywhere else?
    ... 1.8.4 ... lots of places

    kp: needs to be here

    <Greg> If we took that phrase out "within the limits of the
    display/up to the size of the display" woud it really change
    anything?

    <Greg> Would user agents ever let you resize a window or viewport
    smaller but not larger?

    resolution: 1.8.3 is completed!!

1.8.4 Scrollbars: Graphical viewports include scrollbars if the
rendered content (including after user preferences have been applied)
extends beyond the viewport dimensions, overriding any values specified
by the author.

    gl: would like to postpone discussion of 1.8.4 till later

    issue: talk about 1.8.4 later, greg to create clarification

    <trackbot> Created ISSUE-80 - Talk about 1.8.4 later, greg to create
    clarification ; please complete additional details at
    [36]http://www.w3.org/WAI/UA/tracker/issues/80/edit .

      [36] http://www.w3.org/WAI/UA/tracker/issues/80/edit

1.8.5 Viewport History: If the user agent maintains a viewport history
mechanism (e.g., via the "back button") that stores previous "viable"
states (i.e., that have not been negated by the content, user agent
settings or user agent extensions). It maintains information about the
page and embedded controls, including viewport scrolling, selection and
keyboard focus. It restores the...

    UNKNOWN_SPEAKER: saved values when the user returns to a state in
    the history.

Summary of Action Items

    [NEW] ACTION: Greg figure out and or create SC for content reflow.
    [recorded in
    [37]http://www.w3.org/2010/11/09-ua-minutes.html#action01]
    [NEW] ACTION: JS to review document with Kim to adjust all verb
    tenses to present tense. [recorded in
    [38]http://www.w3.org/2010/11/09-ua-minutes.html#action04]
    [NEW] ACTION: JS to review document with Kim to insure that scope of
    Global vs. individual is correct for each SC. [recorded in
    [39]http://www.w3.org/2010/11/09-ua-minutes.html#action02]
    [NEW] ACTION: kford to ensure implementing doc addresses currency
    for 1.6.4. [recorded in
    [40]http://www.w3.org/2010/11/09-ua-minutes.html#action03]

    [End of minutes]
Received on Tuesday, 9 November 2010 21:55:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:39 UTC