- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Mon, 11 Sep 2006 16:24:49 -0400
- To: w3c-wai-au@w3.org
Attendees: - Jan Richards - Greg Pisocky - Tim Boland The three of us agreed that a good way to move forward on the techniques would be for each member to choose a particular authoring tool (or authoring function - e.g. the code editing view of a tool that also offers a WYSIWYG view) and go through the techniques from the perspective of that tool (you may choose to take the view of the developer, the buyer, etc.). The idea is to really focus on the applicability statements and techniques - is anything inaccurate or missing? Do the icons provide a useful guide or not? In order to avoid duplication, please register your intent on the mailing list. Here's a list of possible perspectives (others are possible): WYSIWYG tool (e.g. Dreamweaver's WYSIWYG view) Code level tool Object-Oriented tool (e.g. Visio) Indirect authoring tool (e.g. Desire2Learn) Cheers, Jan Ended early (4:20 ET)
Received on Monday, 11 September 2006 20:25:55 UTC