- From: David MacDonald <befree@magma.ca>
- Date: Sat, 22 May 2004 09:20:27 -0400
- To: "'Gregg Vanderheiden..'" <gv@trace.wisc.edu>, <w3c-wai-gl@w3.org>
- Message-Id: <200405221320.i4MDKEg3005783@mail2.magma.ca>
Gregg says: >>>1) In the guidelines themselves, I think it would be nice to have the links, but have the big long sentences would make it unduly long. How about if after every >>>item in the guidelines, we just simply have 2 one-word links. Perhaps they could be in square brackets to set them off but they would be in the same line as >>>the guidelines so they wouldn't use up an extra vertical line of space. For example: >>>[Checklist] [Techniques] I like that. >>>2) Traffic cop really does cause people problems and also sounds like Bobby, which is not let that function would be >>>I don't have a good final suggestion but some ideas to get us thinking. >>>- Locator >>>- Technique Locator >>>- Customizer Yeah, I knew early on that the name "Traffic Cop" wasn't a keeper. I was just thinking of it as a code name until we had a better name. But I love the concept and basic design of the "whatever we call it." ---------------------------------------------------------------------------- ----------- >>>>On the second illustration where you show the two flow pads off of the guidelines, the first box is the guidelines and the last box at the bottom is either the >>>techniques or the checklists. Between them are two boxes which have a description but not a name. Aren't these really the techniques gateway document and the >>>checklist gateway document? If they are, we might just label those boxes on the diagram with those names and then put the function in parenthesis underneath them. I was going to call these two boxes "mini cops" but thought I better leave them unnamed for obvious reasons. I wasn't thinking of those boxes as the current "Technique Gateway" document which currently contain the "Technology Independent Techniques". I was thinking of them as what you call above a "Locator" . The way into the Techniques from the Guidelines (the left middle box) would be something like this www.eramp.com/david/traffic_cop_from_guidelines.htm The way into the Checklists from the Guidelines (the right middle box of the 2nd diagram) would be something like this www.eramp.com/david/traffic_cop_from_guidelines_checkbox.htm Perhaps on one of our Thursday calls I should explain these use cases that have grown out our Wed Techniques calls. Cheers David MacDonald For those who are wondering, the "Traffic Cop" (or technique locator) is modeled at www.eramp.com/david <http://www.eramp.com/david> Cheers David MacDonald -----Original Message----- From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of David MacDonald Sent: Friday, May 21, 2004 10:23 AM To: Becky_Gibson@notesdev.ibm.com; w3c-wai-gl@w3.org Subject: RE: [TECH] use cases diagrammed Hi Becky I made the adjustment for Use Case persona Andy's printing from the Checklist (not the Techniques). I've posted these use cases to <http://www.eramp.com/david/becky_use_cases.htm> www.eramp.com/david/becky_use_cases.htm <http:// <http://www.eramp.com/david/becky_use_cases.htm> www.eramp.com/david/becky_use_cases.htm> The models for the Traffic Cop and navigation paths through the documents are at www.eramp.com/david/ <http:// www.eramp.com/david/> I also made a temporary Checklist gateway that will serve as a placeholder until I understand all the checklists and how the will look and work together. It is here. Use Case persona Jessica would have sent this URL .http://www.eramp.com/david/checklist_window.htm Cheers David MacDonald --------------------------------------------- .Access empowers people. .barriers disable them. <http://www.eramp.com/> www.eramp.com _____ From: Becky_Gibson@notesdev.ibm.com [mailto:Becky_Gibson@notesdev.ibm.com] Sent: Friday, May 21, 2004 10:16 AM To: w3c-wai-gl@w3.org Cc: David MacDonald Subject: Re: [TECH] use cases diagrammed Thanks very much to David for wading through my use cases and creating the drawings! I think his diagram in the posting from <http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0333.html> http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0333.html captures everything that these use cases require - I just needed to create a "real world" scenario to wrap my head around them better! I also don't fully understand the checklists and how they will be organized. I liked his example at <http://www.eramp.com/david/benshtmlchecklist.htm> http://www.eramp.com/david/benshtmlchecklist.htm. I also envision one page that is able to encapsulate the entire checklist for a specific technology but that may be too complicated. I agree that it is probably too complicated to add all the checklist links to the traffic cop but it would be a good idea to add a link to the checklist gateway from there. I would like to see a link to the checklist gateway in the cell/row for each guideline. It seems like overkill since it will be the same link in each cell but a person may enter the traffic cop in the middle and not find a checklist gateway link at the top or bottom of the page. Also, do you think it makes sense to add a link to the checklist from the success criteria page? This will allow direct access to a checklist with just one hop from the traffic cop. That may be too complicated to maintain, though, but I think it would be helpful. In the Jessica example you have: 1) The first link she sends is here: <http://www.eramp.com/david/traffic_cop_from_guidelines_checklists.htm> http://www.eramp.com/david/traffic_cop_from_guidelines_checklists.htm This actually takes you to a checklist gateway for a particularly guideline. I was envisioning a Checklist Gateway that is not guideline specific and allows you to select a technology. I then assumed that Andy would pick the HTML or CSS set of checklists. But, this gets back to how the checklists are organized - is it possible to have all of the checklist for one technology in the same document? One other minor nit in the diagram is that I expected Andy to print an HTML checklist. You have the printing from the techniques (which is also a good idea) branch. I just wanted to include printing so we would think about it when we designed the checklist page. thanks, -becky Becky Gibson Web Accessibility Architect IBM Emerging Internet Technologies 5 Technology Park Drive Westford, MA 01886 Voice: 978 399-6101; t/l 333-6101 Email: <mailto:gibsonb@us.ibm.com> gibsonb@us.ibm.com "David MacDonald" <befree@magma.ca> Sent by: w3c-wai-gl-request@w3.org 05/20/2004 10:14 AM To <w3c-wai-gl@w3.org> cc Subject [TECH] use cases diagrammed My action item was to make drawings and comments on Becky's use cases. My drawings are simple box diagrams so that "lay people" can easily understand them. They are based on UML principles but not strict UML (to avoid visual jargon that might not be understood by all and inaccessible). I've posted these use cases to <http://www.eramp.com/david/becky_use_cases.htm> www.eramp.com/david/becky_use_cases.htm. The models for the Traffic Cop and navigation through the documents is at <http://www.eramp.com/david/default.htm> www.eramp.com/david/default.htm Wendy has asked me to send these links to the list for review by anyone who wishes. Cheers David MacDonald --------------------------------------------- .Access empowers people. .barriers disable them. <http://www.eramp.com/> www.eramp.com
Received on Saturday, 22 May 2004 09:21:33 UTC