W3C logo Web Accessibility Initiative (WAI) logo

WAI UA Telecon for May 9th, 2002


Chair: Jon Gunderson
Date: Thursday, 9 May 2002
Time: 2:00-3:30 pm Boston Local Time, USA (18:00-19:30 UTC/GMT)
Call-in: Longfellow Bridge (+1) (617) 252-1038


Agenda

Review Action Items

Announcements

none

Discussion

  1. Issue 544: Should we delete requirements re: fee links from UAAG 1.0 since not really part of Web today?
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#544
  2. Issue 543: [Clarification] 11.5: Forward/back one viewport for 2d renderings only?
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#543
  3. Issue 542: [Clarification] 11.5: What does "refresh" mean, notably in light of usage in 3.5
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#542
  4. Issue 541: [Clarification] 11.5 (default binding requirements): Moving UI focus to address box sufficient
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#541
  5. Issue 540: [Editorial] 10.3 (indicate rendering progress): Clarify that not about download progress, but position of viewport
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#540
  6. Issue 539: 11.6 (user profiles): Must the user profile be portable? Does saving configurations suffice?
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#539
  7. Issue 538: [Editorial] Make checkpoint requirements distinct from exceptions, sufficient conditions
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#538
  8. Issue 536: [Editorial] 9.7: Title is too forceful and doesn't communicate key bit of checkpoint
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#536
  9. Issue 535: 9.4 (restore history): Must consider UA cache availability Issue
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#535
  10. 534: [Clarification] 9.3 (Move content focus): Clarify that "each element" refers to elements in set defined in provision 1
    http://www.w3.org/WAI/UA/issues/issues-linear-cr2.html#534

Attendance

Chair: Jon Gunderson

Scribe: Ian Jacobs

Present:
David Poehlman
Eric Hansen
Tim Lacy
Harvey Bingham
Jim Allan

Regrets:


Action Item Summary

Open Action Items

  1. IJ: Send proposal for Guideline 10 modifications based on today's teleconference
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002AprJun/0027.html
  2. IJ: Propose text to the UAWG on conformance profiles for use by other specifcations.
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002AprJun/0027.html
  3. IJ: Review UAAG 1.0 for which checkpoints should be "all formats" v. "formats that are part of the claim".
    http://lists.w3.org/Archives/Public/w3c-wai-ua/2002AprJun/0049.html
  4. JG: Write up user scenarios for why non-text-based highlighting important for users; notably which users.
    Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002AprJun/0027.html
    See for additional questions: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002AprJun/0029.html
  5. JG: Clarify why "Max rating" used in some cases (in low implementation experience section) and "Avg rating" in some cases. Also, delete "+/-" with P (round down from G to P)
    http://lists.w3.org/Archives/Public/w3c-wai-ua/2002AprJun/0049.html
  6. JG: Contact developers for API requirements
  7. ALL: Send to the WG the top 5 things you need through an API.
    Deadline: 4 April 2002

New Action Items

None

Completed Action Items

  1. IJ: Update issues list.
  2. RS: Write up paragraph about the importance of thread-safe access for in-process ATs.
    http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JanMar/0100.html
  3. IJ: Add a note to 12.2 (documentation) to remind people that APIs benefit accessibility.
  4. IJ: Update techniques document with RS text:
    http://lists.w3.org/Archives/Public/w3c-wai-ua/2002AprJun/0055
  5. HB: Find out what SVG WG is doing these days in the way of test suites, and find out how to get UAAG 1.0 requirements incorporated.
    http://lists.w3.org/Archives/Public/w3c-wai-ua/2002AprJun/0049.html

Minutes


Copyright  ©  2002 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.