- From: Yeliz Yesilada <yesilady@cs.man.ac.uk>
- Date: Thu, 17 Jun 2010 09:11:47 +0300
- To: wai-eo-editors@w3.org
Unfortunately, I couldn't add all my comments to the questionnaire as I was getting an error from the server. Here is the rest of my comments. === <http://www.w3.org/WAI/training/topics.html> This document includes a comprehensive set of topics and it is well written. You can find some comments below: * priority: editor's discretion * location: opening paragraph, second sentence * current wording: "Other parts of this resource provide Presentation Outlines and a Training Outline that use these topics" * suggested revision: "Other parts of this resource provide Presentation Outlines and a *Workshop* Outline that use these topics" * rationale: The link label says training but it is linked to a page that uses workshop in the title, so to be consistent I would change that to workshop. * priority: editor's discretion * location: topics in general * current wording: Most of the topics currently focus on developers, advocates, etc, but I wonder if some presentation topics can be added targeting end users (training end users) * suggested revision: For example, "How to complain? or how to contact organisations about their inaccessible web sites?", or "Better Web Browsing <http://www.w3.org/WAI/EO/Drafts/adaptive/ strategies.html>" * rationale: people in training end users might find these topics useful. * priority: editor's discretion * location: topics in general * current wording: Managing Accessibility topics * suggested revision: What about adding another topic that discusses the relationship between Search Engine Optimisation and Accessibility * rationale: I think there are a lot of people interested in search engine optimisation. * priority: editor's discretion * location: "Tips and suggestiins" section in all topics * current wording: All the tip sections are organised around "demonstration, question, tip, activity" * suggested revision: I suggest to highlight this categorisation * rationale: To improve scan-ability * priority: editor's discretion * location: "What the audience will learn" section in all topics * current wording: In some topics, it says "know where to get more information" * suggested revision: I suggest to add this to all topics or may be consider to add this to most of them * rationale: From what I can see from all the topics discussed this would be a learning outcome in all, or may be in most of them. * priority: editor's discretion * location: Topic 1, "What the audience will learn" section * current wording: "Know about international efforts to ensure web accessibility" * suggested revision: I suggest to drop this * rationale: I cannot see how the audience will learn about this by looking at the rest of the topic discussion * priority: editor's discretion * location: Topic 3, "Goal" section * current wording: "Introduction to WAI's three sets of guidelines that contribute to an an accessible web." * suggested revision: "Introduction to WAI's three sets of guidelines that contribute to an accessible web." * rationale: "an" is repeated. * priority: editor's discretion * location: Topic 3, "Tips and suggestions" section * current wording: * suggested revision: Add a discussion point: "Ask participants to think about the key players in Web interaction: what are the key players in Web interaction? Is it enough to make one of them accessible?" * rationale: This will get the participants think and visualise the key players in mind and also enable them to conclude themselves that accessibility has to be considered as a whole with all these key components in mind. * priority: editor's discretion * location: Topic 9, "Tips and suggestions" section * current wording: * suggested revision: Add a discussion point: "Ask participants to think what an authoring tool is, what would be the best way to define an authoring tool, would they consider some web sites as authoring tools?" * rationale: These questions will enable the participants to see that Web authoring is not only about CMS, it is also about web sites that can used to contribute content, etc. * priority: editor's discretion * location: Topic 10, "Tips and suggestions" section * current wording: * suggested revision: Add a demonstration point: "Show a before and after demo, for example show how a slider/drag and drop or navigation item used before ARIA and after with ARIA" * rationale: I think this would be a good demonstration of benefits of using ARIA * priority: editor's discretion * location: Topic 11, "Resources" section * current wording: * suggested revision: Add WAI resources that show the relationship between mobile Web and accessible Web * rationale: Since mobile web is used as a demonstration item * priority: editor's discretion * location: Topic 12, "what the audience will learn" section * current wording: * suggested revision: I suggest revising and shortening the list of learning outcomes * rationale: I think based on the description of this topic, the learning outcomes listed there look ambitious to me. * priority: editor's discretion * location: Topic 15, "audience" section * current wording: Web developers; procurement personnel; web policy makers * suggested revision: I think Topic 11 audience can also be added here "Web accessibility advocates, web site managers and other management staff who need data to inform decisions about the return on web accessibility investment" * rationale: The relationship can be used to show the business case for accessibility * priority: editor's discretion * location: Topic 15, "Handouts" section * current wording: there is no handouts section * suggested revision: I think this resource could be added to the handouts section: "http://www.w3.org/2007/02/ mwbp_flip_cards.html" and also WCAG 2.0 at a glance "http:// www.w3.org/WAI/flyer/Overview.html#glance" * rationale: Could be useful to handout in the presentation === === <http://www.w3.org/WAI/training/workshop-outlines.html> * priority: editor's discretion * location: "Overview" section, "Target audience" * current wording: All 3 days...Days 1 and 2...Day 1... * suggested revision: I would re-order them so "Day 1...Day 2...All 3 days..." * rationale: starting from first day would be easier to see the focus * priority: editor's discretion * location: "Overview" section, "Target audience" * current wording: Website developers, application programmers, Web authors, visual designers, non-technical developers (used in the other parts of the document) * suggested revision: I think it would be good to briefly define these somewhere * rationale: In the rest of the document, these terms are used quite a lot in the audiences part, and I personally found it hard to see the differences === Regards, Yeliz -------------------------------------------------------- School of Computer Science The University of Manchester Manchester M13 9PL URL: http://www.cs.man.ac.uk/~yesilady/ Tel: +44 (0) 161 275 6239 Fax: +44 (0) 845 139 5599 --------------------------------------------------------
Received on Thursday, 17 June 2010 06:12:20 UTC