W3C home > Mailing lists > Public > public-wcag2ict-tf@w3.org > November 2012

Re: WCAG2ICT 2nd Public Draft

From: Andi Snow-Weaver <andisnow@us.ibm.com>
Date: Thu, 29 Nov 2012 16:08:16 -0600
To: Michael Cooper <cooper@w3.org>
Cc: "'Bailey, Bruce'" <Bailey@Access-Board.gov>, David MacDonald <david100@sympatico.ca>, "'Judy Brewer'" <jbrewer@w3.org>, "'Peter Korn'" <peter.korn@oracle.com>, public-wcag2ict-tf@w3.org
Message-ID: <OF1AEDF732.38B030C5-ON86257AC5.00798767-86257AC5.00799B92@us.ibm.com>
We have an action item to discuss the organization and layout of the
document. As Michael said, this is a discussion for after this next


From:	Michael Cooper <cooper@w3.org>
To:	David MacDonald <david100@sympatico.ca>
Cc:	"'Peter Korn'" <peter.korn@oracle.com>, "'Bailey, Bruce'"
            <Bailey@Access-Board.gov>, public-wcag2ict-tf@w3.org, "'Judy
            Brewer'" <jbrewer@w3.org>
Date:	11/29/2012 03:09 PM
Subject:	Re: WCAG2ICT 2nd Public Draft

Regarding expanding / collapsing sections in the document, short answer -
at the very least, not for this round.

There has been an on-again off-again effort to modernize the style of W3C
TR documents, and introducing expanding / collapsing suggestions is
certainly something people want to do. But so far, these efforts haven't
come to a level of maturity that they have been taken up as on TR

Furthermore, to make it accessible, we'd have to use ARIA. The way W3C
rules work, you can't use a spec as the DTD of a document in TR until that
spec is a W3C Recommendation. So we're not allowed to use ARIA until that
spec matures. The PFWG has been investigating exceptions to this rule but
there isn't one in place yet.

I would not want to make WCAG2ICT a test case for either the style choice
nor for the exception to allow ARIA in the spec. Particularly not when
starting to explore the issue just a week before hoped publication. If this
is something the TF really wants to do, we can explore it with greater
lead-time for the next publication.

If you want to make changes to how Understanding content is included, we
can explore that. But I wouldn't want to get into anything too radical on
that either just before publication. It's also something the TF could
explore with greater lead-time for the next publication.


David MacDonald wrote:
      I totally support that, although perhaps the W3C document publishing
      requirements may be a hurdle. I’ve never seen an accordion widget on
      a w3C doc.

      Judy or Michael?

      David MacDonald

      CanAdapt Solutions Inc.
        Adapting the web to all users
                  Including those with disabilities

      From: Peter Korn [mailto:peter.korn@oracle.com]
      Sent: November-29-12 2:10 PM
      To: Bailey, Bruce
      Cc: public-wcag2ict-tf@w3.org
      Subject: Re: WCAG2ICT 2nd Public Draft

      Bruce, gang,

      Since our output is a web document, I wonder if we might have the
      text of the SCs and Intent in expanding/collapsing blocks, which by
      default are collapsed when we publish the document.  That way only
      "our" text is immediately visible, but the full content can be shown
      in context.


      On 11/29/2012 5:51 AM, Bailey, Bruce wrote:
            I respectfully request that we revisit the decision to have the
            full excerpts of the verbatim success criteria and Intent
            sections from the Understanding document.  It really makes it
            hard to digest our “value added” work.  Closely tracking Intent
            was important to the process, but as part of our final
            deliverable, it is quite counterproductive IMHO.

            That said, this exercise makes the case that this sort of
            stand-alone version of Understanding WCAG 2.0, which is limited
            to only Intent, would be a valuable addition to the WAI
            document collection.

            From: Andi Snow-Weaver [mailto:andisnow@us.ibm.com]
            Sent: Wednesday, November 28, 2012 11:14 PM
            To: public-wcag2ict-tf@w3.org
            Subject: WCAG2ICT 2nd Public Draft

            The editors are still reviewing the draft but it's good enough
            for you all to start looking at it.


            I'll send out a survey early tomorrow where you can put your



      Peter Korn | Accessibility Principal
      Phone: +1 650 5069522
      500 Oracle Parkway | Redwood City, CA 94065
      Oracle is committed to developing practices and products that help
      protect the environment


Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org
Information Page

(image/gif attachment: graycol.gif)

Received on Friday, 30 November 2012 00:39:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:17:47 UTC