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

Minutes: [html-techs-tf] Agenda 4th of March 2013

From: James Nurthen <james.nurthen@oracle.com>
Date: Mon, 04 Mar 2013 10:02:55 -0800
Message-ID: <5134E1CF.8020500@oracle.com>
To: w3c-wai-gl@w3.org, Protocols and Formats Working Group WG <w3c-wai-pf@w3.org>
Minutes from the call can be found at 
http://www.w3.org/2013/03/04-html-techs-tf-minutes.html and in text below.
Thanks to Detlev for scribing

regards,
James

    [1]W3C

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

                                - DRAFT -

                     HTML5 + ARIA Techniques for WCAG

04 Mar 2013

    See also: [2]IRC log

       [2] http://www.w3.org/2013/03/04-html-techs-tf-irc

Attendees

    Present
           James_Nurthen, Jon_Gunderson, +49.404.318.aaaa, Detlev,
           Loretta, Marc_Johlic, [IPcaller]

    Regrets
    Chair
           JamesNurthen

    Scribe
           Detlev

Contents

      * [3]Topics
      * [4]Summary of Action Items
      __________________________________________________________

    <jamesn> [5]https://www.w3.org/2002/09/wbs/35422/18_2_2013/

       [5] https://www.w3.org/2002/09/wbs/35422/18_2_2013/

    <scribe> scribe: Detlev

    Looking at survey - few answers - apologies

    This is rthwe link to the survey:
    [6]https://www.w3.org/2002/09/wbs/35422/18_2_2013/

       [6] https://www.w3.org/2002/09/wbs/35422/18_2_2013/

    Walking through Loretta's comment

    Loretta: not sure why they were related to SC 1.3.1
    ... should be applicable to SC 2.4.4
    ... Question what will show up in things like SR link lists

    James: aria-describedby doesn't usually show up in link lists
    ... Why necessary to be in 2.4.4 rather than 2.4.9?
    ... Fear is that this technique will be seen as necessary for
    meeting 2.4.4

    Loretta: unsure what the issue is

    James: suggests to use an example where 2.4.4 would not be met
    without it

    Loreatta: Every 2.4.9 technique is also a 2.4.4 technique

    James: Proposes one example where 2.4.4 wouldn't be met without
    aria-describedby

    Marc: possibly looking at failures (F63) adapting for
    aria-described by

    [7]http://www.w3.org/TR/WCAG20-TECHS/F63.html

       [7] http://www.w3.org/TR/WCAG20-TECHS/F63.html

    James: suggestion was to amending one of the examples in F63 to
    add to this technique so it would help meeting 2.4.4

    Loretta: willing to make edits but questions remain

    Group making on-the-fly edits to technique
    [8]http://www.w3.org/WAI/GL/wiki/Using_aria-describedby_for_lin
    k_purpose

       [8] http://www.w3.org/WAI/GL/wiki/Using_aria-describedby_for_link_purpose

    James: aria spec does not prescribe behaviour how AT would
    handle info in aria-describedby

    Loretta: Will give some indication that both the link text and
    description text will usually both be made available
    ... either available at the vey end of accessible name , states
    etc, or offered as option to explore
    ... Possibility to remove headings to meet 2.4.4 from
    sufficient to advisory

    James: but this may not happen

    Loretta: shall we drop example 7, and what do you think of ex.
    3?

    James: Example 3 not ideal, may be covered by other examples

    Lortetta: suggest dropping Ex. 3 and 7

    James: seconds that
    ... Example 7 may not actually work anyway

    Same applies to example 6 - needs testing

    Detlev: Proposes testing example 6 in that technique
    ... suggests links to AT support database once it's there

    Loretta: Detailed level of support info not usually part of
    WCAG techniques - changes too quickly

    Moving to Technique "Using aria-label for link purpose"
    [9]http://www.w3.org/WAI/GL/wiki/Using_aria-label_for_link_purp
    ose

       [9] http://www.w3.org/WAI/GL/wiki/Using_aria-label_for_link_purpose

    James: If someone's using the A11y API to compute the list of
    links they would get the aria-label info, if they use the DOM,
    they wouldn't
    ... Could be 2.4.9 Candidate
    ... Accordign to aria spec aria-label should override / replace
    the link text
    ... Good practice to start aria-label text with the same text
    as the link text - "Read more.." replaced by "Read more about
    Seminole tax hike"

    (On-the -fly changes to technique being made by James)

    (...explaining/reinforcing the replacement rule according to
    the spec's acessible name computation)

    Marc: should we include the link?

    <jamesn>
    [10]http://www.w3.org/TR/wai-aria/roles#textalternativecomputat
    ion

      [10] http://www.w3.org/TR/wai-aria/roles#textalternativecomputation

    James: its called text alternative comutation

    sorry, text alternative computation

    <jongund> I have to go

    James: adding reference to SC 2.4.9

    Support notes need to be updated

Summary of Action Items

    [End of minutes]
      __________________________________________________________


     Minutes formatted by David Booth's [11]scribe.perl version
     1.137 ([12]CVS log)
     $Date: 2013-03-04 18:01:43 $
      __________________________________________________________

      [11] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
      [12] http://dev.w3.org/cvsweb/2002/scribe/




On 2/28/2013 12:18 AM, Joshue O Connor wrote:
> Agenda:
> Survey HTML Techniques Task Force for March 4th 2013
> https://www.w3.org/2002/09/wbs/35422/18_2_2013/ 
Received on Monday, 4 March 2013 18:03:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 March 2013 18:03:29 GMT