W3C logo Web  Accessibility Initiative (WAI) logo
 

WAI Education & Outreach Meeting, September 17, 1998

Posted by: Judy Brewer, WAI EOWG Chair

Last updated: September 30, 1998

Present:

DD Daniel Dardailler
MK Marja-Riitta Koivunen
BK Ben deLong
HB Harvey Bingham
CL Chuck Letourneau
JB Judy Brewer
PB Peter Bosher
AC Alan Cantor
SS Sheela Sethuraman
JA Jim Allen
WL William Loughboro

AGENDA:

1. curriculum slide set, first sample format for review
2. integrated demo pages, specific proposal
3. events coverage, proposal
*. reference card
4. upcoming meetings

1) Initial review of curriculum slide set format.

See example linked from
http://www.starlingweb.com/wai/eoslides.htm , by Chuck Letourneau. Note
only item B.4 is expanded so far, so the links to "techniques & examples"
on the other items won't go anywhere.
DISCUSSION:
- do these kinds of examples work?
- are they sufficiently self-explanatory that speaker's notes aren't needed?
- could this format perhaps even work jointly for presentation materials
and for a self-instructional module?
(By the way, in terms of format, right now the top page is being written as
an HTML file with multiple H1's, on which we'll run a perl script that
generates multiple slide-like HTML pages.)
NOTES:
CL: three guidelines mocked up; a1, descriptions for graphics, etc.; fit into W3C slidemaker program; tries in a chatty way to give live examples of Web design; links aren't live much yet; question of which ones to point to real world;
HB: don't point to sites that aren't fully accessible
CL:
JB: can we use this format for self-instruction as well
SS: for self-instructional modules, need a feedback loop, needs to be more interactive
WL: also might be useful for Jutta's group
JB: Jutta might be doing so
HB: these formats are diverging too much, needs to be aligned with
CL: opportunities
SS: just a way of lightening it -- works okay
BK: humor needed
CL: rating...
JA: lots of room for tightening up...
MK: language

2) Integrated demo pages:

We have an offer from Joe Welinsky of WinWriters to write integrated demo
pages for us, in other words, mocked-up "sites" that show off a lot of
accessibility features in their design, such as a florist site that has
display info, ordering info, forms to fill out, etc. These would complement
the technique-specific examples which will be part of the curriculum slide
sets.  He will be recruiting people to work on the sites, and wants
guidance from us. Initially our thoughts were to have WinWriters develop
eight "integrated demo sites": Four categories, and in each category a
plain/simple site, and a technically complex site. The four proposed types
of sites are:
- marketing/sales (such as amazon.com)
- customer service (such as microsoft support)
- information
- portals
DISCUSSION:
BK: many sites are becoming dynamic content generation, information & ... all diverging
- multi-media sites (education, distance-learning)
- education
- business
- personal
- entertainment
- government
- news updated (ticker)
JB: how to make the sites most useful
AC: want very succinct information. if he's willing to create a multitude of mock-up sites, have them extremely small; get across the principles in maximum of 3 or 4 pages. don't try to demonstrate everything in each site
SS: the idea of an accessible site that runs all through the Web site; like the idea of a running list of notes, would be happy to help draw
AC: bury the comment in the code
HB: ?put in longdesc
JA: give people a choice, please do both

3) Back to event coverage. Proposal:

- Kitch maintains the events page, including who's-covering-what info, in
WAI EO space; also adds as much info as possible about when submissions are
due. (Kitch can start doing this in early October.)
- We set up a link on the WAI IG home page (which needs lots of work, yes),
to an input form on the events page, for anyone from any WAI group
including WAI IG itself to report, if they like, on events they're
attending or presenting at;
- We remind people in WAI IG & WG's periodically about input form in
updates to WAI IG;
- WAI EO establishes a priority system for covering events, for instance:
  1. Major mainstream computer industry conferences, with emphasis on
Web-based applications development, or content development;
  2. Government info tech conferences, with emphasis on
obligations/requirements for accessible design;
  3. Disability community events, with emphasis on resources available, and
how to get involved in promoting implementation;
- Coverage priorities:
  A: Plenary opportunity (awareness-building)
  B: Workshop or tutorial (in-depth how-to)
  C: Panel (awareness-building)
  D: Booth presence (awareness-building)
  E: BOF's
- Someone (Kitch? WAI staff?) reviews the events site regularly WRT to
these priorities, flags things that aren't covered, recommends level of
coverage, canvasses other WAI WG's as necessary for volunteers to present
or makes other arrangements to cover.
- Eventually -- maybe after a trainers best practices exchange meeting ??in
Jan/Feb 99 (?), and/or after some of curriculum slide sets available we
start a "WAI-speakers" mailing list, over which we can send notices of
upcoming submission deadlines, recommend coverage, etc.
DISCUSSION:
BK: held an event on SMIL. PC Week wrote an event on SMIL. Web
BK: key is to make contact with who's running the event. also associations & supporting companies.
getting press kits into press room. get
contact person
Press list: up to event
HB
anyone working with WWW8
* Jim: okay to track. form. draft it.
- having presence at the big ones. Fall INET world 150 signed up for the press room. from all over the world.
AC: don't forget the little ones. nothing about xsblty.
INET World, Comdex, DCI. work with non-profits.
put all the events in the conference literature. put a whole conference in it.
Web 98 has a whole different conference...
 


Copyright  ©  1998 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.