- From: Ian Jacobs <ij@w3.org>
- Date: Fri, 14 Jan 2000 10:09:09 -0500
- To: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
- CC: w3c-wai-ua@w3.org
Jon Gunderson wrote: > > In checkpoint #178 I suggest that we drop the phrase "and through APIs" for > checkpoint 10.1 and 10.2 for the following reasons: > > 1. We have other checkpoints that deal with providing information in > accessible ways in Guideline 1 and Guideline 5 Checkpoint 1.1 deals with input device APIs, so it doesn't cover the requirement of 10.1 and 10.2 Checkpoint 5.2 addresses programmatic access to UA user interface controls. Can the keyboard configuration be considered a user interface control? > 2. Outside of guideline 1 and 5 we only reference API in one other > checkpoint, checkpoint 9.1. How is that relevant to the required functionality? > It is assumed in the guidelines for checkpoints related to providing > information to the user natively that APIs are used that make the same > information available to ATs. Where is that stated in the Guidelines? The checkpoints seem to cover programmatic access to: - content - ui controls - changes to content and ui - activation of ui features I don't think the assumption is made uniformly. For instance, we have checkpoint 2.1 (user access to content) and checkpoint 5.1 (programmatic access to content). There is no assumption necessary since the requirement is explicit in 5.1. > I don't think we need to repeat ourselves on > this issue in checkpoints 10.1 and 10.2. I wouldn't mind deleting the phrase, but I'm not sure that the requirement is covered by another checkpoint. I don't think checkpoint 1.5 (messages to the user) covers the requirement. - Ian -- Ian Jacobs (jacobs@w3.org) http://www.w3.org/People/Jacobs Tel/Fax: +1 212 684-1814 Cell: +1 917 450-8783
Received on Friday, 14 January 2000 10:10:13 UTC