1. THE BUSINESS CASE FOR INTERNET ACCESSIBILITY AND WHY IT MATTERS TO YOU Thomas Logan, Chief Technology Officer – HiSoftware

2. Overview WCAG 2.0 WhatWhyHow Overview

3. HTML XML WCAG What is WCAG 2.0?

4. Evolution What is WCAG 2.0? WCAG 1.0 Section 508 BITV (Germany) JIS x8341- 3 (Japan) Ministerial Decree (Italy) PAS 78 (UK) WCAG 2.0

5. Need for IT Accessibility Increasing Disabled Population Worldwide Internet Access as a Basic Right Greater Awareness of Rights of People with Disabilities Success of Section 508 and Similar Laws Why WCAG 2.0?

6. WCAG 2.0 Why WCAG 2.0?

7. WCAG 2.0 Why WCAG 2.0?

8. WCAG 2.0 Why WCAG 2.0?

9. PrinciplesGuidelinesSuccess CriteriaTechniques Challenge 1: Different Terminology & Taxonomy GuidelinesCheckpointsTechniques

10. Why WCAG 2.0? Challenge 2: Overlapping Techniques Guideline 1 Success Criteria 1 Technique 1 Technique 2 Success Criteria 2 Technique 3 Technique 4

11. HISOFTWARE COMPLIANCE SHERIFF Automating WCAG 2.0 Compliance How to Meet WCAG 2.0?

12. A Complex Problem… Solved with Automation Repeatable Practical Measurable Automated checks for International standards Easily customized by your staff to meet your specific regulatory governance requirements Repeatable testing incorporated into the content life-cycle Reduces time & money spent on manual testing / custom solutions Standardizing testing takes the guesswork out of content compliance Scalable - include only the compliance options you need Provides visibility to compliance issues across the enterprise (Executive to developer) Tracks site compliance over time Automated monitoring/auditing to keep content compliant Deliver highest standards compliance...automatically How to Meet WCAG 2.0?

13. Built In Checkpoints Customizable

14. Testing Compliance Level

15. Testing Specific Guideline

16. Testing WCAG2 Best Practices Start with most common issues that exist on site – Page Templates – Style Sheets Meet Compliance Level A first Focus on key scenarios/pages Group related manual test work Document work to demonstrate process

17. Identifying Common Issues Count number of occurrences for all guidelines

18. Identifying Common Issues Count number of occurrences for specific guideline

19. Identifying Common Issues

20. Compliance for Key Scenarios

21. Manual Testing Warnings and Visual checks require manual inspection Use Result Revision Wizard to mark content Audit trail for who and when issue was verified

22. Reporting / Documentation Manual and Automated verification roll up for one central report

23. CSS Scanning

24. CSS Scanning – Error Highlighting Errors Highlighted on Page

25. Scanning – Error Highlighting Errors Highlighted on Page

26. User Variables Customize multiple checkpoints at once 2.4.3 Focus Order 2.4.7 Focus Visible 3.2.1 On Focus

27. User Variables / Customize Rules

28. User Variables

29. WCAG 2.0 Wrap-Up Automation is a necessity to organize the work for verifying WCAG2 Compliance Manual verification is unavoidable Prioritizing key scenarios and documenting progress are crucial WCAG 2 features are constantly evolving as new customer scenarios evolve

30. Raising the Bar on Proactive Content Compliance Periodic Monitoring and Reporting Checking Content onDemand Checking Content Before Posting as Part of the SharePoint Workflow Making SharePoint Infrastructure Compliant How to Meet WCAG 2.0?

31. ALT Text Missing People working with disabled colleagues always forget to put alt text on the images in their documents making them non-compliant and usable The Compliance Sheriff workflow lets you educate your enterprise and guide users to include the necessary information to make documents easy to use for all users

32. User Uploads Document

33. Email Notification

34. Accessibilty ALT Text

39. Insufficient Color Contrast People in an office environment often highlight or use their own conventions for marking information. Vision impairments are very common. The Web content accessibility guidelines include clear rules for color contrast settings. The Compliance Sheriff check scan lets the document creator know if the content will be difficult to see for users with vision impairments

40. How to Meet WCAG 2.0? Color Contrast

41. Questions Thomas Logan (t.logan@hisoftware.com) – Chief Technology Officer