Chair: Jon Gunderson
Date: Wednesday, March 24th
Time: 12:00 noon to1:00 pm Eastern Standard Time
Call-in: W3C Tobin Bridge (+1) 617-252-7000
HB: (Deadline 25 March): Table proposal for techniques document.
JG: Tell WG when DOM meeting will happen.
CMN: Post response to WG.
MK: Draft techniques related to multimedia.
Editors: Add Cross link in 5.2.4 (and 5.2.6) to 7.3.3.
CMN: This is a general concern and is applicable for other checkpoints.
CO: (with reservations from CO): Review checkpoints and list those where OS conventions should be elicited.
CO: Review 4.3.2 and 4.3.3 for wording and priority.
IJ: Eric Hansen review of WCGL intro. I will compare and take into account.
Group: Review: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0254.html
Subgrouping of checkpoints
Keyboard navigation checkpoints for active elements
Keyboard navigation checkpoints for all elements
Chair and Scribe: Jon Gunderson (JRG)
Harvey Bingham (HB)
Kathy Hewitt (KH)
Rob Relyea (RR)
Marja-Riitta Koivunen (MRK)
Denis Anson (DA)
Scott Luebking (SL)
Mark Novak (MN)
Ian Jacobs
Kitch Barnicle
JG: Tell WG when DOM meeting will happen (http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0348.html)
CMN: Post response to WG on table cell access. (http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0348.html)
MK: Draft techniques related to multimedia. (http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0353.html)
HB: (Deadline 25 March): Table proposal for techniques document.
Editors: Add Cross link in 5.2.4 (and 5.2.6) to 7.3.3.
CO: (with reservations from CO): Review checkpoints and list those where OS conventions should be elicited.
CO: Review 4.3.2 and 4.3.3 for wording and priority.
IJ: Eric Hansen review of WCGL intro. I will compare and take into account.
MN: will post information on information exchange and DOM
JRG: respond to MK on multi-media posting
JRG: Post a message saying that the checklist subgrouping will be integrated into the next working draft based on Jon Gundersons proposal
HB: ACTION post issue on keyboard remapping from the WAI discussions at CSUN
RR: Respond to HB posting of issue related to work and ideas at MS
DA: will write techniques for 5.5.3 and 5.5.4
Editors: Integrate checklist subgrouping into next working draft based on JRGs proposal (http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0254.html), individual comments can be sent to the list for discussion
Checkpoint subgrouping in Section 5.4 to AT only
Checkpoint subgrouping in Section 5.5 and 6.1 as stated by JRG (http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0254.html)
JRG: Reviewed action items
HB: Report on WAI meetings at CSUN
Keyboard binding remapping for applications and assistive technology
Watched people have a lot of transfer of training problems
JRG: For AT or mainstream technology
HB: ACTION post issue on keyboard remapping from the WAI discussions
JG: Kathy did it come up ay Microsoft meetings
ACTION Rob respond to HB posting of issue related to work and ideas at MS
JG: Discussion of
DA: If AT is required to do something make sure that information is available programmatically from DGUA
DGUA: AT compatibility 7.2.1, 7.2.2
/* Discussion of tab ordering and keyboard access */
SL: How does the person know what the number of the link is?
KH: Power toy available to list pages
Not having HTML markup
Rob: Go to the link to get to the next page
DA: Denis suggested a priority 3
RESOLVED: AT checkpoint for tab-ordered access to links
DA: didn't CO check say 90% of waht assistive technology needs in IE
HK: I think that it dependends on the AT and we ahve people lokking at that in many development groups. Decisions are partly based on how they benefit all people.
DA: What we are saying is that DGUA must implement natively
HK: IE will make sure that information needed by AT will be available programmatically
DA: In terms of conformance the DGUA must provide the user agents
JRG: 7.2.1 and 7.2.2
DA: Does AA provide information on attributes ROB: As these exposed interfaces with through AA and object model
JRG: The goal is to define the information to be exchanged ...
DA: The conformance is based on the exchange of information not the mechanism
RESOLVED: AT checkpoints for tables Section 5.4
Leaving the call: KH, RR, SL
/* Group thank you to Kathy Hewitt and welcome of Rob */
SL: ATM will become browser, article in Toronto newspaper
MN: We need to limit the scope of the guidelines to DGUA and AT
DA: Device independence in the checkpoints
JG: We have a separate checkpoint for deveice independence
RESOLVED: Checkpoints in Section 5.5 as stated by JRG
HB: 5.5.3 what is text content mean?
JRG: This issue needs to be clarified.
DA: The text content is what the user endered or in the control on loading
HB: Many designs would use both
DA: You want to move around in information that entered
ACTION: DA will write techniques for 5.5.3 and 5.5.4
Section 6.1
MK: Provide the user with the number of viewports would be easy to implement for DGUA
JRG: Discussed the we need to have definite disability populations that benefit from a feature for DGUA that will not be required to use AT and that we need to have an example of a techniques for proposals. Not clear how this would be useful without some AT.
MN: 6.1.7 ( 10 February WD) If you change viewports how does the user agent keep track of the view information in hte previos view/
HB: 6.1.7 (10 February WD) Technical issue on how long should a user agent maintain its point of reguard: how long does it kep the information, what happens when you navigate to previously viewed page.
RESOLVED: Checkpoints in Section 6.1 as stated by JRG
ACTION: MN will post information on information exchange and DOM
HB: Already has outstanding action
ACTION: JRG respond to MK on multi-media posting
MN: Will you send information to me about tables
JRG: One hour meeting or 90 minute
MN: current meetings are not too long given the amount of work
HB: current meetings are not too long given the amount of work
ACTION: JRG Posting a message saying that the checklist will be integrated into the next working draft