W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2001

Re: Responses to Bryan Campbell issues raised during second last call of UAAG 1.0

From: Ian Jacobs <ij@w3.org>
Date: Mon, 19 Mar 2001 10:28:25 -0500
Message-ID: <3AB62599.F90303DF@w3.org>
To: Bryan Campbell <bryany@pathcom.com>
CC: w3c-wai-ua@w3.org

Your comments seem very reasonable and I will make the suggested
change (unless there are strong objections). Fortunately, the text
you cite is in the Techniques Document, which we will only be
showing to the Director as a proposed Note, not Recommendation.
So I don't think we shall be slowed down a bit. Thank you
for your continued contributions!

 - Ian

Bryan Campbell wrote:
> 16-03-01 you wrote
> >Please indicate before 27 March whether you are satisfied with
> >the UAWG's resolutions, whether you wish the WG to carry forward
> Hello Ian
> The new wording for Guideline 1, seen below, is satisfactory. Another part
> of my submission deals with Techniques in what has now become Guideline 7
> Checkpoint 7.3 paragraph 11 remains unclear. Probably it is unclear because
> the 2nd sentence expresses 2 different thoughts making it very long:
> "Maintain consistency in the user interface between versions of the
> software. Consistency is less important than improved general accessibility
> and usability, but developers should make changes conservatively to the
> layout of user interface controls, the behavior of existing
> functionalities, and the default keyboard configuration."
> Sentence 2 is fine till the 1st comma saying usability is more important
> than consistency, a fact the rest of the sentence appears to contradict. A
> few more words clarifies matters, "Consistency is less important than
> improved general accessibility and usability when adding new controls.
> However,". Replacing the 1st comma with the phrase "when adding new
> controls. However," says do what is necessary for better usability with new
> items while not changing any common default commands. The 2 ideas must be
> in separate sentences so requirements that common defaults are 99.9%
> unchanged is not interpreted as limiting the kinds of commands which may be
> created to give very easy to use Accessibility. Such change will ensure
> that later undue weight is not given to "existing functionalities" as
> governing the Accessibility interface. I formally ask the WG to inform the
> Director of the necessity of this change which I hope wont give the WG too
> much more work as its task turned out to be far more involved than we
> expected. My thanks to the WG for its work & for continuing to ask me to
> review its efforts!
> >[0] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000OctDec/0248
> >===============================================
> >The UAWG agreed with you:
> >#338: Editorial: Edits to Guideline 1 prose re: easy access
> >  Comment: The edited sentences in Guideline 1 about the importance
> >  of keyboard access are:
> >  "Keyboard operation (using as few keystrokes as possible) of all
> >  functionalities offered through the user interface is one of the
> >  most important aspects of user agent accessibility on almost every
> >  platform. The keyboard is available to most users, it is widely
> >  supported, and specialized input devices may reuse the keyboard API."
> >  Please also note the evolution of our keyboard configuration
> >  requirements in Guideline 11
> Those ideas will help developers understand what most increases usability.
> Regards,
> Bryan Campbell
> -> "Trifles make perfection, and perfection is no trifle." Michelangelo

Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783
Received on Monday, 19 March 2001 10:28:32 UTC

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