W3C home > Mailing lists > Public > public-html-a11y@w3.org > February 2014

Minutes: HTML A11Y TF Teleconference, 13 February 2014

From: Mark Sadecki <mark@w3.org>
Date: Thu, 13 Feb 2014 12:27:46 -0500
Message-ID: <52FD0092.2020200@w3.org>
To: HTML A11Y TF Public <public-html-a11y@w3.org>
Hello,

The minutes for the HTML Accessibility Task Force Teleconference 13 February 2014 are available in HTML and plain text below:

HTML:
http://www.w3.org/2014/02/13-html-a11y-minutes.html

TEXT:
   [1]W3C

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

              HTML Accessibility Task Force Teleconference

13 Feb 2014

   See also: [2]IRC log

      [2] http://www.w3.org/2014/02/13-html-a11y-irc

Attendees

   Present
          janina, Mark_Sadecki, Cynthia_Shelly, Plh, chaals, Judy,
          David_MacDonald, BillyG, Adrian_Roselli

   Regrets
          John Foliot, Leonie Watson, Rich Schwerdtfeger

   Chair
          Janina_Sajka

   Scribe
          MarkS

Contents

     * [3]Topics
         1. [4]Identify Scribe
            http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scr
            ibe_List
         2. [5]Longdesc Update
         3. [6]Canvas 2D Status & Next Steps
         4. [7]Alt Guidance & Next Steps
         5. [8]Bug Triage: Review of Resolved Bugs tracked by TF
         6. [9]13273
         7. [10]13437
         8. [11]13275
         9. [12]13461
        10. [13]13651
     * [14]Summary of Action Items
     __________________________________________________________

   <trackbot> Date: 13 February 2014

   <janina> Meeting: HTML-A11Y Task Force Teleconference

Identify Scribe
[15]http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List

     [15] http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List

   <scribe> scribe: MarkS

Longdesc Update

   <chaals> MS: Chaals is slacking…

   <chaals> … but we're getting on with it and will continue to
   update people.

   MS: Chaals and I continue to work on items

Canvas 2D Status & Next Steps

   <chaals> MS: We were waiting to hear back from Mozilla about
   trying out hit regions...

   <chaals> … yesterday they said that they think this approach is
   actually looking good.

   <chaals> … they have a prototype and expect to show that next
   week. They do not intend to drop drawFocusIfNeeded. That is
   good news all around...

   <chaals> … Unsure about status of Chrome.

   <chaals> JB: Good to hear. Understand that hit test depends on
   several things, including perhaps path which is not going to
   get into the current spec. Would implementation get this into
   level 1?

   <chaals> MS: Think the spec will require work on hit regions
   and path, but don't think this is *months*.

   <chaals> … sowe would have to go through some administrative
   hoops to get this into L1

   <chaals> JB: With implementations, this is a pretty good reason
   to put it back in…

   <chaals> MS: Asked them to summarise their position in public,
   haven't seen that yet.

Alt Guidance & Next Steps

   JS: interested in finding out what the timeframe will be for
   Hit Regions

   <janina>
   [16]http://lists.w3.org/Archives/Public/public-html-a11y/2014Fe
   b/0026.html

     [16] http://lists.w3.org/Archives/Public/public-html-a11y/2014Feb/0026.html

   JS: SteveF has shared the list of bugs that HTML WG had
   requested regarding ALT work/changes
   ... we have been talking about syncing 5.1 and 5.0 specs
   ... Paul had some ideas on how to move forward process wise,
   but he is not here.

Bug Triage: Review of Resolved Bugs tracked by TF

   -> [17]http://www.w3.org/2014/02/12-a11y-bugs-minutes.html
   Minutes from Bug Triage

     [17] http://www.w3.org/2014/02/12-a11y-bugs-minutes.html

   MS: Bringing one bug to the canvas sub team
   ... Bringing one bug to the canvas sub team
   ... Reopened a bug against 5.1

   <scribe> ...Closed two

   -> [18]https://www.w3.org/Bugs/Public/show_bug.cgi?id=13549
   13549 4.10.18 associating form elements with forms that do not
   contain them can cause navigation problems for AT and keyboard
   users

     [18] https://www.w3.org/Bugs/Public/show_bug.cgi?id=13549

   CS: This could be addressed with a WCAG failure. but should
   also bring it against 5.1

   JS: Feel like this should cause a validation failure
   ... should be a 5.1 issue

   CS: If there isn't a WCAG failure, there should be

   DM: Please send a note to WCAG

   -> [19]https://www.w3.org/Bugs/Public/show_bug.cgi?id=12964
   12964 <video>: Declarative linking of full-text transcripts to
   video and audio elements

     [19] https://www.w3.org/Bugs/Public/show_bug.cgi?id=12964

   JS: talked about this in Media sub team. syncing functionality
   could be added if programatically linked
   ... there is mainstream interest in this
   ... more than just a longdesc for video
   ... think we should defer this to 5.1
   ... cognitive accessibility could be improved with this feature

   AR: wondering how this is different than closed captioning.
   ... don't want to see a situation where we duplicate a feature
   that already exists.

   JS: another use case is for people who want to read through the
   transcript.

   DM: WCAG recommends authors put text transcripts on the page of
   the video.

   -> [20]http://tinyurl.com/p5qkc2z LC1 HTML spec Resolved
   NEEDSINFO, INVALID, WONTFIX

     [20] http://tinyurl.com/p5qkc2z

13273

   [21]https://www.w3.org/Bugs/Public/show_bug.cgi?id=13273

     [21] https://www.w3.org/Bugs/Public/show_bug.cgi?id=13273

   Clarify text in media element user interface section

   Agreement that this would be better as a MUST requirement.

   OK with moving it to 5.1

   We should test current support

   DM: comes back to that old conversation about disabling
   javascript.

   JS: potential for use case for disabling js in order to get
   around inaccessible custom controls.
   ... anyone interested in keeping this in 5.0?

   CMN: I am in favor of that, but think we would have a hard time
   getting it into 5.0

   DM: it is a failure in WCAG

   CS: is there a failure technique for this?

   DM: yes, if you can't reach everything with the keyboard

   CMN: I think we should clarify that we are not moving this to
   5.1 just because we couldn't get it into the 5.0 timeline. It's
   something we should have done in 5.0

13437

   [22]https://www.w3.org/Bugs/Public/show_bug.cgi?id=13437

     [22] https://www.w3.org/Bugs/Public/show_bug.cgi?id=13437

   Editorial changes to The Video element (5 of 5)

   CMN: the argument they use to reject this bug seems like
   nonsense to me.

   CS: Seems like a non-issue to me

   agreement from the group

   CMN: If we want to keep this requirement, then its not that
   difficult to explain how it could be done. We would reopen this
   in 5.0.
   ... we would like to see implementers pick up the a11y features
   and get it right. They could be put at risk if they don't
   ... I think we want this always available (not necessarily
   visible)
   ... I suggest we open this and get it right. We want to make
   sure the control is available, but not necessarily visible.
   Right now its not clear that the UA is required to make it
   available.
   ... reopen and discuss it quickly.

   PLH: If you do that you should add more info.

   CMN: reopen it, assign it to me and put in some clarifying
   info.

13275

   [23]https://www.w3.org/Bugs/Public/show_bug.cgi?id=13275

     [23] https://www.w3.org/Bugs/Public/show_bug.cgi?id=13275

   Display of media control UI when scripting is disabled

   CMN: This looks the same as the previous bug. Mark it as a
   duplicate and state the intention is the same. would like to
   fix it in 5.1

13461

   [24]https://www.w3.org/Bugs/Public/show_bug.cgi?id=13461

     [24] https://www.w3.org/Bugs/Public/show_bug.cgi?id=13461

   Commentary on Issue #30 (longdesc) from the Association of
   American Publishers

   JB: progress was made on this in the TF. They are aware of
   that. Since we are nearly complete with our extension spec, we
   can thank them for offering comment, point to the longdesc
   extension, etc.

13651

   [25]https://www.w3.org/Bugs/Public/show_bug.cgi?id=13651

     [25] https://www.w3.org/Bugs/Public/show_bug.cgi?id=13651

   Missing alt should not be considered conforming in the presence
   of figcaptions over 50 words in length.

   JB: will take time to write up the research I did on this issue
   and determine a threshold
   ... propose it stays assigned to mark and gets reopened in 5.1

   JS: I think the pushback on this was around the specific
   number.

   JB: right we need to justify the threshold
   ... need examples to backup the threshold

Summary of Action Items

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [26]scribe.perl version
    1.138 ([27]CVS log)
    $Date: 2014-02-13 17:24:56 $

     [26] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [27] http://dev.w3.org/cvsweb/2002/scribe/
Received on Thursday, 13 February 2014 17:27:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:37 UTC