Regrets

SL: Steve Lucas - MatchLogic

Summary of action items
from this call

+ JB: before next call will review past minutes & contact people individually
for pending action items
+ SO, SS, DB, PB will work together on re-constructing Stella's first
draft of reference card in very concise format; PB only available till
Tuesday next week; aim is to revise it, re-post it to the EOWG list for
comment by end of next week
+ EOWG members please review revised reference card & comment _before_
next meeting
+ JB will then send revised reference card to PAWG & request review
from PAWG
+ BK, DD will work together on assembling a page of publishing resources
& links to editorial calendars
+ JB should add press market compilation to the deliverables list
+ BK will help with contacts to editors for marketing articles
+ DD, MP, SO, GF can help with writing articles
+ HB: will send more pointers to Kitch & Jim, cc to EOWG,
for events calendar, including DCI
+ JB: URL for /~kitch/eo and /~kitch shouldn't go to the same document?
will discuss with Kitch moving calendar to W3C space
+ JB: will tell Kitch & Jim that submission deadlines are key and
ask if they can fill them in for each conference, also to make them more
specific to the different parts of the conference procedings, since there
is usually more than one submission deadline per conference; also ask them
to set up a way to search for submission deadlines that have not closed
yet;
+ JB: will also re-discuss with Kitch & Jim developing some kind
of fill-in form for who's covering what conference already and plan a regular
way to keep it updated;
+ JB: will draft some kind of system for planning events coverage,
bring it back to the group for discussion

1. Action Item Updates

2. Reference card discussion

JB: Stella, thanks for various drafts.
SO: Shorter version fits on half of A4 page, longer one on both sides;
they essentially have the same content.
SS: Need headings for items
SO: First line of each item would be the heading
DB: Envisioned very brief statements of principle, with brief code
example, with pointers for more information
SS: Who's the audience
JB: Very broad, naive
SS: In that case Stella's first version is most useful
PB: See this as a useful tool for managers to get a sense of what accessibility
requirements are. Regarding content, need change on the links issue
WL: need to specify separation of presentation from content
HB: issue is covered with existing points
PB: access to audio-visual materials
SS: not rank ordered
PB: rank ordering would be helpful
JB: how to coordinate with Page Author Guidelines Working Group (PAWG).
Can clean this up, and then submit to PAWG for review
MR: good, this is more general
GF: can point back to PAWG

+ SO, SS, DB, PB will work together on re-constructing Stella's first
draft in very concise format; PB only available till Tuesday next week;
aim is to revise it, re-post it to the EOWG list for comment by end of
next week
+ EOWG members please review revised reference card & comment _before_
next meeting
+ JB will then send revised reference card to PAWG & request review
from PAWG

3. Technical articles development

PB: Daniel's proposal good start
DD: asked for several sub-deliverables -- how do we compile magazine
marketing materials?
BK: has lists of internet press. Also there are Web sites with
databases of submission guidelines, can help compile.
MP: the articles need to be much more technical in nature than what
Daniel has proposed-- that's what I'm hearing from readers & reviewers.
We need to write about how to program things, what to do.
DD: that sounds more like a tutorial
MP: the articles I do are about 5 pages length
BK: from standpoint of NAW's membership, tutorials work well.
There's a lot of awareness materials out there, but we need the technical.
MP: technical articles coming out on XML, SMIL
SO: I've been writing on JAVA,
BK: Also can compile editorial calendars and help with contact to editors
for articles
SO: Daniel are you thinking about journals, or conference procedings?
single author or collaborative?
DD: both journal & conference procedings, but collaboratively done.
No, not conference procedings
MP: can help with writing
GF: can help with writing
BK: NAW's New England chapter is starting an outreach initiative on
accessibility: upcoming SMIL/accessibility breakfast; awareness & technical
articles planned
JB: Coordinating with Masters of the Web to get accessibility guidelines
into judging criteria.
BK: Maybe a joint press release?

+ BK, DD will work together on assembling a page of publishing resources
& links to editorial calendars
+ JB should add press market compilation to the deliverables list
+ BK will help with contacts to editors for marketing articles
+ DD, MP, SO, GF can help with writing articles

4. Events coverage

BK: NAW/WOW would be happy to have WAI brochures or reference cards at
their booths at conferences, also if there's a press-kit, can help get
the word out in the press room
[Several]: Great
HB: SGML etc not listed on events calendar
BK: DCI not listed
PB: format is good, can easily spot something in Glasgow & get
someone there
MR: submissions deadlines need to be specific to each of the different
parts of the conference procedings
BK: will be attending WebDesign & Development, conferences in NY,
in Orlando, etc., our Executive Director
MK: wil be attending SIG CHI Conference, May 15, need to submit something,
deadline is coming up
JB: we need a way to also capture both the "I will be presenting on
Web accessibility" and "I'll be there and can raise the issue" categories
of coverage
SS: need to get more specific about what our presence means at a conference,
just being there isn't clear enough
JB: we're still not addressing issue of how to prioritize which conferences
to have WAI coverage at
JB: could categorize as three levels of presence to plan for: 1) plenary
presentation for awareness message with focused workshop or panel on how-to
methods; 2) an slot on someone else's panel for awareness; 3) booth-sharing
or BOF (birds of a feather) session for awareness.
MK: need materials to use when at conferences
JB: the EO deliverables list
SO: agree with presence level categories
WL: could also compile lists of grassroots/user organizations local
chapters to help get memberships to get active on Web accessibility issue
JB: sounds like a separate deliverable
BK: would be useful, could contact them when attending an event in
a given location

+ HB: will send more pointers to Kitch & Jim, cc to EOWG, for events
calendar, including DCI
+ JB: URL for /~kitch/eo and /~kitch shouldn't go to the same document?
will discuss with Kitch moving calendar to W3C space
+ JB: will tell Kitch & Jim that submission deadlines are key and
ask if they can fill them in for each conference, also to make them more
specific to the different parts of the conference procedings, since there
is usually more than one submission deadline per conference; also ask them
to set up a way to search for submission deadlines that have not closed
yet;
+ JB: will also re-discuss with Kitch & Jim developing some kind
of fill-in form for who's covering what conference already and plan a regular
way to keep it updated;
+ JB: will draft some kind of system for planning events coverage,
bring it back to the group for discussion

5. Coverage for WWW8 specifically

JB: coverage ideas from WAI meeting at WWW7 regarding planning ahead for
WWW8 coverage
- get accessibility listed as a program category
- make sure the Web site is accessible
- make sure the conference site & arrangements are accessible
- mention accessibility in conference literature
- have a plenary/keynote focusing on accessibility; or raise it in
several keynotes
- conduct a panel with different perspectives on accessibility (went
well at WWW7, would need different)
- have a focused workshop or tutorial, advertise in advance
- have a demo room - maybe ATRC (Jutta's shop) can help
- piggy-back a WAI meeting on WWW8
DD: some additional notes from WAI meeting in Brisbane, will send pointer;
minutes include mention from IBM of technical problems in supporting hands-on
labs
MP: had asked for IW3C2 to include someone representing disability
issues on steering committee
JB: could also try to get someone on program committee

6. Scenarios review

JB: thanks, Marja, for re-drafts
HB: like very much, covers a lot of items
PB: the first example is absurd for the UK, move it down
MP: no people really do that, work when they're driving
[debate]
JB: let's just move it down
GF: difficult to follow because some extraneous detail
JB: please send Marja examples of too much detail
JB: need to also show stuff that doesn't work
SS: yes
PB: changed since last version?
JB: please comment on drafts to the list as much as possible, we have
much material to review, will help us move forward

+ GF will send Marja more comments on where too much detail
+ MK will re-draft
+ EOWG please comment to list

7. Next meeting

JB: Please keep checking list for phone bridge number, may keep changing,
but for next call we're back to usual (as of now)
JB: Conflicts for September dates, move up by one week okay?
[Agreed]: next meetings Thursday August 27, Thursday September 3rd,
Thursday September 17.