Skip to
content
EOWG
Face-to-Face Meeting
27 February, 28 February, and 2 March 2006
Cannes-Mandelieu, France
Page Contents
Lodging, and other logistics information available from the Technical Plenary and WG Meeting Week page.
Participation
Participation is open to participants of W3C WAI Education and Outreach Working Group (EOWG). If you are not currently an EOWG participant and want to attend, contact Shawn Henry (W3C Staff contact for EOWG).
Registration
Registration is required and is open until 23 February 2006. A W3C login is required to access the registration form.
If you forgot your login, use the Account Password Recovery.
If you have any questions about registration, contact Shawn Henry (W3C Staff contact for EOWG).
If you would like any accessibility accommodations, contact Shawn Henry (W3C Staff contact for EOWG).
Preliminary Agenda
All times are Central European Time Zone (CET).
Monday, 27 February
Meeting room: 223
- 8:00 am: Registration
- 8:45 am: Introductions, Announcements, Agenda review
- 9:00 pm: "Retrofitting" document
- Latest version: Improving the Accessibility of Your Web Site
- Background: the requirements and changelog document includes "About
Retrofitting Web Sites for Accessibility" section and links
to previous drafts, minutes from telecons, e-mails, etc.
- 10:00 am: Break
- 10:30 am: Retrofitting document, continued
- 12:00: Lunch
- 1:30 pm: Glossary
- Review Requirements and status
- See definitions in Notes from December 2005
- Discuss Needs EOWG discussion list (assistive technology, equivalent alternative, graceful transformation, markup language, real-time event)
- 3:00 pm: Break
- 3:30 am: Glossary, continued
- See definitions in Notes from December 2005
- Discuss Needs input list (keyboard equivalent, metadata, natural language, transcript)
- 5:30pm: Meeting adjourn
Tuesday, 28 February
Meeting room: 223
- 8:00 am: Registration
- 9:00 am: Glossary,
continued
- New or remaining issues
- 10:00 am: Break
- 10:30 am: Glossary,
continued
- New or remaining issues
- Plans for coordination with WCAG WG, ATAG WG, and others
(see Ready for Coordination list)
- 12:00: Lunch
- 1:30 pm:Brainstorm on supporting newbies
- What do people who are new to accessibility need? Web developers? Non-developers?
- Consider problem definition, focusing on brief personas; and solution ideas, including possible resources and outreach activies...
- 3:00 pm: Break
- 3:30 am: [this space intentionally left blank for overflow topics from above or additional topics from below]
- 5:30pm: Meeting adjourn
Wednesday, 1 March
Thursday, 2 March
Meeting room: 223
- 8:00 am: (Registration open, if you haven't yet)
- 9:00 am:
- Tools list: last pass on advanced search: quick check of changes from ERT WG requests, and standards/guidelines language (look for updated info on list) (~30 minutes) [For background: Requirements and changelog, and Tools List Overview page ]
- WCAG Glossary comments: quick review of proposed comments on remaining glosses w/ questions (~30 minutes)
- 10:00 am: Break
- 10:30 am:
- Retrofitting: review re-organization of document & additional questions (45-60 minutes)
- Evaluation report to accompany B/A demo: review outline & approach (30-45 minutes)
- 12:00: Lunch
- 1:45 pm:
- Standards Harmonization: review of changes as requested by review, and caution to reduce potential mis-use; changelog; earlier draft (~45 minutes)
- [possible] Business Case slide sets: basic set with basic changelog & requirements; and/or the how-to set with how-to changelog & requirements. (0-30-60 minutes, depending...)
- 3:00 pm: Break
- 3:30 pm: [overflow topics from above only as needed]
- 4:30 pm: Meeting adjourn
Possible Additional Topics
- Tools List Search
- Discuss wording in Advanced Search
- For background:
- BAD
- Review requirements and status
- Discuss approaches to Evaluation Report
- Discuss any other open issues
- Business Case slides
- Discuss draft slides: Business Case Overview, Creating a Customized [links coming]
- For background:
- "Review Teams" doc
- [to be updated Latest draft: Combining Expertise to Evaluate Web Accessibility]
- Background: Requirements and changelog
- Why Standards Harmonization is Essential to Web
Accessibility
- [to be updated: Standards Harmonization Draft]
- For background: Changelog