W3C logo Web Accessibility Initiative (WAI) logo

WAI UA Telecon for January 4th, 2001

Chair: Jon Gunderson
Date: Thursday, 4 January 2001
Time: 2:00 pm to 4:00 pm Eastern Standard Time, USA
Call-in: Longfellow Bridge (+1) (617) 252-1038


Review Action Items


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


  1. Looking for a UA representative at coordination group meeting on 27 Feburary at all working group meeting in Boston
  2. Update on glossary group formed in WCAG
  3. Update on joint meetings at all working group meeting
  4. Issue #421: Checkpoint 8.6: Clarification about intent required.
  5. Issue #422: Checkpoint 8.8: Clarification of usage of terms active element/focus + techniques
  6. Issue #423: Checkpoint 9.3: Need min requirement for how/where conf information presented.
  7. Issue #424: Checkpoint 9.3: Do author-specified shortcuts include active elements that take mouse input?
  8. Issue #425: Checkoint 9.5: Need to emphasize more why different from 9.4
  9. Issue #426: Checkpoint 9.8: Clarify that brief sequences satisfy this checkpoint
  10. Issue #427: Checkpoint 10.1: HTML is not only accessible format
  11. Issue #428: Checkpoint 10.5: Add requirement that changes that affect accessibility be part of dedicated documentation (10.4)
  12. Issue #429: New requirement: documentation of API for querying preferences.
  13. Issue #430: Checkpoint 3.2: Animations, not just animated images


Chair: Jon Gunderson

Scribe: Ian Jacobs

David Poehlman
Eric Hansen
Gregory Rosmatia
Tim Lacy
Rich Schwerdtfeger
Jim Allan

Charles McCathieNevile
Kitch Barnicle
Harvey Bingham

Action Item Summary

Open Action Items

  1. IJ: Follow up with Greg Lowney on issue 389
  2. IJ: (Issue 387) Propose new wording for check point 8.4 reflecting discussion on 28 November
  3. IJ, EH, AG: Propose new definitions forterms in question (equivalence, text element, etc.)
  4. IJ: Get wording from Martin for thisrequirement (e.g., "conform", "implement", etc.) for issue 327
  5. IJ: Propose new checkpoints/modifiedcheckpoints for 8.2.
  6. IJ: Add some more explanation about the difference between 7.3 and7.4.
  7. IJ: Add to techniques a link to Adobe's accessible PDF information.
  8. IJ and AG: Revise the applicability provision and send to WG.
  9. IJ: Ask Adobe why this is hard (issue 382)
  10. IJ: 1.4 needs to be re-written in light of changes in checkpoint 1.1.
  11. IJ: Proposed text in 2.1
  12. IJ: Add a note to 5.8 - content requirements may also apply to user interface
  13. IJ: Mention that resizing and overiding absolute values is part of some specification in section 1.2
  14. IJ: Clarify the meaning of system colors
  15. IJ:
    a) clarify "recognize style" in checkpoints 4.5
    b) need more rational - refer to WCAG - style less important than other content
    c) add note 4.5 - give example of multimedia content that can be recognized as style
  16. IJ: Add technique to checkpoint 4.12 to make clear that:
    - This includes author-override if speech engine allows.
    - This includes whatever granularity offered by speech engine.
  17. IJ: Add a clarifying note to 4.11 that if you allow independent control of all sources of audio, you satisfy the checkpoint as well.
  18. IJ: Add a P3 checkpoint on user control of windows that automatically close
  19. IJ: Add a clarification to checkpoint 4.20 including:
  20. IJ: Delete second sentence from 4.21
  21. IJ: Add to end of first sentence "with which it overlaps" in checkpoint 4.21
  22. IJ: Add "that benefit accessibility" to end of second sentence of checkpoint 5.8
  23. IJ: Put a note in the definition of active element that this does not include selection. (optional clarification note)
  24. IJ: Include selection and focus in note after 1.1 as examples of what must be done.
  25. JG: Implementation information for guideline 2
  26. JG: Propose a list of things we areexpecting UAs to recognize in scripts.
  27. JG: Schedule face-to-face time with other WGs (need to contact voice and mobile)
  28. JG: Propose text for the techniques document about synthesized speech implementation issues. Notably UA and AT wanting to use the same synthesizer engine.
  29. JG: Create issue list for things that need to be addressed in the next version of the document
  30. GR: Review checkpoints in Guideline 10 for implementation information
  31. GR: Talk to Håkon about CSS support.
  32. GR: Talk to AFB about captioning and positioning
  33. JA: Review checkpoints in Guideline 4 for implementation information
  34. MQ: Send more details about control of speech parameters for the techniques document based on OpenBook.
  35. KB: Submit technique on providing information on current item and number of items in search

New Action Items

  1. IJ: Update 8.8 techniques.
  2. IJ: Put up UAWG meeting page for meeting week of technical plenary. Link to Plenary meeting page.

Completed Action Items

  1. IJ: Ask Jason White for CSS implementation information for emacspeak
    Done: Asked T. V. Raman.
  2. IJ: Publish new implementation report for the meeting
  3. IJ: Improve wording of note for 4.14 related to CSS reference
  4. IJ: Draft new language for 6.2
  5. IJ: Propose new checkpoints to see how it feels to harmonize the requirements related to comments in issue 348.
  6. IJ: Proposed fixed wording for 7.5
  7. IJ: Evaluate whether silent or invisible rendering has an impact on checkpoints other than 7.5 (search).
  8. JG: Propose resolution of issue 421

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.