[BUGS] Minutes Bug Triage sub-team 31 August 2010

Minutes of the Bug Triage sub-team for 31 August 2010 are posted to
http://www.w3.org/2010/08/31-a11y-bugs-minutes.html and copied below.


  Bug Triage sub-team - HTML A11Y TF


    31 Aug 2010

See also: IRC log <http://www.w3.org/2010/08/31-a11y-bugs-irc>


    Attendees

Present
    Michael_Cooper, Martin_Kliehm, Joshue_O'Connor, Marco_Ranon
Regrets
    Laura_Carlson, Sally_Cain
Chair
    Michael_Cooper
Scribe
    MichaelC


    Contents

    * Topics <http://www.w3.org/2010/08/31-a11y-bugs-minutes.html#agenda>
         1. Homework
            <http://www.w3.org/2010/08/31-a11y-bugs-minutes.html#item01>
         2. Next meeting: Tuesday 7 September 2010 at 15:00 UTC
            <http://www.w3.org/2010/08/31-a11y-bugs-minutes.html#item02>
    * Summary of Action Items
      <http://www.w3.org/2010/08/31-a11y-bugs-minutes.html#ActionSummary>

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

9326: might be a duplicate of 10066

pinging Cynthia to verify, added note to bug

(that is, 10066 has taken over the role of ARIA mapping omnibus bug, so
9326 not needed)

8673: assigned to cynthia, need info from the mapping sub-team

no action from us at this time

8000: Assigning to Cynthia to address in ARIA mapping sub-team

<Joshue> Just for the record, list of bugs we are working on as of Aug 1
2010
http://www.w3.org/Bugs/Public/buglist.cgi?keywords=a11ytf&bug_status=RESOLVED&resolution=NEEDSINFO&resolution=INVALID&resolution=WONTFIX
<http://www.w3.org/Bugs/Public/buglist.cgi?keywords=a11ytf&bug_status=RESOLVED&resolution=NEEDSINFO&resolution=INVALID&resolution=WONTFIX>

8644: this is an omnibus @alt bug on several elements

seems primarily related to <embed>

(fall back for the other elements being addressed separately)

10077 separately requests @alt for <embed>

<object> has a fallback model via being "transparent", but <embed> lacks
this

there's confusion about when to use <embed> and when to use <object>

and whether fallback content as supported by <object> is browser support
fallback or accessibility alternative fallback

these are two separate use cases, even though sometimes they get
confused / blended

as defined in
http://dev.w3.org/html5/spec/content-models.html#fallback-content, the
fallback for object is for browser support and does not address
accessibility

so this leads us to conclude that both <embed> and <object> do not have
accessibility fallback mechanisms at the moment

this issue turns out to be represented by 8885

<Joshue> 8885 http://www.w3.org/Bugs/Public/show_bug.cgi?id=8885


      Homework

Review the wontfix bugs so we can be more efficient in next triage meeting

http://www.w3.org/Bugs/Public/buglist.cgi?keywords=a11ytf&bug_status=RESOLVED&resolution=WONTFIX
<http://www.w3.org/Bugs/Public/buglist.cgi?keywords=a11ytf&bug_status=RESOLVED&resolution=WONTFIX>

Josh to make proposals on 9216, 9437, 9871, 9872

Michael to make proposals on 9061, 9098, 9212, 9215

Martin to look at 8674, 8681, 8754

Marco to look at 8827, 8872


      Next meeting: Tuesday 7 September 2010 at 15:00 UTC

<scribe> scribe: MichaelC


    Summary of Action Items

[End of minutes]
------------------------------------------------------------------------
Minutes formatted by David Booth's scribe.perl
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm>
version 1.135 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2010/08/31 17:16:28 $


-- 

Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org <mailto:cooper@w3.org>
Information Page <http://www.w3.org/People/cooper/>