RE: [techs] Use cases for techniques

Sorry I wasn't clear. I mean ways people will go through the techniques
documents, the kind of information they're looking for. A person creating a
bus schedule will need to know about tabular markup (probably in the Gateway
Techniques) and the specific HTML codes to use or avoid (in the HTML
Techniques). There are different possible ways they may look for this
information, and we need to make it easy for them to find it regardless of
the route they take. I provided a little more explanation in my post to the
IG list [the archive seems to be down so no URL]. Michael

> -----Original Message-----
> From: John M Slatin [mailto:john_slatin@austin.utexas.edu]
> Sent: Wednesday, September 03, 2003 3:36 PM
> To: Michael Cooper; WAI GL (E-mail)
> Subject: RE: [techs] Use cases for techniques
> 
> 
> Michael,
> 
> To be certain that I understand what's wanted-- please clarify what's
> meant by "use cases" here: do you meanthings for which tables might be
> used, e.g., "A bus schedule is presented with intersections listed
> across row 1 and timepoints shown in the columns below"?
> 
> Thanks.
> John
> 
> 
> "Good design is accessible design." 
> Please note our new name and URL!
> John Slatin, Ph.D.
> Director, Accessibility Institute
> University of Texas at Austin
> FAC 248C
> 1 University Station G9600
> Austin, TX 78712
> ph 512-495-4288, f 512-495-4524
> email jslatin@mail.utexas.edu
> web http://www.utexas.edu/research/accessibility/
> 
> 
>  
> 
> 
> 
> -----Original Message-----
> From: Michael Cooper [mailto:michaelc@watchfire.com] 
> Sent: Wednesday, September 03, 2003 2:30 pm
> To: WAI GL (E-mail)
> Subject: [techs] Use cases for techniques
> 
> 
> 
> In today's techniques teleconference we discussed the structure of
> Gateway Techniques and how they relate to the rest of the
> technology-specific techniques. The problems and benefits of 
> particular
> approaches related to specific use cases, or goals people 
> have from the
> techniques and ways people achieve those goals in our documents. It
> seemed that we did not have a complete of use cases on the 
> table, which
> we need to complete this discussion. Everyone on the call 
> agreed to come
> up with possible use cases during this week, and email them 
> to the list
> so we can review them. We will continue the discussion in the face to
> face meeting next week.
> 
> So people on the list know what's going on when these 
> messages appear we
> thought it best to explain what we're doing. If members of 
> the list who
> weren't on the call would like to contribute use cases, that would be
> welcomed as well. I suggest all use case proposals be posted 
> as a reply
> to this message so we can keep the thread toegher. I will also ask the
> IG list for thoughts.
> 
> Michael
> 
> Michael Cooper
> Accessibility Project Manager
> Watchfire
> 1 Hines Rd
> Kanata, ON  K2K 3C7
> Canada
> +1 613 599 3888 x4019
> http://bobby.watchfire.com/
>

Received on Wednesday, 3 September 2003 16:08:31 UTC