Regrets - Re: EOWG: Agenda and Readings for 19 October 2007 Teleconference

Shawn Henry wrote:
> 
> Dear EOWG Participants:
> 
> An agenda and calling logistics for our 19 October 2007 teleconference 
> follow.
> 
> Time:    8:30am - 10:30am U.S. Eastern Time. For other time zones see:
>             http://www.timeanddate.com/worldclock/meeting.html
> Bridge:  +1.617.761.6200 / +33.4.89.06.34.99 / +44.117.370.6152, code: 
> EOWG# (3694#)
> IRC:     Channel: #eo, server: irc.w3.org, port: 6665
> 
> Scribe:    *Henny* (per www..w3.org/WAI/EO/2003/scribes )
> 
> BACKGROUND:
> The W3C "Mobile Web Best Practices" (MWBP) 
> <http://www.w3.org/TR/mobile-bp/> provides advice on creating Web 
> content that works well on mobile devices. There is some overlap between 
> MWBP and WCAG. This discussion is about documenting that overlap.
> 
> READINGS:
> * http://docs.google.com/View?docid=dftkhw2k_21dw7jpf
> - "Mobile Web Best Practices and WCAG document, goals and audience": 
> Review all sections
> * http://docs.google.com/View?docid=dftkhw2k_16w7bkx7
> - "Use Cases for the document Relationship between...": Review all
> * 
> http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/latest 
> 
> - Section 1. Introduction: Review all subsections
> - Section 2. How Barriers Experienced by Web Users with Disabilities 
> Parallel those in the Mobile Context: Review the first paragraphs, and 
> skim the table
> - Section 3. How Mobile Web Best Practices can Benefit Users with 
> Disabilities: Review the first part, and skim the details
> Agenda:
> 
> 1. Relationship between Mobile Web Best Practices 1.0 and Web Content 
> Accessibility Guidelines 1.0
> * Purpose and audience: http://docs.google.com/View?docid=dftkhw2k_21dw7jpf
> * Use cases: http://docs.google.com/View?docid=dftkhw2k_16w7bkx7
> * Draft document: 
> http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/latest 
> 
> 
> Questions:
> 1. Overall reactions to the draft document?
> 2. Comments on the purpose, goals, objectives?
> 3. Comments on the target audiences? Are all these audiences basically 
> equal, or some primary and other secondary?
> 4. Comments on the use cases? Are all these basically equal, or some 
> primary and other secondary?
> 
> (Back to the draft document:)
> 5. Does the overall organization and approach to the document meet the 
> expected usage by the target audience and the use cases? How might it 
> better meet the needs of the primary target audiences and use cases?
> 
> (Some specifics:)
> 6. How should the purpose/goals/objectives be expressed in the first 
> section (1.1)?
> 7. How should the target audiences be expressed in the first section (1.3)?
> 8. What information is needed about the Scope, section 1.4?
> 9. Is the Terminology section 1.7 clear? Should additional information 
> be added, or pointed to in other documents?
> 10. Should more background be provided in the Introduction section, or 
> linked to?
> 
> (The other sections:)
> 11. Is the concept behind section 2 (Parallel Barriers Experienced by 
> Web Users with Disabilities) expressed clearly? Is its usefulness (to 
> help people understand why there is so much overlap) clear?
> 12. Is the thinking behind section 3 (How Mobile Web Best Practices can 
> Benefit Users with Disabilities) expressed clearly?
> 13. In section 3, there are numerous hyperlinks to WCAG Techniques. 
> Would it be better to include or quote the Techniques here to make the 
> document printable? Doing so would make it very long.
> 
> ----
> Note: Shawn will not be at the teleconference as she will be presenting 
> at a conference. Judy will chair the discussion.
> 
> Regards,
> ~ Shawn and Judy
> 
> ===
> 
> NOTE: If you reply to this email, please change the subject line. If you 
> are sending regrets, add "Regrets" to the front of the current subject 
> line. If you are commenting on a document or topic, put the document 
> title or topic in the subject line. Thanks.
> 
> IRC reminders and tips:
> - IRC is supplemental to the call. Some participants do not have IRC. 
> All substantive comments should be said verbally in the call (not just 
> in IRC).
> - To type a side comment that will _not_ get recorded in the minutes, 
> type /me comment - e.g.:
>     /me hopes everyone had pleasant holidays
> will come out:
>     *shawn hopes everyone had pleasant holidays
> 
> Teleconference information:
> - Managing IRC for EOWG meeting minutes: 
> http://www.w3.org/WAI/EO/2003/template.html
> - W3C Zakim Teleconference Bridge: http://www.w3.org/2002/01/UsingZakim
> - Zakim IRC Bot: http://www.w3.org/2001/12/zakim-irc-bot
> - A source for help with IRC (Internet Relay Chat): http://www.irchelp.org/
> 
> * Upcoming EOWG meeting schedule: http://www.w3.org/WAI/EO/#meetings
> 
> ###
> 
> 
> 
> 
> 

-- 
Shadi Abou-Zahra     Web Accessibility Specialist for Europe |
Chair & Staff Contact for the Evaluation and Repair Tools WG |
World Wide Web Consortium (W3C)           http://www.w3.org/ |
Web Accessibility Initiative (WAI),   http://www.w3.org/WAI/ |
WAI-TIES Project,                http://www.w3.org/WAI/TIES/ |
Evaluation and Repair Tools WG,    http://www.w3.org/WAI/ER/ |
2004, Route des Lucioles - 06560,  Sophia-Antipolis - France |
Voice: +33(0)4 92 38 50 64          Fax: +33(0)4 92 38 78 22 |

Received on Thursday, 18 October 2007 11:13:55 UTC