Status as of 9 August 2007

1. Status as of 9 August 2007 • Rough concept draft only, much of it is incomplete • There are Notes for some slides, and none yet for others Note: This document contains unapproved draft ideas and should not be referenced or quoted under any circumstances.

2. IMPORTANT Note to Presenters The slides themselves have limited text, in order to avoid participants reading much while you are talking. There are extensive presenter’s notes in the Notes section. Make sure you can read them in preparing for a presentation. On this slide, the notes start with “[NOTES SECTION:…”

3. WCAG 2.0Web Content Accessibility GuidelinesUpdate DRAFT Last Updated 9 August 2007

4. Talk about today • What is WCAG- along with Who, Where, When, Why, and How • What WCAG 2 gives you- Applies to more advanced technologies- Clearer criteria- Flexible, adaptable- Practical implementation examples and info • Making accessibility easier & better- Authoring tools and browsers • What you can do now

5. We won’t cover • The basics of Web accessibility and WCAG 1.0 • The business case • Policies, laws, • … and such Will provide resources for these.

6. WCAG = Web Content Accessibility Guidelines • International standard • Applies to Web pages, sites, applications • For: • Web developers and designers, • Authoring tool and evaluation tool developers, and • Others who need a technical standard. • (not for novices)

7. Who develops WCAG • Organizations and individuals around the world, through W3C WAI

8. How WCAG is developed, Stage 1 WCAG Working Group development Community|Public review and comment WCAG Working Draft

9. Getting better with age • For example, • 2006 draft: @@ • May 2007 draft: @@ • Note new and improved documents: • WCAG 2 FAQ • WCAG 2.0 Quick Reference • Summary of Issues, Revisions, and Rationales for Changes to WCAG 2.0 2006 Last Call Draft

10. Milestones • Working Drafts • Last Call Working Draft

11. Milestones • Public Working Drafts • Last Call Working Draft • Candidate Recommendation • Implementations • Proposed Recommendation • W3C Recommendation =Web Standard

12. How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute

13. When will WCAG 2.0be completed?

14. WCAG 1.0 --> WCAG 2.0

15. WCAG 2.0 WD Principles Guidelines WCAG 1.0 Guidelines

16. WCAG 2.0 WD Principles P-O-U-R Guidelines WCAG 1.0 Guidelines

17. What WCAG 2 gives you • Easier to understand success, that is:more precisely testable(do still need human)

18. WCAG 2.0 WD Principles Guidelines Success CriteriaLevel A, AA, AAA WCAG 1.0 Guidelines CheckpointsPriority 1, 2, 3

19. WCAG 1.0 Checkpoint • 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits…

21. WCAG 1.0 Checkpoint • 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits… • WCAG 2.0 Success Criteria • Text (and images of text) have a contrast ratio of at least 5:1…(from the May 2007 Draft)

22. What WCAG 2 gives you • Applies to more advanced Web technologies- current, future, non-W3C • Adaptable, flexiblefor different situations,and developingtechnologies and techniques

23. WCAG 2.0 • www.w3.org/TR/WCAG20/ • Formal Web standard draft, planned to become a “W3C Recommendation” • “Normative”

24. WCAG 2.0 Techniques • “Informative”supporting document • Examples for HTML, CSS, etc. • Can be updated

25. WCAG 2.0 requirements are more flexible

26. More design flexibility • WCAG 1.0 Checkpoint 7.1:Until user agents allow users to control flickering, avoid causing the screen to flicker • WCAG 2.0 allows more movement within defined parameters

27. Scripting allowed!

28. Scripting Techniques • Providing client-side validation and alert • Using functions of the Document Object Model (DOM) to add content to a page • Using Dynamic Web Content Accessibility to programmatically identify form fields as required • . . .

29. Flexibility for rich Internet applications • WAI-ARIA:Accessible Rich Internet Applications Suite • Techniques for meeting WCAG 2.0 • E.g., accessible and highly usable expanding and collapsing menus/tree controls/nav bars

30. WAI-ARIA status • Implementations already in browser and screen reader • Documents • Technical material for tool and specification developers • Best practices for Web content developers

31. WCAG 2.0 flexibility for different situations Accessibility Supported Technologies(formerly “Baseline”)

32. What WCAG 2 gives you • Extensive supporting materials, - practical implementation guidance

33. WCAG 2.0 WD Principles Guidelines Success CriteriaLevel A, AA, AAA 2.0 Support Techniques + Understanding WCAG 1.0 Guidelines CheckpointsPriority 1, 2, 3 1.0 Support Techniques

34. Techniques WCAG 2.0 Understanding • “Informative”supporting document • Reference manual

35. Techniques WCAG 2.0 Understanding

36. Techniques WCAG 2.0 Quick Reference! Understanding

39. Overview WCAG 2 FAQ Issues, Changes Techniques WCAG 2.0 Quick Reference! Understanding

40. What WCAG 2 gives you • Applies to more advanced Web technologies- current, future, non-W3C • More precisely testable- (still need human) • Adaptable for situations • Extensive supporting materials, -practical implementation guidance

41. @@How make my site accessible? • Understanding accessibility issues • How People with Disabilities Use the Web • Involving Users in Web Accessibility [Design and] Evaluation • Videos

42. @@Role of Guidelines/Standards • Understanding how people with disabilities use your site • Technical standards • Shared definition of requirements • Adaptable, flexible • How-to “techniques” for different levels

43. Who is responsible forWeb accessibility?

44. Making accessibilityeasier & better @@

45. Components of Web Accessibility Web Content(WCAG)

46. Components of Web Accessibility Web Content(WCAG) User Agent(UAAG)

47. Components of Web Accessibility Web Content(WCAG) Authoring Tool(ATAG) User Agent(UAAG)

48. A c t i o n !

49. What else you can do now A c t i o n !

50. Start using WCAG 2.0 now