Minutes of UAWG teleconference of 31 July 2014

HTML Minutes:
http://www.w3.org/2014/07/31-ua-minutes.html

Summary of Action Items:

    [NEW] ACTION: Greg to adjust Examples associated with changes
    to SC from SB04 and SB05
    [NEW] ACTION: Jan to draft a new proposal for action-1006 CA05
    [NEW] ACTION: Kim to rewrite 1.8.2 Example 2 from EO21


Text of Minutes:
    [1]W3C

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

                                - DRAFT -

     User Agent Accessibility Guidelines Working Group Teleconference

31 Jul 2014

    See also: [2]IRC log

       [2] http://www.w3.org/2014/07/31-ua-irc

Attendees

    Present
           Greg_Lowney, Jan, Jeanne, Kim_Patch, kelly

    Regrets
           Jim, Eric

    Chair
           kelly

    Scribe
           jeanne

Contents

      * [3]Topics
          1. [4]CA06
          2. [5]Kim's proposal for action-1006
      * [6]Summary of Action Items
      __________________________________________________________

    <trackbot> Date: 31 July 2014

    <kford>
    [7]http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JulSep/00
    30.html

       [7] 
http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JulSep/0030.html

    <kford> MS07 - more relevance for non-desktop users - waiting
    on action-983 to get language from IndieUI about alternative
    language for keyboard interface

    <kford> MS04 - Delineate between content and browser - Waiting
    on action 976 to review definition of rendered content. Check
    3.2.2 and 3.2.3 for relevance to this comment

    <kford> MS05 [Implementing] - Done in UAAG, but there are some
    followup in Implementing on other success criteria examples to
    review for consistency.

    <kford> EO13 - change title of Implementing UAAG to
    Understanding UAAG EO15, EO16, EO20 - add a link to the EO
    intro page to the Abstract and rewrite the Abstract

    <kford> EO21 - [Implementing] rewrite 1.8.2 Example 2 SB04,
    SB05 [Implementing] Done in UAAG, but Implementing still needs
    an example update

    <kford> LG02 - [Implementing] prevent minify CSS waiting on
    action-987 for 1.7.4

    <kford> Group talking about what they can ask for and not. JS
    and GL saying not possible to ask for more than the
    accessibility API gives.

CA06

    Proposed response : UAWG agrees on this very important
    principle and have worked this into all appropriate parts of
    UAAG. However, the user agent can only ask for name, role,
    state, value, selection, and focus from the Accessibility API.
    "Meaning" can be inferred from the name, but there is no
    accessibility API attribute for "meaning". Otherwise, this is
    exactly what is intended with 4.1.2

    UAWG agrees on this very important principle and has worked
    this into all appropriate parts of UAAG. However, the user
    agent can only ask for existing attributes such as name, role,
    state, value, selection, and focus from the Accessibility API.
    "Meaning" can be inferred from the name, but there is no
    accessibility API attribute for "meaning". Otherwise, this is
    exactly what is intended with 4.1.2

    <Jan> JR: +1

    <Greg> +1

    RESOLUTION: Accept the response for CA06: UAWG agrees on this
    very important principle and has worked this into all
    appropriate parts of UAAG. However, the user agent can only ask
    for existing attributes such as name, role, state, value,
    selection, and focus from the Accessibility API. "Meaning" can
    be inferred from the name, but there is no accessibility API
    attribute for "meaning". Otherwise,

    this is exactly what is intended with 4.1.2

Kim's proposal for action-1006

    <kford> JR and GL talking about proposal.

    <kford> JR: Has started toahve too many extra requirements.

    <Jan> [8]https://support.google.com/chrome/answer/142893?hl=en

       [8] https://support.google.com/chrome/answer/142893?hl=en

    <Greg> Here's the page on Firefox's auto-fill feature: Control
    whether Firefox automatically fills in forms with your
    information | Firefox Help

    <Greg>
    [9]https://support.mozilla.org/en-US/kb/control-firefox-automat
    ically-fills-in-forms

       [9] 
https://support.mozilla.org/en-US/kb/control-firefox-automatically-fills-in-forms

    <kford> Group talking about what gets saved on a form.

    <Greg> It seems as if Firefox is only auto-filling in fields
    when you return to the same form, but that Chrome may be being
    more aggressive and auto-filling fields in new forms the first
    time you view them (and thus gives a warning about only using
    it on forms you trust, for fear of hidden fields being used to
    capture your information).

    <Greg> Firefox has some of the sub-requirements that Kim
    suggested: you can delete entries, reset the history, and
    prevent caching. You cannot cause it to automatically clear
    entries after a period of time, for example.

    <Jan> [10]http://webaim.org/techniques/forms/controls

      [10] http://webaim.org/techniques/forms/controls

    <Greg> It appears that Firefox caches text I've entered into an
    input control only when I've submitted the form. Also note that
    it never auto-fills, but rather gives me the option on a
    per-control basis: click on it to get a list of previous
    values.

    <Greg> Jeanne is correct that Firefox does not cache TEXTAREA
    contents, only INPUT text fields.

    Greg: I think we need to separate out the saving of the form
    from the caching of the form

    Jan: I think we should have a low bar and not include recovery
    from a browser crash

    kelly: I think this should be AAA, especially when considering
    the mobile space. Mobile is a more transitory because it is
    hard to complete forms on mobile.

    Jan: In my Android Chrome, if I fill in a form and come back to
    the page, my data is still there.

    Greg and Kelly: navigate away and close it, and then see if the
    data is still there.

    Kelly: If a browser crashes, the likelihood of data being saved
    is low.

    <Jan>
    [11]http://androidwidgetcenter.com/android-tips/how-to-enable-a
    utofill-in-android-browser/

      [11] 
http://androidwidgetcenter.com/android-tips/how-to-enable-autofill-in-android-browser/

    <Jan> So this implements simpler autofill req
    [12]http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JulSep/0
    024.html

      [12] 
http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JulSep/0024.html

    <scribe> ACTION: Jan to draft a new proposal for action-1006
    CA05 [recorded in
    [13]http://www.w3.org/2014/07/31-ua-minutes.html#action01]

    <trackbot> Created ACTION-1009 - Draft a new proposal for
    action-1006 ca05 [on Jan Richards - due 2014-08-07].

    3) Finishing up open items:

    MS07 - more relevance for non-desktop users - waiting on
    action-983 to get language from IndieUI about alternative
    language for keyboard interface

    MS04 - Delineate between content and browser - Waiting on
    action 976 to review definition of rendered content. Check
    3.2.2 and 3.2.3 for relevance to this comment

    MS05 [Implementing] - Done in UAAG, but there are some followup
    in Implementing on other success criteria examples to review
    for consistency.

    EO13 - change title of Implementing UAAG to Understanding UAAG

    EO15, EO16, EO20 - add a link to the EO intro page to the
    Abstract and rewrite the Abstract

    EO21 - [Implementing] rewrite 1.8.2 Example 2

    SB04, SB05 [Implementing] Done in UAAG, but Implementing still
    needs an example update

    LG02 - [Implementing] prevent minify CSS waiting on action-987
    for 1.7.4

    <scribe> ACTION: Kim to rewrite 1.8.2 Example 2 from EO21
    [recorded in
    [14]http://www.w3.org/2014/07/31-ua-minutes.html#action02]

    <trackbot> Created ACTION-1010 - Rewrite 1.8.2 example 2 from
    eo21 [on Kimberly Patch - due 2014-08-07].

    <scribe> ACTION: Greg to adjust Examples associated with
    changes to SC from SB04 and SB05 [recorded in
    [15]http://www.w3.org/2014/07/31-ua-minutes.html#action03]

    <trackbot> Created ACTION-1011 - Adjust examples associated
    with changes to sc from sb04 and sb05 [on Greg Lowney - due
    2014-08-07].

Summary of Action Items

    [NEW] ACTION: Greg to adjust Examples associated with changes
    to SC from SB04 and SB05 [recorded in
    [16]http://www.w3.org/2014/07/31-ua-minutes.html#action03]
    [NEW] ACTION: Jan to draft a new proposal for action-1006 CA05
    [recorded in
    [17]http://www.w3.org/2014/07/31-ua-minutes.html#action01]
    [NEW] ACTION: Kim to rewrite 1.8.2 Example 2 from EO21
    [recorded in
    [18]http://www.w3.org/2014/07/31-ua-minutes.html#action02]

    [End of minutes]
      __________________________________________________________

-- 
_______________________________
Jeanne Spellman
W3C Web Accessibility Initiative
jeanne@w3.org

Received on Thursday, 31 July 2014 18:28:19 UTC