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

Report from WCAG Working Group meeting today

From: Andi Snow-Weaver <andisnow@us.ibm.com>
Date: Thu, 19 Jul 2012 20:37:50 -0500
To: public-wcag2ict-tf@w3.org
Message-ID: <OF3680B16F.78511C2A-ON86257A40.007D7F89-86257A41.0008F515@us.ibm.com>


ACCEPTED AS PROPOSED
   * 1.3.1 Info and Relationships
   * 1.4.2 Audio Control
   * 1.4.4 Resize Text - although we have an action to revisit Christophe's
   comments after we publish the draft
   * 3.3.2 Labels or Instructions
   * 3.3.3 Error Suggestion
   * FRONTMATTER

ACCEPTED WITH MODIFICATIONS

   * 1.3.2 Meaningful Sequence

      WCAG WG thought that the note was better addressed in WCAG 2.0 intent
      as it is applicable to both web and software. They accepted 1.3.2
      with the note removed from our guidance and agreed to add similar
      content to the end of the intent, slightly modified with additional
      text in [bold brackets] as

      For clarity:

          1. providing a particular linear order is only required where it
      affects meaning.
          2. there may be more than one order that is "correct" [(according
      to the WCAG 2.0 definition)]
          3. only one correct order needs to be provided.

   * 2.4.3 Focus Order

      WCAG WG thought that the note was better addressed in WCAG 2.0 intent
      as it is applicable to both web and software. They accepted 2.4.3
      with the note removed from our guidance and agreed to add similar
      content to the end of the intent, as follows:

      For clarity:

          1. focusable components need to receive focus in an order that
      preserves meaning and operability only when navigation sequences
      affect meaning and operability.
          2 in those cases where it is required, there may be more than one
      order that will preserve meaning and operability
          3. if there is more than one order that preserves meaning and
      operability, only one of them needs to be provided

   * 2.4.6 Headings and Labels - accepted with the note reworded FROM "Note
   that in software user interfaces, headings and labels are used to
   describe [blocks of text and controls] respectively." to "Note that in
   software user interfaces, labels and headings are used to describe
   [controls and sections of content] respectively."

   * Introduction - accepted with the following two edits:

      2nd paragraph: change "This draft document is intended to help make
      non-Web ICT more accessible to people with disabilities." to "This
      draft document is intended to help clarify how to use WCAG 2.0 to
      make non-Web ICT more accessible to people with disabilities."

      6th paragraph, change "what WCAG 2.0 Conformance means" -> "what WCAG
      2.0 Conformance would mean"

   * 3.3.1 Error Identification and 3.3.3 Error Suggestion proposed edits
   to intent accepted with the word "software" changed to "system"

SC THAT HAVE THE TEXT '(see Introduction for how to interpret "content")'

   WCAG WG would like us to either describe what "content" means in the
   introduction, or remove all of the sentences from the WCAG2ICT TF
   comments that say " See introduction for the way to interpret content.
   The definition in 1.3.2 is acceptable to WCAG WG if the task force would
   like to use it.

   * 1.4.3 Contrast (minimum) accepted with the text '(see Introduction for
   how to interpret "content")' removed

DID NOT ACCEPT

   * 2.4.2 Page Titled - we ran out of time on this one but they did
   recommend that we find a different term for "title attribute" used in
   the comment on documents to avoid confusion with HTML title attributes.

Andi
Received on Friday, 20 July 2012 01:43:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 20 July 2012 01:43:25 GMT