W3C logo Web Accessibility Initiative (WAI) logo

WAI UA Telecon for January 22nd, 2001

Chair: Jon Gunderson
Date: Monday, 22 January 2001
Time: 2:00-3:30 pm Eastern Standard Time, USA
Call-in: Tobin Bridge (+1) (617) 252-7000


Review Action Items


  1. Next User Agent face-to-face meeting in Boston on 1-2 March 2001


  1. Update on joint meetings at all working group meeting
  2. Issue 389: Conformance: Hard to test conformance in an objective fashion.
    Source: http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#389
    Status: I wrote the reviewer with clarifications and asked for comment. No response yet.
    Proposed resolution by IJ: We have reduced some of the conformance requirements as a result of the reviewer's comments. We have worked very hard on this conformance scheme and rejected a number of others. If the reviewer has specific suggestions, we will consider them.
  3. Issue 443: Checkpoint 1.4: Device indepdent access to pointer (mouse) specific events.
    Source: http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#443
    Status: The document currently requires emulation of mouse-specific controls by virtue of our requirement that the user must be able to do everything through the mouse.
    a) Do we want to require the UA to repair device-specific bindings specified by the author?
    b) Do we have evidence that the ability to simulate mouse events through the keyboard benefits the user?
  4. Issue 448: Checkpoint 5.7: Is CSS read-only or read/write? [This is checkpoint 5.9 in the 13 January 2001 draft.]
    Source: http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#448
    Comment: The reviewer's comment was "Is this section referring to viewing the page or editing the page? Why would a user need to access the CSS when viewing a document?"
    Proposed resolution by IJ: Make this requirement read-only access. - We already require that a conforming user agent allow the user to select and apply user style sheets (checkpoint 4.15 in 13 Jan 2001 draft). - We require that the user be able to operate the user agent through keyboard alone. - Therefore, the user should be able to apply user style sheets through the conforming UA's user interface. ATs do not need to write to user style sheets through an API. Can people suggest a scenario where the AT would need to write to the conforming user agent's user style sheet through an API?
  5. Issue 450: If UA is implemented in Java, what system conventions should it follow?
    Source: http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#450
  6. Issue 451: Checkpoint 2.6: Generalize to decorative content, not just null alt
    Source: http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#451
  7. Issue 452: Checkpoint 2.2: Review minimal requirement (three options?)
    Source: http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#452
  8. Issue 453: Checkpoint 3.5: Generalize to "programmatic objects"
  9. Issue 454: Checkpoints 3.6/3.7: Should these be Priority 1?
  10. Issue 455: Guideline 4: Change to "Ensure user control of presentation"?
  11. Issue 456: Editorial: Need to clarify in section 3.2 that we do not mean system APIs
    Source: http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#456
  12. Issue 457: Checkpoint 5.4: Ambiguity about what exactly required: standard APIs only?
    Source: http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#457
  13. Issue 458: Do link highlighting requirements apply to all zones of an image map? What is required granularity?
    Source: http://server.rehab.uiuc.edu/ua-issues/issues-linear-lc2.html#458


Chair: Jon Gunderson

Scribe: Ian Jacobs

RSVP Present:
David Poehlman
Eric Hansen
Harvey Bingham
Mickey Quenzer
Al Gilman

Charles McCathieNevile

Action Item Summary

Open Action Items

  1. IJ: Add these resolutions for issue 324.
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0098.html
  2. IJ: Add IJ proposed checkpoint for character set API support for issue 324
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0098.html
  3. IJ: Ask Philippe Le Hegaret about read only suport for DOM style module and alert the WG
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0098.html
  4. IJ, EH, AG: Propose new definitions forterms in question (equivalence, text element, etc.)
  5. IJ and EH: to review the definition of "presentation" to possibly drop URI-dependencies.
  6. IJ and EH: Work on definition of "animation" that identifies "animated image" as a special case. Also talks about script effects, style sheets effects, markup languages as being able to create animations. (Blinking not part of animations...?)
  7. JG: Talk to Al Gilman at the next WAI CG meeting about a joint meeting with UA, PF, and Voice WG (or participants) to discuss accessibility issues.
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0083.html
  8. JG: Send screen shots of directional techniqes
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0083.html
  9. JG: Implementation information for guideline 2
  10. JG: Propose text for the techniques document about synthesized speech implementation issues. Notably UA and AT wanting to use the same synthesizer engine.
  11. JG: Create issue list for things that need to be addressed in the next version of the document
  12. GR: Review checkpoints in Guideline 10 for implementation information
  13. GR: Talk to AFB about captioning and positioning (deadline 1/18/2001)
  14. JA: Review checkpoints in Guideline 4 for implementation information
  15. MQ: Send more details about control of speech parameters for the techniques document based on OpenBook. (deadline open)
  16. KB: Submit technique on providing information on current item and number of items in search

New Action Items

  1. IJ: Implement "environment conventions" changes per resolution of Issue #450
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0105.html
  2. AG: Consult Trace Institute and reply to UAWG about what the requirement should be for checkpoint 2.6.
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0105.html
  3. DP: Send information on programmable objects based on security options in IE
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0105.html
  4. JG: Request input on the resolution of issue 454
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0105.html

Completed Action Items

  1. DP: Send information about tools that allow mouse binding reconfiguration
    Completed: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0104.html
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0083.html

Link to Minutes

Copyright  ©  2001 W3C (MIT, INRIA, Keio ), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.