Requirements and changelog for WCAG 2.0 Presentation
Page Contents
Latest Version: Instructions for the WCAG 2.0 Presentation starting page
Pending edits:
- add "WCAG 2.0 at a Glance"
- to wcag 2.0 intro slide, notes section, add:
Web “content” is the information in a Web page, Web site, or Web application, including:
- natural information such as text, images, and sounds
- code or markup that defines structure, presentation, etc.
Purpose, Goals, Objectives
- Convey key points about WCAG 2.0, especially:
- Benefits of WCAG 2.0 over WCAG 1.0
- Also mention other issues:
- WAI-ARIA
- Authoring tools
- Address common misunderstandings around WCAG 2.0, including:
- WCAG 2.0 is too long (main doc not so long, reference material not intended to be read all through)
- WCAG 2.0 is too difficult to read (current draft is much better than past drafts)
- Address common questions, including:
- When should I start using WCAG 2.0 (start looking at it now, but realize that it will change)
- Primary: Provide presenters with good information on WCAG 2/.0
- Secondary: Provide a self-study guide on WCAG 2.0
Audience
- Direct audience: Presenters
- Anyone presenting on WCAG 2.0, in a wide range of situations,
including:
- General conferences
- Internal groups
- Other accessibility sessions
- Opinion-leaders
- Anyone interested in WCAG 2.0
- Anyone presenting on WCAG 2.0, in a wide range of situations,
including:
- Indirect audience: Audience
- Assume some knowledge of accessibility and WCAG 1.0, little or no knowledge of WCAG 2.0
- Be aware that some might not know anything about accessibility
Approach
- File Format: Provide in 2 formats:
- A presentation format. Prefer to use Open Office ODP since it's open source; however, since PowerPower doesn't open ODP, will need to provide PPT. Ensure that all of the PPT works well in Open Office.
- HTML, with CSS embedded. Provide only as a simple single file, not try to incorporate it into Slidy or other HTML presentation format.
- Slide content approach: Generally follow good practice with little text on slides, and then include detailed "speakers notes", which would also be clearly visible to self-study users. However, consider providing a little more text than might be optimum for experienced presenters, to help novice presenters and those not familiar with the content.
- Datedness: Make the content not outdated until WCAG 2 becomes a Rec -- so that we don't have to change anything. Note that we might choose to change it later; however, don't want to have to in order to avoid incorrect, outdated material. Put clear instructions to check WCAG 2 FAQ for the current status.
- Simplicity: No builds, animations, or fancy stuff. Novices might have trouble with them, and experienced people can do them themselves.
- Timing and customization: Use the cafeteria/salad bar approach where we include all topics (within scope), and then note that presenters should customize it based on the audience and time.
Notes
- Dissemination/outreach: WAI home page highlight & RSS, personal contacts, target key opinion leaders at conferences and bloggers. promote along with recent London presentations.
Open Issues:
- ...
Consider for later version
- Provide more guidance on customizing presentations for different situations
- Update and promote handout(s) to go along with it: www.w3.org/WAI/flyer/Overview
- Optimize a version for self-study
References
Docs:
- WCAG 2 FAQ: www.w3.org/WAI/WCAG20/wcag2faq
- Handouts: www.w3.org/WAI/flyer/Overview
Discussions and old drafts:
- 14 September 2007 EOWG meeting minutes
- 7 September 2007 EOWG meeting minutes
- 31 August draft in presentation format, 31 August draft in word processing format
- 31 August 2007 EOWG meeting minutes
- 28 August draft in presentation format, 28 August draft in word processing format
- 27 August draft of Instructions for the WCAG 2.0 Presentation
- 25 August draft in presentation format, 25 August draft in word processing format
- 24 August 2007 EOWG meeting minutes
- 21 August draft in presentation format, 21 August draft in word processing format
- 16 August draft in presentation format, 16 August draft in word processing format
- 10 August 2007 EOWG meeting minutes
- 9 August draft in presentation format, 9 August draft in word processing format
- 2 August draft in presentation format, 2 August draft in word processing format
- 27 July 2007 EOWG meeting minutes
- 25 July draft in presentation format, 25 July draft in word processing format
- 20 July 2007 EOWG meeting minutes
- 13 July 2007 EOWG meeting minutes: Web accessibility current situation, EOWG short-term focus
Archive
Changes between 8 Sept and 17 Sept versions
- 1 Changed the first sentence to: "The Notes section for each slide contains important information."
- 5 Done: Added "2.0" in the slides and Notes and bolded "WCAG 2.0 itself" in the Notes.
- 8 moved arrow left to right
- 18 removed arrows
- [pending] 22 different image & first paragraph of notes
- [open] 40-43 columns headings in ppt since in HTML?
- 69 chgned image descriptin in Notes
Open Issues:
- What kinds of "branding" do we want to have on the template. W3C WAI logos? None? Pros and cons?
- Are their any constraints on what they can do with it? Is it fully changeable?
- What requirements do we want to have for credit.
- Note what we've done in the past:
"W3C grants permission to use the Overview of the Web Accessibility Initiative slides in presentations according to the copyright and document use policies of W3C.
Reference the slides as follows: Overview of the Web Accessibility Initiative, J. Brewer, et al., ed...." - www.w3.org/WAI/intro/wai-overview-slides#permission
However, taht doesn't allow changes to content. Instead, I wonder if we want to go with CC? - Should we require or request that people who use it gives us some data on the audience; e.g., how many and generally what roles
For 27 July EOWG discussion
- Generally, are the important topics, issues, myths, questions, etc. included? What's missing?
- In what order should the topics be covered?
- Most common, most pressing questions first (a more user-focused
approach) (generally the current organization):
- When will WCAG 2 be done (W3C process) [could move below iii]
- Benefits of WCAG 2 & When should I start using WCAG 2 (flexibility & such)
- How WCAG 2 is different from WCAG 1 (structure of supporting docs, testability & flexibility/adaptability examples, Quick Ref demo)
- Components & guidelines: authoring tools, browsers, content
- General material first:
- Components & guidelines: authoring tools, browsers, content
- How WCAG 2 is different from WCAG 1 (structure of supporting docs, testability & flexibility/adaptability examples, Quick Ref demo)
- Benefits of WCAG 2 & When should I start using WCAG 2 (flexibility & such)
- When will WCAG 2 be done (W3C process)
- Most common, most pressing questions first (a more user-focused
approach) (generally the current organization):
- Any other big things jump out at you with this rough concept draft?
- Any ideas for layout slide 32 -- the one with 7 boxes?
Changelog
About WCAG 2.0
...
Benefits of WCAG 2.0
- 12 June: added 2 slides
- 13 June: added slide 2 "WCAG 2.0 is", tweaked "Integrated Accessibility Guidelines" (currently #7) "Cooperatively developed International standard" (currently #8)