W3C home > Mailing lists > Public > w3c-wai-au@w3.org > April to June 1999

Re: Comments on Guidelines 2.5, 2.6, and 2.7 of 17 June AU Guidelines

From: Charles McCathieNevile <charles@w3.org>
Date: Mon, 21 Jun 1999 01:01:14 -0400 (EDT)
To: Ian Jacobs <ij@w3.org>
cc: w3c-wai-au@w3.org
Message-ID: <Pine.LNX.4.10.9906210051330.25843-100000@tux.w3.org>
My comments sprinkled throughout - look for IJ and CMN

On Sat, 19 Jun 1999, Ian Jacobs wrote:

  Reference Document:
  1) The first sentence of the rationale sounds like
     an inevitability. I propose rewriting it as follows:
     "When adding features to software, developers must
      ensure that they are integrated into the overall
      "look and feel" of the software. Consistency
      promotes accessibility and acceptance of new features.
Actually, I propose expanding slightly on your text, so it reads

...Consistency promotes both accessibility of the tool and author acceptance
(and therefore use) of new features

However I will not make either change to the draft for the Interest Group on
Monday, unless there is strong support and no dissent from the list during
the day.
  2) Checkpoint 2.5.1: Could be split into two checkpoints.
     Not crucial.
Noted as issue for working group
  3) Checkpoint 2.6.1: Change "which" to "that" several times.
I did a global search/replace for them. One of the features of an Australian
editor I guess *grin*
  4) Checkpoint 2.6.2: What does the "nature of an alert" mean?
     Does this mean "severity"?
I think it means the nature - its severity, the way it appears, etc. I don't
think we should constrain this too much, although we may want to give
examples of possible changes in the techniques document.
  5)  Checkpoint 2.6.3: Change "which" to "that" several times.
CMN Done
  6) Checkpoint 2.6.5: Change "accessibility status" to
     "document accessibility status".
  7) Checkpoint 2.7.2: Change "Explain the use of accessible
     authoring practices" to "Explain the accessible authoring

  8) Checkpoint 2.7.3: Change "Examples must not use
     inaccessible markup" to "Do not use inaccessible markup
     in examples."
These seem like simple editorial changes - unless there is any dissent they
will be made.  

--Charles McCathieNevile            mailto:charles@w3.org
phone: +1 617 258 0992   http://www.w3.org/People/Charles
W3C Web Accessibility Initiative    http://www.w3.org/WAI
MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA
Received on Monday, 21 June 1999 01:01:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:42 UTC