Education & Outreach Working Group (EOWG) Deliverables

Introduction | Index | Deliverables | EOWG Home

Introduction:

• test link Where from: These deliverables are taken from the EOWG Charter, related WAI-TIDE workpackages, and EOWG discussions.
• Development: EOWG deliverables will be produced by EOWG members, or under subcontract, or by delegation to WAI staff.
• Process:The EOWG will review at least one draft of each of the EOWG deliverables, and comments will be incorporated to the extent appropriate. The WAI Interest Group will also be asked for comments. W3C is the final arbiter of materials release.
• Priority: There are three general priority levels: high, regular, later.

Disclaimer:

This deliverables list is for on-going planning use by the WAI Education & Outreach Working Group (EOWG).  Because it is a planning document, items, priorities, owners, etc. will change over time as the project progresses and as we re-assess project needs and resources.  In particular:

• the URL's listed here are temporary,  and SHOULD NOT be bookmarked as reference materials;
• proposed timelines are subject to change;
• links to EOWG discussions of deliverables are incomplete;
• all materials linked from here should be considered as "DRAFT" unless they are also linked from the WAI resource area at http://www.w3.org/WAI.

Index of Deliverables:

1. Planning Information
   1. Strategies/Timelines High. DONE, needs on-going updating.
   2. Events Calendar/Coverage High. DONE, needs on-going updating.
   3. Translation & Localization Regular. Almost done, needs final edits.
   4. Baseline Data on Web Accessibility, & Impact Regular. Started.
2. Promotional & Outreach Materials
   1. WAI Web site High. In progress. Needs on-going additions & tuning.
   2. Bulletin High. In progress.
   3. Dissemination Points High. In progress.
   4. Press Coverage High. In progress.
   5. Brochures High. In progress.
   6. Pointers Flyer High. DONE, but needs updating.
   7. Literature Stuffer. High. DONE, but needs updating.
   8. Quick Tips Reference Card High. DONE.
   9. Articles/Chapters/Books Regular. Some done, some on-going.
   10. Targetted Promotions/Outreach Regular. Not started.
3. General Reference Materials
   1. Policy References High. DONE.
   2. Business Case High. Started.
   3. Demographic Information Regular. Started.
   4. Scenarios Regular. In progress.
   5. Related Activities Listing Regular. Started.
   6. Consultant List Later. Not started.
4. Technical Reference Materials
   1. Narrative Descriptions of HTML4 Accessibility Improvements High. DONE, but needs revision.
   2. Narrative Descriptions of CSS2 Accessibility Improvements High. DONE. Revision also almost done.
   3. Narrative Descriptions of SMIL Accessibility Improvements DONE!
   4. Narrative Descriptions of MathML Accessibility Improvements High. Not started.
   5. Sample Implementations of Tables Regular. See note.
   6. Sample Implementations of Interactive Forms Regular. See note.
   7. Sample Accessible Style Sheets Regular. Started.
5. Instructional Materials: Curricula & On-Line Learning
   1. Existing Curricula Regular. Started.
   2. WAI Overview High. Almost done.
   3. Web Content Accessibility Guidelines On-Line Curriculum High. Almost done.
   4. User Agent Guidelines/ User Interface Issues Later. Not started.
   5. Authoring Tool Guidelines/ Prompting, Alerts, Help Text Later. Not started
   6. CSS1&2/Creative & Accessible Design Later. Not started.
   7. XML & JAVA Later. Not started
   8. Business Case/ Implementation Promotion Regular. Not started
   9. User Information & Involvement/ Related Projects Regular. Not started
   10. Trainer Prep: Accessibility Overview & Resources for Web Design Instructors Regular. Not started.
6. Demonstration Materials
   1. Rotating Gallery of Accessible Sites. High. Started.
   2. Demo Accessible Web sites High. Started.
   3. Web Sites that Work Regular. Almost done.
   4. Alternative Browsers Regular. DONE.
7. Training Programs & Coordination with Trainings
   1. Trainer Best Practices Exchange Later. Not started
   2. Web Content Developer Workshops Regular. On-going.
   3. Training & Certification Programs Regular. Started.
   4. Review Teams for accessible sites. High. Started.
8. For EO Reference: WAI-TIDE Workpackages
   1. Internet book for VIP's
   2. Web site for page developers
   3. Web site for users
   4. Leaflet suite

DELIVERABLES LIST

1. EO Planning Information

1.1 Strategies & Timelines

• What: List of planned education/outreach deliverables, with priorities, owners, status, etc., info
• Owner: Brewer
• Priority/Status: High. DONE, needs on-going updating.
• URL: This page: <http://www.w3.org/WAI/EO/EO-Deliverables>
• Localization: Deliverables list should be reviewed to reflect localization concerns
• Stability: Update at before or after each EOWG meeting
• Discussion: January 8, 1999; December 11, 1998; December 4, 1998; July 30, 1998; July 16, 1998; July 2, 1998; March 3, 1998

1.2 Events Coverage

• What:
  • Events calendar listing Web industry events, government IT conferences, disability conferences, other events with key audiences needing awareness-raising or technical training on Web accessibility.
  • Input system for WAI IG members to share information with events calendar owners.
  • Feeds into coverage system which notifies WAI EOWG & WAI IG members of upcoming submissions deadlines for key events.
  • Tracks relevant presentations.
• Owner: Barnicle & Allan, Dardailler liaison, Loughborough flagging upcoming events
• Priority/Status:
  • High. DONE, but needs lots of on-going updating.
• Localization: Critical. Need more info outside of the U.S.
• Stability: Needs to be updated at least on a montly basis.
• URL: http://www.w3.org/WAI/References/Events.
• Notes:
  • Dependencies with the Trainer Best Practices event. Would be good to develop an experts' speakers bureau and get more of these events covered.
  • Needs more staff resources.
• Discussion: December 4, 1998; November 6, 1998; October 29, 1998; October 8, 1998; October 1, 1998; September 17, 1998; August 13, 1998; August 13, 1998 about WWW8

1.3 Translation & Localization

• What: Prioritized plan for translation of given documents into given languages, with resources & timelines identified
• Owner: Steve Tyler, Judy Brewer
• Priority/Status: Regular. Almost done, needs final edits.
• Localization: needed
• Stability: Needs constant updating as translations become available
• URL: http://www.w3.org/WAI/EO/Translation.html 
  • First translation of WAI EO materials! A Finnish version of the WAI Pointers flyer (check back later for an updated URL)
• Notes: Possible criteria for what to translate: stable, key reference materials, promotion materials.
• Discussion: --

1.4 Baseline data on accessibility & impact over time

• What: Data collection on impact that WAI is having on Web accessibility; analysis of which activities are contributing to or detracting from project success; recommendations for changes in activities.
• Owner: Brewer
• Priority/Status: Started. Regular. Started.
• Localization: No
• Stability: Update quarterly?
• URL: not yet
• Notes: As of October 1998 starting to coordinate with W3C Web Characterization Activity to coordinate on some measurements of the Web.
• Discussion: October 22, 1998
• Discussion: November 13, 1998
• Discussion: December 4: federal role? clipping service? Jamal -tracking attitude changes over time?

2. Promotional & Outreach Materials

2.1 WAI Web Site

• What: WAI Web Site
• Owner: Brewer (for now)
• Priority/Status:
  • High. DONE, needs on-going additions & tuning.
  • Clean-up & re-organization high priority; next generation design "later"
• Localization: Can pursue mirroring arrangements with appropriate cautions
• Stability: Should be updated weekly.
• URL: <http://www.w3.org/WAI>
• Notes: This topic used to be "Interactive Web site/ Mirroring/ CD-ROM.Discussions in June 1998 (?) agreed those would likely be unstable (the CD-ROM).
• Discussion: Re-org of current WAI home page: December 18, 1998

2.2 Bulletin

• What: Concise monthly update of WAI activities, to go to very broad public audience.
• Owner: Judy Brewer
• Priority/Status:
  • High. Not started.
  • Drafted. Dissemination list needs to be fixed.
• Localization: Translation advised.
• Stability: Changes monthly; format consistent.
• URL:
• Discussion: October 1, 1998

2.3 Dissemination Points

• What: Listings of contact points for different audiences for outreach.  Should include at least: diverse media, industry, disability, research, government contact points.
• Owner: Brewer, Neff, Fink
• Priority/Status:
  • High. Not started.
  • In progress: some compilation already, good brainstorm at prior EOWG meeting
• Localization: Critical
• Stability: Needs a mechanism for regular updating
• URL: (first draft) <http://www.webspots.net/eo/pr_list.htm>
• Notes: Dependency with Bulletin & targetted outreach
• Discussion: September 3, 1998
• Discussion: January 8, 1998

2.4 Press Coverage

• What: A compilation of press coverage to date on WAI & related press on Web accessibility
• Owner: Brewer, Fink
• Priority/Status: Regular. In progress: some compilation already, needs to be finished & then maintained
• Localization: should be comprehensively international
• Stability: needs constant updating
• URL: not yet
• Notes: This is a compilation of press coverage to date, including WAI-related coverage & general Web accessibility coverage
• Discussion: December 11, 1998

2.5 Brochure(s)

• What: Promotional brochures on WAI & Web accessibility.  Issue statement, intro to project, a few starting tips, pointers to resources.  Hard copy, professionally designed; alternative formats available.
• Owner: Brewer & Tyler (RNIB may help with review of contents and or one or more translations)
• Priority: High (single basic brochure is high priority, additional brochures may come later)/Status: In progress
• Localization: as much as possible
• Stability: Update annually?
• URL: won't be one?
• Notes: Volunteer reviewers: Loughborough, Allan, Sethuraman, Bosher, Letourneau.
• Discussion: October 1, 1998

2.6 Pointers Flyer

• What: One-page project description with list of pointers to WAI & W3C URL's, can be printed out for workshops
• Owner: Brewer
• Priority/Status: High. DONE. Needs revision.
• Localization: As much as possible
• Stability: Update quarterly?
• URL: <http://www.w3.org/WAI/Resources/Pointers-flyer>
• Notes: Also available in Finnish!
• Discussion: October 1, 1998

2.7 Literature Stuffer

• What: One-page stiff paper description with list of pointers to WAI & W3C URL's, with tear-off Quick Tips cards at bottom of page.
• Owner: Brewer
• Priority/Status: High.DONE, but needs to be updated to reflect that the WCAG are done.
• Localization: As much as possible
• Stability: Update only when guidelines go to Recommendation.
• URL:
• Discussion:

2.8 Quick Tips Reference Card

• What: Business-card sized "Quick Tips" reference card. Maximally concise conceptual capture of Web Content Accessibility Guidelines (WCAG), with URI of where to go for more information.
• Owner: O'Brien, Bingham, Cantor
• Priority/Status: High. DONE.
• Localization: Translations needed (and underway).
• Stability: Annual updating?
• URL: <http://www.w3.org/WAI/References/QuickTips>
• Discussion: December 4, 1998, November 13, 1998, November 6, 1998, October 22, 1998, October 8, 1998, September 3, 1998, August 13, 1998, August 3, 1998

2.9 Articles/Chapters/Books

• What: A variety of published materials describing Web accessibility issues, including technical and general interest articles; generic materials to be integrated throughout chapters in Web authoring manuals; books on Web accessibility. These materials may be developed on a free-lance basis or externally to WAI, but where possible can be coordinated with WAI resources and message.
• Owner: Dardailler? Others?
• Priority/Status: Regular. Paciello book almost done (external to WAI but somewhat coordinated).
• Localization: needed
• Stability: Will need frequent updating & generation of new material.
• URL: not yet
• Discussion: August 13, 1998

2.10 Targetted Promotions/Outreach

• What: Mini-outreach campaigns to specific audiences, such as writers' associations, government agencies, libraries, assistive technology developers; and/or a planned & sustained promotional campaign with a PR firm
• Owner: Brewer
• Priority/Status: Regular. Not started
• Localization: needed
• Stability: Each mini-campaign is new.
• URL: --
• Notes: Offer for coordination w/ PR agency. Need to reschedule.
• Discussion: ATIA Outreach, December 18, 1999
• Discussion: Possible PR Campaign, January 8, 1999

---

3. General Reference Materials

3.1 Policy References

• What: Reference collection of laws, regulations and policies related to Web accessibility. Collection should include materials from any countries which have or are developing such policies.
• Owner: Brewer
• Priority/Status: High. DONE. Needs some links fixed, added.
• Localization: Critical. Compile info from WAI IG list contacts
• Stability: Will need to be updated as additional policies are developed.
• URL: http://www.w3.org/WAI/References/Policy
• Notes: Ready for broaden input & checking
• Discussion: October 22, 1998
• Discussion: October 29, 1998
• Discussion: November 6, 1998
• Discussion: January 9, 1999

3.2 Business Case

• What: Modular narrative (allowing mix/match of sections) providing a generic business case for Web accessibility.  Modules to include disability demographics, universal design benefits, regulatory requirements where applicable, an overview of implementation procedures and resource materials.
• Owner: Brewer, plus reviewers already volunteered.
• Priority/Status: High. Started. Some brainstorm/detail already, some info being collected
• Localization: Can be adapted locally for national, cultural or company specificity.
• Stability: Will need some updating.
• URL: not yet
• Discussion: -

3.3 Demographic Information

• What: A compilation of statistics related to disability and the Web, including statistics related to potential impact of carry-over benefits from universal design.
• Owner: Carey, Brewer
• Priority/Status: Regular. In progress. EOWG discussion occured, some drafts in progress, needs further development/compilation
• Localization: Critical -- need international data but also need country-specific data
• Stability: Will need periodic updating as additional materials
• URL: not yet
• Notes:  Need to not only look at what kind of demographic information is available, but also what our wish-lists of statistical & demographic data.
• Discussion: July 30, 1998

3.4 Scenarios

• What: A listing of very brief descriptions of how individuals would use the accessibility features in WAI guidelines. These "scenarios" would be usage examples with different access technologies, personal impact stories, carry-over Universal Design benefit examples, etc.
• Owner: Koivunen & Brewer
• Priority/Status: Regular. Koivunen has circulated revised drafts. Brewer will revise & add into Central Reference NOTE for Guidelines.
• Localization: if sufficiently general and/or diverse, maybe localization not needed?
• Stability: Stable?
• URL: incorporated into core reference note at <http://www.w3.org/WAI/EO/Drafts/profiles-19990930.html>
• Discussion: August 13, 1998

3.5 Related Web Accessibility Activities

• What: A reference listing of projects focusing on Web accessibility.  Should be comprehensive internationally.
• Owner: Sethuraman
• Priority/Status: Regular. Some info exists on reference page but is very out-of-date, needs to be reviewed
• Localization: Critical
• Stability: Should be updated periodically as projects come and go.
• URL: <http://www.w3.org/WAI/References> (outdated, but what we have for now)
• Discussion: ___________?

3.6 Consultant List

• What: List of experienced consultants in Web accessibility
• Owner: ?
• Priority/Status: Later. Not started
• Localization: Yes
• Stability: Frequent updating
• URL: not yet
• Discussion: October 1, 1998

4. Technical Reference Materials

4.1 Narrative Description of HTML4 Accessibility Improvements

• What: A description of the features in HTML4 that support accessibility, and their significance for accessibility.
• Owner: Jacobs
• Priority/Status: High. Originally DONE -- but needs to be revised as a technical reference Note.
• Localization: Some needed. MN working on a Japanese translation.
• Stability: Stable.
• URI: http://www.w3.org/WAI/References/html4-access

4.2 Narrative Description of CSS2 Accessibility Improvements

• What: A description of the features of CSS2 that support accessibility, and their significance for accessibility.
• Owner: Jacobs
• Priority/Status: High. DONE , but being revised as a technical reference Note.
• Localization: Some needed. MN working on a Japanese translation.
• Stability: Stable.
• URI:
  • original: http://www.w3.org/WAI/References/css2-access
  • revision: http://www.w3.org/WAI/EO/CSS-access-19990330

4.3 Narrative Description of SMIL Accessibility Improvements

• What: "Accessibility Features of SMIL": A description of the features of SMIL 1.0 that support accessibility, and their significance for accessibility.
• Owner: Koivunen & Jacobs
• Priority/Status: DONE. Published September 20, 1999. Updated to correct bug September 21, 1999.
• Localization: Can be translated.
• Stability: Should be stable until SMIL 2.0 comes out.
• URL: <http://www.w3.org/TR/SMIL-access>
• Note: Approved by EOWG, PFWG, SYMM WG.
• Discussion: October 29, 1998 & other.

4.4 Narrative Description of MathML Accessibility Improvements

• What: A description of the features of MathML that support accessibility, and their significance for accessibility.
• Owner: Jacobs?
• Priority/Status: High. Not started
• Localization: Needed?
• Stability: Stable.
• URL: not yet
• Note: Coordinate with UAGL and AUGL

4.5 Example Tables

• What: Sample accessible tables with tutorial notes
• Owner: Bingham?
• Priority/Status: Regular. Not started
• Localization: Needed?
• Stability: would need to be updated when there are significant changes in browser and authoring tool implementations of  table features(?)
• URL: not yet
• Note: Question: Is this sufficiently covered in techniques document already?

4.6 Example Interactive Forms

• What: Sample accessible forms with tutorial notes
• Owner: ?
• Priority/Status: Regular. Not started yet
• Localization: Needed?
• Stability: would need to be updated when there are significant changes in browser and authoring tool implementations of  table features.
• URL: not yet
• Note: Raggett willing to advise. Question: is this sufficiently covered in Techniques document?

4.7 Sample Accessible Style Sheets

• What: (1) Create sample accessible style sheets; (2) conduct an accessibility review of W3C core style sheets; (3) make recommendations for accessibility features to test for in W3C Test Suites
• Owner: Freed & Bosher
• Regular/Status: Freed & Bosher have reviewed & commented on W3C Core style sheets with regard to accessibility; Jacobs has incorporated this input into DOM style sheet?  Accessible style sheets & test suite recommendations not yet started.
• Localization: Needed.
• Stability: Would need frequent updating as style sheet implementations in browsers in authoring tools improve.
• URL: Some URL's related to this deliverable: W3C Core style sheets -- http://www.w3.org/StyleSheets/Core/; W3C CSS2 Validator -- http://jigsaw.w3.org/css-validator/; W3C CSS2 Test Suites http://www.w3.org/Style/CSS/Test/

5. Instructional Materials: Curricula & On-Line Materials

NOTE: The deliverables in this "instructional" section should all be modular & interchangeble, and use the same accessible, Web-based format so that presenters can easily mix & match among the various topics listed. Initial discussion for this area:  July 30, 1998. Also see more discussion, about use of WAI curriculum by others, at December 11, 1998.

5.1 Existing Curricula (this is a compilation only)

• What: A collection of existing curricula: slide sets & instructional materials from people who present on Web accessibility, so that we won't re-create materials that already exist; these can become reference materials for people developing the EO presentation curricula.
• Owner: Loughborough
• Status: Later (may not be so essential as references for EO curric after all, since we're using specific format/content for WAI curricula). In progress -- some collected. Are they gathered anywhere so that EOWG members can look at them? Suggest we drop this for now.
• Localization: Need to gather from EU too.
• Stability: Collection needs to be updated periodically
• URL: Store them somewhere in non-public space for now
• Discussion: ______

5.2 WAI Overview Curriculum

• What: A description of W3C Web Accessibility Initiative: project need, rationale, activities, progress, support & participation, etc.
• Owner: Brewer
• Priority/Status: High. Almost done. (Reviewed by EOWG, awaiting revisions).
• Localization: Will need translations.
• Stability: Will need to be updated frequently, preferably monthly or bi-monthly, to keep up with work.
• URL: http://www.w3.org/Talks/WAI-Intro
• Note: May need a short, medium, and long version, so can be plugged into other presentations. Or...[April, 1999] just do a medium-length one, and add links where people can go into more depth.

5.3 Web Content Accessibility Guidelines On-Line Curriculum

• What: Detailed instructional curriculum for Web Content Accessibility Guidelines
• Owner: Letourneau & Freed
• Priority/Status: Basically finalized
• Localization: Will need translations
• Stability: Stable until guidelines change.
• URL: http://www.starlingweb.com/wai/wcag/
• Note: Complete dependency on Web Content Accessibility Guidelines.
• Discussion: September 3, 1998; Discussion: September 17, 1998; Discussion: October 8, 1998; Discussion: October 22, 1998; Discussion: November 6, 1998; Discussion: November 13, 1998

5.4 User Agent Guidelines/ User Interface Issues

• What: A walk-through of WAI user agent guidelines, with an emphasis on accessible user interface design for Web-based applications.
• Owner: Gunderson
• Priority/Status: Later. Not started
• Localization: Not needed?
• Stability: Should be fairly stable once user agent guidelines go to Proposed Recommendation status; will need to be updated whenever the guidelines themselves are.
• URL: Started?
• Note: Dependency on WAI user agent guidelines

5.5 Authoring Tool Guidelines/ Prompting, Alerts, Help Text

• What: A walk-through of WAI authoring tool guidelines, with a focus on automating accessibility as much as possible through the use of prompting, alerts, and help files.
• Owner: Treviranus
• Priority/Status: Later. Not started
• Localization: not needed?
• Stability: should be fairly stable once authoring tool guidelines go to Proposed Recommendation status; will need to be updated whenever the guidelines themselves are.
• URL: Started?
• Note: Dependency on WAI authoring tool guidelines

5.6 CSS1&2/Creative & Accessible Design

• What: A more advanced "how to write accessible Web pages," with an emphasis on use of CSS1 & 2 as ways to improve design without "breaking" accessibility.
• Owner: ?
• Later/Status: Later. Not started
• Localization: Needs translations?
• Stability: will need to be updated frequently as implementations of CSS1 & 2 in browsers and authoring tools improves.
• URL: not yet
• Note: Important, but tough to do at this time, given the implementation issues with style sheets

5.7 XML & JAVA

• What: A more advanced "how to develop accessible Web sites" using XML & JAVA accessibly.
• Owner: Paciello
• Priority/Status: Later. Not started
• Localization: not needed
• Stability: ?
• URL: not yet
• Note: -

5.8 Business/Policy Case

• What: A comprehensive "why Web accessibility is good for your organization" which will include modules on demographics, universal design carry-over benefits, policy/regulatory considerations, etc.  Audience is primarily managerial/decision-makers; modules should be mix & match so that regulatory or business-related reasons can be emphasized depending on the audience.
• Owner: X
• Priorirty/Status: Regular. Not started.
• Localization: not needed
• Stability: will need updating, possibly quarterly, as policies change
• URL: not yet
• Notes: This isn't the business case itself, but rather promotional summary of business case on slides

5.9 User Information & Involvement/ Related Projects

• What: This is for a user audience, explaining issue, current activities, opportunities for involvement, related projects & resources.
• Owner: Sethuraman
• Priority/Status: Regular. Not started
• Stability: will need to be updated frequently as new projects or resources are added and as activities change.
• Localization: will need translations
• URL: not yet
• Notes: -
• Discussion: October 22, 1998
• Discussion: October 29, 1998

5.10 Trainer Prep: Accessibility Overview & Resources for Web Design Instructors

• What: This would be a comprehensive trainer overview, to be used in a train-the-trainer setting; and would focus on how to most effectively present the issues & use the other training materials available.
• Owner: ?
• Priority/Status: Regular. (This is important, but not feasible until more of other modules are available.) Not started.
• URL: not yet
• Stability: would need to be updated occasionally, when there are significant changes in materials available.
• Localization: may need some kind of localization, particularly as regards pointers to local resources or activities
• Notes: This curriculum would link to all the other modules

6. Demonstration & Video Materials

6.1 Gallery of Accessible Web Sites

• What: Rotating Gallery of accessible live Web sites (as opposed to specially-commissioned demonstration/tutorial sites, 6.2)
• Owner: Burger?
• Priority/Status: High. Started.
• Localization: Needed.
• Stability: Rotate highlighted sites monthly.
• URL: not yet
• Notes: Close dependency with review teams.
• Discussion: September 17, 1998
• Discussion: December 4, 1998

6.2 Demonstration/Tutorial Accessible Web Sites

• What: Web sites that are accessible and that showcase accessible features, coordinated with curriculum slide sets
• Owner: To be subcontracted.
• Priority/Status: High. Started. Needs to be re-started with different arrangement.
• Localization: maybe needed?
• Stability: updated once a year?
• URL: not yet
• Notes: have had EOWG discussion, given initial input to WinWriters. WinWriters okay with outline, will request feedback during development. As of February 1999 determined that we need to subcontract this.
• Discussion: September 17, 1998
• Discussion: December 4, 1998

6.3 Video of Web Browsing with Assistive Technologies

• What: Video of people using the Web with different disabilities and assistive technologies: screen readers & speech synthesis or refreshable Braille display, caption fields, head-mice, voice recognition, etc.
• Owner: RNIB, under WAI-TIDE. Tyler, Carey, Petrie, Booth.
• Priority/Status: Regular. Almost done.
• Localization: translations perhaps.
• Stability: stable!
• URL: not yet
• Notes: Contract specifies delivering master copy; can be transferred to any medium or carrier.
• Discussion: October 8, 1998
• Discussion: November 13, 1998
• Discussion: December 4, 1998
• Discussion: December 18, 1998

6.4 Alternative Browsers

• What: Downloadable demos of text and voice browsers, so site developers can try out different kinds of tools.
• Owner: Bosher
• Priority/Status: Regular. DONE.
• Localization: No
• Stability: Periodic updates
• URL: http://www.w3.org/WAI/References/Browsing.html
• Discussion: October 22, 1998

7. Training Events

7.1 Trainer Best Practices Exchange

• What: A meeting where people who frequently present or train on Web accessibility can come together & share best practices/ materials as well as give feedback on the different WAI presentation curricula.
• Owner: Brewer?
• Priority/Status: Later. Needs EOWG discussion.
• URL: not yet
• Localization: Would be good to bring an international gathering of people together in one place for two days.  Would require some participant support costs.
• Stability: Probably just a one-time event.
• Notes: Needs EOWG discussion. Dependency with Slide Set Curriculum Development, and with Speakers's Bureau if we do one of those.  Trainer Best Practices Exchange; or dedicated trainings in content development community. Possible format: 2-day training exchange, participation linked to commitment to do four trainings in the coming year & agreement to cooperate with impact assessment.

7.2 Page Author/Content Developer Workshops

• What: Dedicated training events for page authors / content developers / site developers; in-depth technical training on how to design accessibly.
• Owner: ?
• Priority/Status: Regular. On-going
• Localization: Needed.
• Stability: Curriculum needs to be updated frequently.
• URL: not yet
• Notes: Strong dependency with Events Coverage & with slide set curriculum development modules & with stability of page author guidelines

7.3 Training & Certification Programs

• What: Dedicated training events for page authors / content developers / site developers; in-depth technical training on how to design accessibly.
• Owner: ?
• Priority/Status: Regular. On-going
• Localization: Needed.
• Stability: Curriculum needs to be updated frequently.
• URL: not yet
• Notes: Strong dependency with Events Coverage & with slide set curriculum development modules & with stability of page author guidelines
• Discussion: Certification Program: December 18, 1998

7.4 Review Teams for Evaluation of Web Site Accessibility

• What: Trained & coordinated teams of Web site reviewers
• Owner: Burger, DuChateau.
• Priority/Status: High. Started
• Localization: Needed.
• Stability: Expect turnover.
• URL: Not yet.
• Notes: Strong dependency with Gallery of Accessible Sites.
• Discussion:

WAI-TIDE

WAI-TIDE deliverables under WAI workpackages are not updated here, and not inclusive of all WAI-TIDE partners (EBU, BrailleNet), and some deliverables (e.g. RNIB film) are integrated among deliverables above.

TIDE is now known as the Telematics Applications Programme for Disabled and Elderly, and is part of the European Commission's Directorate Generale XIII.

Internet book for VIPs, including large section on Web

• What: Internet book for Visually Impaired Persons
• Priority: Regular
• Owner: Helen Petrie, Kevin Carey
• Due: August 1999
• Status: In progress
• URL: None
• Localisation: None
• Stability: 2-3 years before revision
• Notes: Directed to users, explaining how to use the Internet, and discussing Web Content Accessibility Guidelines and how to access the Web as someone who is visually impaired. To be available in all formats.

WAI Web Site for Page Designers

• What: Web demonstration of how to make pages accessible
• Priority: Regular
• Owner: Helen Petrie, Kevin Carey
• Due: August 1999
• Status: In progress
• URL: None
• Localisation: EOWG/TRACE peer review
• Stability: intrinsically, chronically unstable
• Notes: Web-based demos of access barriers and good access models. This will be launched at the same time as the "Internet book for VIP's"

WAI Web Site for VIPs

• What: A specially designed accessible Web site for VIPs on WAI, principles of accessibility, examples of good and bad practice
• Priority: Regular
• Owner: Helen Petrie, Kevin Carey
• Due: August 1999
• Status: In progress
• URL: None
• Localisation: EOWG/TRACE peer review
• Stability: Updated regularly
• Notes: This is basically a portal for visually impaired users, as a companion to the book and the design site listed above.

Video "Web Sites that Work"

Miscellaneous:

Tutorial including mention of accessibility

• What: On-line instruction on good site design, with reference to accessibility
• Priority: Later.
• Owner: Raggett
• Status: Needs re-draft to include accessibility
• URL: http://www.w3.org/MarkUp/Guide/
• URL: http://www.w3.org/MarkUp/Guide/style.html
• Localization:
• Stability:
• Note: This is in a "coordinated items" section since it's not really WAI EO, but the author did want feedback.
• Discussion: September 3, 1998

Distance Learning

• Discussion: October 29, 1998

Request for Cross-Disability review of guidelines

• Discussion: December 4, 1998
• Discussion: December 11, 1998

Do we need short & friendly guidelines?

• Discussion: December 11, 1998

Copyright  ©  1999 W3C (MIT, INRIA, Keio ), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.