AC: Two years ago I was approached by book editor to write a chapter on Web Training. Did so. Not published yet. Updated to current. Will ask permission to republish. Most content is previously published material.
KA: Got new quick tip cards.
JC: Works with people with learning difficulty needs.
JB: Quick tips in eleven languages. More next week. Others available from Daniel's office.
DD: French, Finnish, Swedish, Norwegian, Danish, Dutch, German, Italian, Spanish, Portugese, [Arabic (translation done), Greek, Japanese, and Hebrew are coming.] French was checked for French Canadian. Contents of these translations are available on the site:
WL: Mediatalk list, from ragged edge magazine. Kelly Ford posted on an anti-access article, Bill Fretza on Internet Week online.
Organizing letter writing to counter it.
JB: This kind of response is not an appropriate W3C news release. Instead we can an make the myth countering fact-sheet that gets sent out as an information packet, on the W3C news list for reporters. A staff technical writer may have time to address this.
WL: Recommends as a W3C project, to do a myth debunking article to counteract.
JB: When the US 508 proposed rule comes out, there will be a feeding frenzy of articles complaining about it.
JC: Worry about mis-presentation of the basis for the issues.
JB: We may want to do background.
HB: XTECH 2000 was attended by about 400, and four W3C folks. We got courtesy stuffing of the Tips card into the 400 conference bags. No accessibility spokesperson attended, so far as I know.
JB: Consider having a WAI facts page to give info to W3C folks.
JB: Develop beginners entry points on web design experience.
JC: Nothing available to help on FTTP.
AC: General design of site is important.
JB: Focus rest of meeting on the newly posted draft by JB for:
[HB: New draft posted at end of meeting with many of following comments resolved and incorporated.]
JB: Top-level summary: we reviewed the seven headings, each with a few following sentences. They include 12 links to WAI supporting materials.
JT: Great: This is first page that gives a list for the newbie. This is what I need to grasp to get going. All the guidelines are too much.
WL: It doesn't deal with authoring tools, in preparation for the day when we want those tools to conform to AAA.
AC: Ensure that authoring tool supports the guidelines. None do it automatically.
WL: Add topic For the future: You, the author, should ask the developer of your authoring tool when that tool will support the generation of accessible pages that conform with the guidelines.
AC: Few tools now automatically produce accessible code in all situations. Check with them.
JF: Definition of authoring tools is unclear. For reference, see:
JB: Start with "What it means to be accessible", an overview of accessibility features of pages.
AC: Quick Tips have some geek content.
WL: Need to write the overview.
JB: Add a header, pointing at an overview.
JB: Get background by reading the Frequently Asked Questions for context. Then the guidelines and supporting resources.
WL: Don't start with guidelines. Do the overview first.
JB: Use what we've got today, it can be improved later.
AC: Assumption: this is an early page on WAI. Need intro, before pointing to WCAG, as that is too much for a start.
JC: Who are we writing to? Different needs, different points are important.
JB: Entities that may seek conformance: Governments, companies.
JB: Need priority anchors on guidelines, for internal pointers to them.
JB: Add example from On-line curriculum.
HB: Needn't use whole curriculum. It has useful subsets.
JF: on-line curriculum, can point to examples.
JB: Such as animation: blow up balloon.
JT: Suggest the pointer via alt text to example.
JB: We may want to set up a more detailed tech support answer service.
JB: Wish for simplified way to get tech questions answered by diversion to appropriate experts.
HB: No mention of XML as supported W3C technical recommendations.
JB: There are no accessibility features references on the XML-family.
JB: Link to overview.
KA: How do people get to this page?
JB: Soon it will be in the pointers flier.
WL: Add pointer from article we write.
KA: Add pointer to mission of WAI.
JB: Adding section: For the future -- Get better tools.
HB: Not addressing extensibility to voice browsers.
JB: UA FAQ coming soon. What should topics include?
WL: What's a user agent?
HB: Can I control my user agent?
Can I override author or default browser presentation properties?
How can I use my familiar assistive technology with visual browsers?
JB: Confirmation of new meeting times, including Thursday dates.
JB: Need agenda for face-to-face.