Change log: Planning a Web Accessibility Training - ASSESMENT F0R CA MEETING

Change requests from 24 March 2002

• brainstorming about tutorials & templates [X - LONG TERM LOOK-SUGGEST REVIEW/CREATE UPDATED WISH LIST THAT IS 1) UNDERSTANDABLE AFTER LONG ABSENSE, 2) ELIMINATES ITEMS, 3) REFRAIN FROM ADDING NEW ITEMS FOR NOW]
  • wcag techniques -- being updated, modular, able to be linked to [**DUSTING OFF]
  • mock up page w/ explanation behind it [X - COMPLICATED ISSUE]
  • page of links w/ short info that goes out to different types of info, plug and play examples, best practices examples, etc., [X - TIME CONSUMING]
  • drop in on a faq, w/ buttons saying "simpler" or "more technical" -- allows them to adjust the level of answer they are looking for [X - NEEDS DISCUSSION]
  • if all in central database, can draw out, easier to maintain [**SOUNDS LIKE A "WHY" ITEM]
  • include ud perspective somewhere
  • think about what can link to from html document as well, multiple means of navigation [**DUSTING OFF]
  • think how designers think, especially when they are just getting started [X - NEEDS DISCUSSION]
  • help developers figure out how to use their own tools accessibly [X - COMPLICATED ISSUE]
  • extract summaries as a start [***FROM WHERE?]
  • ensure peer review of the materials [**SOUNDS LIKE A "WHAT" ITEM]
  • think about how to link to external materials that relate to our goals [X - COMPLICATED ISSUE]
  • template=fish, implementations of accessible code; tutorial=how to fish
  • having a way to sort the material to better match the intent of the user X - [USER-CENTERED DESIGN DISCUSSION]
  • eowg: keep figure out how to help people find the right info & tools, better examine the user needs, [X - USER-CENTERED DESIGN DISCUSSION]
  • [ertwg dev aert, going on more in wcag now... so we also need to look at getting people to the eval resources] [X - NEEDS DISCUSSION]
  • [tutorials great idea, can be done little piece by little piece] [**COMMENT ON APPROACH]
  • [look at examples on ibm site, think about blank templates, useful] [X - NEEDS DISCUSSION]
  • templates mainly addressing the issue of navigability and orientation... does not make it comprehensible for people... perceivability not well reflected... [X - NEEDS DISCUSSION]
  • think about the audiences of whole-page templates as including those who commission the design...contextual examples can do that... [X - NEEDS DISCUSSION]
  • template: eowg should name the fish. [**COMMENT ON APPROACH]
    1. plug and play page (less important)
    2. page that drives delivery of content (industry's resp)
    3. general guideline for critical formating (explanation) (eowg)
  • eowg operating as requ gathering arm, wcag how to arm..... [***WHAT IS THIS?]
  • template: a framework into which you plug code, vs sample code, what you plug in
  • don't hijack words, doesn't work [**DUSTING OFF]
  • existence proofs, important to have [***WHAT IS THIS?]
  • ...bobby learning tool... eowg should look at it [***TO WHAT PURPOSE?]

Change requests from 13 March 2002

• http://www.w3.org/WAI/EO/Drafts/training/ra.html
  • broaden up the impact in #1, aging, etc., device independence, electric fences etc. [OR and its impact on everyone including pwd]: start w/ clear focus on people w/ disabilities -- and then expand it to include aging etc., and carry-over benefits to other situations. [**DUSTING OFF]

Change requests from 22 February 2002

• http://www.w3.org/WAI/training/ra
  • #4designing: update links to WCAG modules [LP & AG looking at those resources to compare against the newer modules] [**DUSTING OFF]
  • #4designing: replace link to selecting software [**DUSTING OFF]
  • #5evaluating: point to how to evaluate for web accessibility, separate pointers to prelim & comprehensive [**DUSTING OFF]
  • consider adding in intros & advanced -- let people decide -- hurdle? red flag? (text) [***WHAT DOES THI MEAN?]
• tutorial modules wishlist.... what if we made little tutorial modules about the most intractable design problems, take a design problem from top to toe (these are ideas generated from EOWG discussion 02/22): [*****GEMS??? - JUSTIN & VINCENT?]
  1. how to design tabbed-like navigation
  2. how to design client-side image maps
  3. how to design drop-down list box menus
  4. how to design cascading or fly-out menus
  5. how to design multicolumn layouts
  6. how to design frame alternatives
  7. how to design effective cross-platform css-based page layout [MUCH NEEDED!!!!!]
  8. alt text demystified
  9. how to design data tables with navigation aids
  10. mathml in design
  11. how to set up keyboard shortcuts or to expose standards
  12. specifying page measurements
  13. setting up an accessible forms & communicating on validations errors