Re: TRACE guidelines

I also had trouble using the TRACE guidelines. However, I have expanded the
suggestion I made for techniques slightly, having reviewed IBM, SUN,
Microsoft, Apple, EITAAC, US Dept of Education, Australian Government
guidelines as well as the TRACE documents.

Assuming that this is the discharging of your action item from the face to
face meeting, I will post my proposals to the list shortly. This represents a
summary of those guidelines, part of the action item I and Ian took from the
teleconference after that meeting to look into producing a W3C Note as a
stable reference.

Cheers

Charles

On Tue, 1 Jun 1999 Bruce_Roberts/CAM/Lotus@lotus.com wrote:

  Wendy gave us a URL (http://trace.wisc.edu/docs/browser/) to check out on the
  TRACE web site.  Phil and I had a look and believe the guidelines offered there
  are too general to be useful to us.  The TRACE guidelines apply more to
  electronic hardware devices and as such aren't readily applicable to software UI
  guidelines.  Here's an example:
  
  "Strategies for ensuring that the surface of controls can be easily
  differentiated tactually from the main surface of a product"
  
  
  I recommend we drop this line of inquiry.
  
  -- Bruce
  
  
  

--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 Tuesday, 1 June 1999 18:09:22 UTC