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

10 June UA Guidelines and Techniques available

From: Ian Jacobs <ij@w3.org>
Date: Sat, 10 Jun 2000 01:58:09 -0400
Message-ID: <3941D8F1.D466582@w3.org>
To: w3c-wai-ua@w3.org

I've published the 10 June 2000 version of the UA Guidelines [1]
and Techniques [2]. The full list of changes [3] is online
and quoted below. I believe that this draft includes all of the
resolutions of the Working Group since the previous draft of
7 May 2000.

I think the document is shaping up very well, and although we're
not done yet (see todo list below), we are making very good
progress thanks to this very diligent Working Group!

Eric had suggested [4] that certain changes be in this draft,
and I accommodated 3 of his 5 suggestions (the ones related to
control/configuration and synchronization). For the other
two about usage of terms relating to presentations, Eric and 
Charles and I had a lengthy conversation today out of which
came two proposed changes to the document:

  - One to delete 3.2 and expand 4.0 [5]. This one does not
    appear in the draft.

  - One to clarify 3.3, 3.5, and 3.6 [6]. This one, which 
    I believe to be editorial, does appear in the draft, and
    is subject to review there by the Working Group.

I will take into account Eric's proposed definitions 
concerning multimedia terms [8], his request to ensure
consistent usage, and our discussion today in the next
draft, which I hope to publish as early as next week.

I also updated "Determining Conformance to the User Agent 
Guidelines 1.0" [7] with some more information about
minimal requirements. Not all proposals sent by the
Working Group have been included yet, however.

For the curious, here's a list of things that 
still need to be done (presumably before going to
last call if that is our next step):

1) Once we have resolved all the issues, we need 
   reviewers to sign off on the WG's resolutions. I will
   be sending email to the reviewers to ask them whether they
   think we've addressed their concerns.

2) We need to integrate the minimal conformance information
   into the checkpoints. I'm still not sure of the best
   way to do this, since adding information after each checkpoint
   may lead to an unsightly document (in some cases, 
   the requirements are obvious). The WG already discussed this and  
   preferred the after-each-checkpoint
   approach, but I'm still thinking there's a better solution. 

   The WG also needs to clarify the normative or informative 
   nature of each note after each checkpoint. Is all of that 
   information just commentary, or is some of it key to 
   satisfying the checkpoint?

   Finally, in "How this document is organized", once we have
   established conformance criteria for all the checkpoints, we
   can delete the sentence that reads "Each checkpoint is 
   intended to be specific enough so that someone reviewing 
   a user agent may verify that the checkpoint has been satisfied."
   Instead, we can say that the document states what is expected
   for each checkpoint. In a future draft of the techniques
   document, we can clarify what information is purely descriptive,
   what information concerns minimal conformance, what information
   is reference material, etc.

3)  A few proposed techniques not yet integrated. EH has
    also asked for better descriptions of visuals in the
    techniques document. Here, WG contributions would be
    extremely welcome!!

4) We should begin re-reviewing the implementation report
   in light of changes to the document. That report needs to 
   be updated after last call.

 - Ian

[1] http://www.w3.org/WAI/UA/WD-UAAG10-20000610
[2] http://www.w3.org/WAI/UA/WD-UAAG10-TECHS-20000610
[3] http://www.w3.org/WAI/UA/wai-ua-wd-changes.html
[4] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0425.html
[5] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0434.html
[6] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0435.html
[7] http://www.w3.org/WAI/UA/2000/05/ua-minreqs
[8] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0374.html
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783


  Changes to the Guidelines


     * PDF version is now gzipped (reduced from 10 Megabytes to 600K).
     * Style sheet fixed (was breaking under NN).
     * Changed "application" to "software" in some places, notably in
       definition of "user agent". Based on [7]suggestion from Dick



     * 2.5: Wording changed per [8]chair resolution about checkpoint
     * 3.3, 3.5, 3.6: Changed "turn on/off" to "freeze" per [9]proposal
       for editorial clarification from Ian.
     * 3.8 and 3.9: Split and wording changed per [10]chair resolution
       about checkpoint 3.8.
     * 4.8: Now priority 1 per resolution of [11]8 June 2000 teleconf.
     * 4.10: Wording changed per resolution of [12]8 June 2000 teleconf.
     * 7.6: Wording changed per [13]chair resolution about checkpoint
       7.6. Also, incorporated [14]7.6 edits from EH. Moved part of this
       chckpoint to guideline introduction based on [15]comments from
       Rich Schwerdtfeger.
     * 7.7: Wording changed per resolution of [16]18 May teleconference
     * 8.4: Wording changed per resolution of [17]18 May teleconference.
       Added information to note about the purpose of the checkpoint.
     * 8.8: Wording changed per [18]chair resolution about checkpoint
     * 9.4: Wording changed per [19]chair resolution about checkpoint


   Also, the following checkpoints were affected by the resolution of
   [20]25 May 2000 teleconference to incorporate the [21]changes
   by Madeleine Rothberg about configure and control:
     * Configure and control: 4.8, 4.1, 4.9, 4.10, 7.7, 8.5, 8.7
     * Configure: 2.2, 2.3, 4.2, 4.3, 4.4, 4.11, 4.13, 4.14, 4.15, 4.16,
       9.3. There was no change to the wording of these checkpoints,
       which already used the term "configure".



     * Definition of "native support" modified. Now speaks more clearly
       about implications/benefits of using operating system features,
       and that the UA is not required to make these features available
       through the UI or programatically.
     * Definition of control and configure added, based on [22]suggested
       definition from Eric Hansen and resolution of [23]25 May 2000
     * Definition of synchronization added, based on [24]suggested
       definition from Eric Hansen. Part of Eric's definition was moved
       to the techniques for checkpoint 2.4.


  Changes to the Techniques

     * Clarification to language change techniques based on [25]comments
       from Mimasa.
     * 4.10: Added technique that user agent should allow voice to be
       louder and softer than other audio sources.
     * 9.4: Added comment about gradual image rendering, percentage info
       per Harvey Bingham suggestion.

Received on Saturday, 10 June 2000 01:58:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:27 UTC