KA: Kathleen Anderson
HB: Harvey Bingham
JB: Judy Brewer
DC: David Clark
CH: Carl Heibenstreit
CL: Chuck Letourneau
GL: Gretchen Lowerison
WL: William Longborough
KA: WAI Interest group Microsoft Terry Crowley about Front Page 2000 accessibility problems. Had booth at Assistive Technology conference. Doing Accessessibility training for webmaster next week, Jaws, keyboards, etc. Frontpage will be tool they use. New Horizons will be doing the training, in Windsor, 15 at a time for 10 one-day classes.
JB: WCAG WG initially owning glossary. Task force cross-working group. Need assessment. Possibly useful across W3 as well. DD and JB not wait on any W3-wide Glossary. So WAI should do it itself. HB to represent EO.
GL: Dawson college in Canada is providing accessibility training. Use both MAC and MS. Do not use courseware tools.
CH: An XML.gov website is being set up. Plan to use the XML guideline draft.
HB: Notes are supplemental to changes JB made as we discussed issues. See her revision at
http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/Overview.html
JB: Revisions. Thanks to WL for review. Added new section titles. Added mini-contents for the Scenarios. Linking from within each scenario to separate references, different from the general references.
KA: Scenarios reorder.
WL: Need anchors to improve keyboard support.
HB: Check title word capitalization.
JB: Linking examples. Include links to explain disabilities: example from Online shopper to color blindness, where three barriers noted. When linked to curriculum, get single slide, fast-loading. Later the checkpoint is linked, slower-loading.
DC: Hard to have clear enumerations.
JB: Take out subsection numbers is OK.
WL: Doesn't like option of going to the guidelines.
GL: Likes references to guidelines.
DC: second.
KH: ok.
CL: Likes references to GL/CP.
JB: Exciting to work with scenarios with human case up-front. There is a reason for the requirements. OK for some. Can be disorienting (color via stylesheets). When get to Scenario references, some orientation is useful.
DC: Supplementary references, rather than references from.
KA: If use bookmark won't see that.
JB: Look at 6. References, omit 6.#. The checkpoint text has checkpoint texts, links to curriculum, and then links to the actual checkpoints.
WL: The checkpoint statement language is such a different attitude and writing style from the rest of this document.
JB: The chosen ordering was to use the link experience.
KA: Send to the short fun one first.
CL: Avoid rewriting guideline text.
KA: Full sentence: then short-fun link, then the detail checkpoint link.
DC: Get to the guideline link within the curriculum only?
JB: Only works for WCAG. What to do for AT and UA.
JB: Label for checkpoint, its language, then curriculum example 2.1, Checkpoint 2.1
HB: A table with columns for CP and CU.
KA: Reverse order: CP 2.1, then to curriculum
JB: Guideline name, Guideline number, its text, then curriculum. (will try this)
WL: Checkpoint checker, see its design: rdf.pair.com/xguide.htm
JB: Will try an alternative ordering.
JB: Two additional scenarios were volunteered. They haven't appeared.
JB: It takes about 20 minutes to check linking in the scenarios.
DC: Do not use same icon for different purposes. Take it offline with WL.
JB: No volunteers to add links within case studies So try example of Reporter.
JB: Full keyboard support (ATAG) and access keys (WCAG 7.1 and techniques) and UA) could.
DC: WCAG broken links: "check-use-system-conventions" anchor Same anchor should work in GL and Tech. Going from tech to gl do not have the filename.
GROUP effort: work on internal links among Scenarios into Section 6. JB is editing these on-line.
JB: Link from checkpoint number and when curriculum example, put it at the end.
JB: Prototype example under 6: Access key:
DC: Will work some issues this weekend.
WL: Would like feedback on his page.
JB: Uses AOL-press and jigsaw as tools.
JB: This kind of work session has been useful. Plan to go through rest of document for known updates. Would like full check of the document. KA, WL, DC eventually. Get in condition to send to other groups soon, before end of Nov.
JB: Showed to Steering Council.
WL: Self-reflective instruction (gives example in place) Omitting a navbar on a small page defeats that example for use. Putting resource panel on the left.
CH: Keyboard navigation via tabbing forces the whole link list on the list.
GL: Users are going to be looking for resources, so justify putting on the right.
JB: Again schedule 2 hours, starting at 8:30 a.m. Eastern Standard Time, on this bridge: 617-252-7000.
Minutes by Harvey Bingham