Re: waicard9

> 1.  Can we put a revision control number on the cars.  Very small print and
> possibly in on corner.  I fear that as these circulate and revisions are
> made, we may not know which version of which we are speaking.

I think it's possible but I wonder how useful it will prove to
be. First I think we're not going to have many versions of this card,
maybe 2 or 3 at most. I may be wrong. In any case, whatever feedback
we receive is going to be specific, as in "I don't undestand what
'read out of context' means" and we will know which version we're
talking about. I don't expect software-like report ala "tips 3 on
page 2 is unclear", which would indeed call for a version id.
 
> 2.  Use CSS for layout and style.  I could not agree more with this.
> Suggest,
> "Use CSS for layout and style where practical", or

Hard to define "practical". I would argue it is practical to use CSS
today, for maintenance of one organization's graphic chart for
instance. It is not practical if you want your data to appear the same 
on all browser in the world. 

The guidelines use "wherever possible", that we could reuse here. What
others think ?
 
> 3.  Last item, wish we had room to say something about also testing on voice
> web browsers and screen readers.

We discussed that point last week, in the context of removing "Test
with images, sound, and animation off." The consensus was that
evaluation tools provide this service.

Received on Wednesday, 3 February 1999 09:12:46 UTC