- From: Ian Jacobs <ij@w3.org>
- Date: Mon, 21 May 2001 13:46:40 -0400
- To: Earl Johnson <Earl.Johnson@sun.com>
- CC: eve.maler@sun.com, w3c-wai-ua@w3.org
Earl Johnson wrote: > > Hi Ian, > > > > > Let me know if this is a sufficient answer to your comment. > > > > > > > EJ If the programmatic point came thru clearer... Perhaps reword > > > to something like: "This includes not only the visual and > > > programmatic requirements that directly refer..."? > > > > IJ2: How about instead: > > > > - The API requirements of this document are in Guideline 6. > > - Everything else (needs double checking) is not to be > > satisfied through an API alone. > > > EJ2: You probably only need to add the first point guideline 10 however > remember that not all platforms offer an Accessibility API so focusing > on API as opposed to saying programmatic or something more generic (but > having the same meaning) might be a better approach so UA developers > don't think no API means I don't have to worry about exposing stuff to > AT programmatically. Ah, but the developer *must* implement APIs to conform to UAAG 1.0. The UAWG is refining a proposal [1] for prioritizing which APIs must be implemented. This proposal may address some of your points, but it only ever talks about APIs. What form does programmatic access take if not through an API? - Ian [1] http://lists.w3.org/Archives/Public/w3c-wai-ua/2001AprJun/0169.html -- Ian Jacobs (ij@w3.org) http://www.w3.org/People/Jacobs Tel: +1 831 457-2842 Cell: +1 917 450-8783
Received on Monday, 21 May 2001 13:47:10 UTC