W3C home > Mailing lists > Public > public-html-a11y@w3.org > March 2012

Text Subteam Minutes for 13 March

From: Janina Sajka <janina@rednote.net>
Date: Tue, 13 Mar 2012 14:58:18 -0400
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-ID: <20120313185818.GA4953@sonata.rednote.net>
Minutes from the 13 March teleconference of the HTML-A11Y Task Force Text
Subteam are provided below in text and can be accessed in hypertext at:

http://www.w3.org/2012/03/13-text-minutes.html


   W3C

                                                           - DRAFT -

                                                        SV_MEETING_TITLE

13 Mar 2012

   See also: IRC log

Attendees

   Present
          Judy, John_Foliot, Janina

   Regrets
   Chair
          SV_MEETING_CHAIR

   Scribe
          janina

Contents

     * Topics
         1. PFWG ARIA task force report, including update on future thoughts about aria describedAT, and implications (or
            not) on longdesc and on issue 204
         2. some thoughts about further revisions on meta-name generator proposal; background links:
         3. confirm CP revisions for WG location of alt guidance http://www.w3.org/html/wg/wiki/ChangeProposals/movealt
     * Summary of Action Items
     __________________________________________________________________________________________________________________

   <scribe> scribe: janina

   <Judy> http://lists.w3.org/Archives/Public/public-html/2011Apr/0451.html

   <Judy> http://www.w3.org/html/wg/wiki/ChangeProposal/meta_name%3Dgenerator_does_not_make_missing_alt_conforming

   <Judy> http://lists.w3.org/Archives/Public/public-html/2012Feb/0237.html

   <Judy> http://lists.w3.org/Archives/Public/public-html-a11y/2012Feb/0141.html

PFWG ARIA task force report, including update on future thoughts about aria describedAT, and implications (or not) on
longdesc and on issue 204

   Janina: PF looked at the Issue-204 page and has no problem with the suggested exemption as stated
   ... However, we also did not see that it did anything to make DescribedBy an acceptable alternative for longdesc.
   ... We see 204 is a nice to have, that's completely orthagonal to @longdesc
   ... We continue to se DescribedBy as inappropriate for longdesc
   ... We did also agree on several documentation clarifications to help the HTML-WG reach appropriate conclusions about
   ARIA

   <Judy> John: My concern is that if we allow describing mechanisms to point to hidden content, it becomes dangerous the
   moment it is combined with tab order focus.

   <Judy> Janina: agreed

   <Judy> John: pls clarify face to face discussion on that?

   <Judy> Janina: our clarifications in the documentation will indeed directly address that so that it will work

   <Judy> John: pls be more specific about how pointing to hidden content will work when combined with tab order content?
   they are mixing and matching at-hidden, and aria-hidden. if that hidden content has anything beyond string text, you
   create an interaction problem for screen reader users

   <Judy> Janina: true, but....

   <JF> Judy: concerned about messaging from PF about pointing to hidden content

   jf: Issue-204 concerns both HTML and ARIA features together

   judy: So ther're several issues, it doesn't help longdesc because it doesn't solve rich text

   jf: also it's messing with ARIA specification

   john: putting longdesc aside ... concerned that namely multiple ways of hiding content

   <JF> I have 3 concerns: Process issue (Issue 204 talks about aria-hidden), issue aroudn pointing to "rich-text", and
   messaging problems (re: feedback from PF F2F)

   judy: What's the status of 204 and longdesc

   john: Extention for Jonas to Mar 10
   ... on 23:30 Mar 10 Matt put up a CP
   ... I've asked for time to respond with a cp

   <JF> http://www.w3.org/html/wg/tracker/issues/204

   general discussion that longdesc needs a fair hearing and resolution

   <JF> http://www.w3.org/html/wg/wiki/ChangeProposals/DeprecateLongdesc

   <Judy> "This will not eliminate the need for longdesc because we cannot introduce tab-focusable content that is hidden
   from sighted users; and because you will not get rich content if you hide it."

some thoughts about further revisions on meta-name generator proposal; background links:

confirm CP revisions for WG location of alt guidance http://www.w3.org/html/wg/wiki/ChangeProposals/movealt

   judy: This is about moving the Alt Text doc to WCAG WG space
   ... Rejected by HTMl Chairs, but still on our table

   discussion that judy will address with steve issues on location of the alt doc

   <JF> http://www.w3.org/WAI/PF/aria-implementation/#include_elements

Summary of Action Items

   [End of minutes]
     __________________________________________________________________________________________________________________

Found Scribe: janina
Present: Judy John_Foliot Janina


-- 

Janina Sajka,	Phone:	+1.443.300.2200
		sip:janina@asterisk.rednote.net

Chair, Open Accessibility	janina@a11y.org	
Linux Foundation		http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative	http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)
Received on Tuesday, 13 March 2012 18:58:48 UTC

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