W3C logoWeb Accessibility Initiative (WAI)         logo

WAI: Strategies, guidelines, and resources to make the Web accessible to people with disabilities

User Agent Accessibility Guidelines Working Group
20-21 October 2008
Mandelieu, France

Page Contents

Participation

Participation is open to participants of W3C WAI User Agent Accessibility Guidelines Working Group (UAWG). If you are not currently an UAWG participant and want to attend, contact Jeanne Spellman, Staff Contact.

Registration

Registration is required before 28 September 2008. Under question 5 "Monday 20 October All Group Meetings Attendance" and 6 "Tuesday 21 October All Group Meetings Attendance", select the option button in the column after "User Agent Accessibility Guidelines WG".

If you have any questions about registration, contact Jeanne Spellman, Staff Contact.

Readings and Preparation

Readings will be posted in early October.

Agenda

The times of breaks and lunch are approximate. Lunch may change to 13:00 to 14:00.

Monday, 20 October

8:30 - 10:30 (6:30-8:30 GMT)
Overall document review first pass: comprehensiveness, compatability, organization
10:30 - 11:00 (8:30-9:00 GMT)
Break
11:00 - 12:00 (9:00-10:00 GMT)
Overall document review second pass: feasibility, testability
12:00 - 1:00 (10:00-11:00 GMT)
Lunch
13:00 - 15:00 (11:00-13:00)
Accessible printing in a user agent including: preserving font changes when printing (see printing issues email thread for more details) and the resulting reflow issues (email thread).
15:00 - 15:30 (13:00-13:30 GMT)
Break
15:30 - 18:00 (13:30-16:00 GMT)
Accessible video:
  • review issues and drafting any new success criteria needed. (video issues email thread)
  • video issues raised by HTML5 WG "native rendering of video and communication with AccessAPI" (email thread)
    1. "Rendered Natively" is a cause for concern, as UAAG does not have a definition. This definition would also apply to UAs that have native support for SVG, MathML, etc.
    2. In addition to the DOM, should the UA explicitly communicate the role and state of controls to the appropriate accessibility API or platform accessibility mechanism?
    3. How does the UA reveal the keybindings, if any, to the user?
    4. The author may provide scripted controls in place of the native controls. Should the user be able to override or toggle between the author supplied controls and UA supplied controls?

Tuesday, 21 October

8:30 - 10:30 (6:30-8:30 GMT)
Overall document review third pass: conciseness, clarity
10:30 - 11:00 (8:30-9:00 GMT)
Break
11:00 - 12:00 (9:00-10:00 GMT)
Overall document review overflow issues
12:00 - 1:00 (10:00-11:00 GMT)
Lunch
13:00 - 15:00 (11-13:00 GMT)
Principle 2: Facilitate access by assistive technologies - this section needs a complete rework and fresh technical eyes.
15:00 - 15:30 (13:00-13:30 GMT)
Break
15:30 - 18:00 (13:30-16:00 GMT)
complete Principle 2

Logistics

For meeting location, hotel, transportation, and other logistics, see main World Wide Web Consortium TPAC 2008: W3C Technical Plenary / Advisory Committee Meetings Week page.

Weather notes:

On Site

We are scheduled to meet in room 136.

IRC: Channel: #ua, server: irc.w3.org, port: 6665

Remote

If you are interested in participating via teleconference, please indicate it in the Availability for Upcoming AUWG Teleconferences survey.

A teleconference bridge will be available for both days from 8:30am-5:30pm Central European time.

Bridge: +1.617.761.6200 / +33.4.89.06.34.99 / +44.117.370.6152
Code: UAWG# (3694#)

IRC: Channel: #ua, server: irc.w3.org, port: 6665