W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > July to September 1999

Re: Shorter and more URGENT

From: Charles McCathieNevile <charles@w3.org>
Date: Fri, 16 Jul 1999 17:48:03 -0400 (EDT)
To: Judy Brewer <jbrewer@w3.org>
cc: Daniel Dardailler <dd@w3.org>, WAI EO <w3c-wai-eo@w3.org>, ij@w3.org, Wendy Chisholm <chisholm@trace.wisc.edu>, Gregg Vanderheiden <po@trace.wisc.edu>
Message-ID: <Pine.LNX.4.10.9907161746010.10571-100000@tux.w3.org>
I think we are near enough - I'm not sure that we'll get real consensus
except by attrition (in particular, Daniel and I appear to fundamentally
disagree on the importance of noframes), but I think that whatever is decided
is likely to be good enough. Having said that, I'll keep on the thread...

charles McCN

On Fri, 16 Jul 1999, Judy Brewer wrote:

  EOWG, and GL Editors:
  
  STATUS: 
  - Two issues still to resolve: "frames" and "check your work." One new &
  one old proposal below.
  - The printer has gone home for the day. I do not feel we have sufficient
  consensus on #8 or #10 to procede. I would like to get consensus during the
  weekend, and then freeze it while the printer runs the proofs. Please
  continue to comment until we reach consensus.
  
  - Judy
  
  >> 8. Frames. Title frames, and provide _NOFRAMES_ equivalent.
  >
  >I prefer to leave it as is ("Label with ...") or add to a sentence to
  >the effect of making noframe conditional:
  >"and provide NOFRAMES equivalent if too complex" or "if needed".
  >
  >I don't think we should ask people to provide noframe all the time.
  
  JB That point, in combination with Ian's clarifications about NOFRAMES in
  the HTML spec, and the fact that this is a technique not a checkpoint, says
  to me that we should not make this sound so absolute. I don't know,
  however, whether we have space to say it conditionally. Two attempts:
  
  JB PROPOSAL #1: "Frames. Label with _title_ or _name_. Use _NOFRAMES_ if
  complex."
  
  JB Trouble is, it won't fit on the line.
  
  JB PROPOSAL #2: "Frames: Use _title_ or _name_, and NOFRAMES if complex."
  
  JB Anybody like this?
  
  
  >> 10. Check your work. Use evaluation tools, guidelines and checklist
  >> www.w3.org/TR/WAI-WEBCONTENT
  >
  >We already have the WAI URL at the top of the card, I don't think we need
  >another one here, even more if we make sure the guidelines are always
  available
  >for the top of the WAI home.
  >
  >I don't think redundancy looks good on a business card.
  
  JB I was relaying a strong concerned expressed by Gregg-- that people would
  get to the end of the card, and really think that was it. The WAI URL up
  front doesn't lead directly to the guidelines, and we can't guarantee that
  they'll always be at the top of the WAI home page. I've talked with many
  people who haven't found the Quick Tips or the Techniques document after
  visiting the WAI home page many times, and who are fuzzy about which set of
  guidelines they are using as well. If our insurance for having such a
  concise and sometimes cryptic list of Quick Tips, is to know that we are
  emphatically pointing people to the full resource then I agree with Gregg
  that the card would benefit from _some_kind_of_ reminder at the end of the
  card. Maybe there's better phrasing?
  
  JB We even did some informal "user testing" when discussing this at the
  AAES Conference recently -- Gregg and I each handed cards to a few people,
  gave them a short time to look at them (didn't mention whether there was
  anything on the back or not). One noticed the URL on the top, one didn't--
  he thought it was just a design element, etc. Given how important it is to
  get people to the guidelines, maybe this one bit of semi-redundancy is a
  good thing.
  
  >I'd rather just change "text only browsers" in "text only rendering",
  >to point people at lynx-it web page, not just lynx browser.
  
  Right now that's not part of the proposed re-draft; but in any case, I
  wonder if people will understand "text-only rendering" as easily, even if
  "text-only browsers" isn't 100% of what we mean here.
  
  PROPOSAL STILL: Check your work. Use evaluation tools, guidelines and
  checklist www.w3.org/TR/WAI-WEBCONTENT
  
  - Judy
  ----------
  Judy Brewer    jbrewer@w3.org    +1.617.258.9741    http://www.w3.org/WAI
  Director, Web Accessibility Initiative (WAI) International Program Office
  World Wide Web Consortium (W3C)
  MIT/LCS Room NE43-355, 545 Technology Square, Cambridge, MA,  02139,  USA
  

--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 Friday, 16 July 1999 17:48:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:25 GMT