1. BUILDING AN ACCESSIBLE SILVERLIGHT EXPERIENCE CL51 Mark Rideout Silverlight Program Manager Microsoft markri@microsoft.com blogs.msdn.com/markrideout/

2. Agenda  Why  What  Where  When  How

3. First a statement... You can build accessible experiences and applications with Silverlight.

4. Why  Increase adoption  Increased potential cliental  Legal requirements

5. What  Guidelines and Legal legislation  Section 508c, WCAG 2.0, WAI  Examples of screen readers  JAWS, NVDA, Windows Eyes, Narrator, etc.  Screen Reader rely on  UI Automation  MSAA  DOM access  Screen scrape

6. Where  Keyboard  Application functions can be done without a mouse  Visual  Application is “visible” to a screen reader  Application can be used by users with low visual acuity  Audio  Your media can be “read” and not heard

7. When  Start Early  Designers - Good design doesn’t mean accessible  Developers - Implement with accessibility  Check often  Testers - Check throughout at major milestones  Developers – Use UI Spy and AccExplorer  Verify - Run tools like UIA Verify and AccChecker

8. How - Keyboard Keyboard accessibility Demo

9. How – Keyboard  Review  Looks nice  Not accessible  Use Controls for tab/focus support  Handle keystrokes for custom keyboard actions  Be aware of keystroke limitations for hotkeys

10. How - Visual Silverlight and Screen Reader Demo

11. How – Visual  Review  Use built in controls and retemplate  Some controls need additional metadata  If building “from scratch” create own AutomationPeer  Identify non text (e.g. images)  AutomationProperties.Name

12. How – Visual  High contrast  Look at SystemParameters.HighContrast  Use System Colors theme (Silverlight Toolkit)  Don’t rely on color  Add some other shapes or text styling  Zoom and larger text  Ensure app scales with browser zoom  Provide text-sizing UI control

13. How – Audio  Use pre-built “media players”  Accessible Media Project (AMP)  Expression Encoder  Close captioning

14. Now  Call To Action  Accessibility is important  Design and develop with Accessibility in mind  Use best practices (avoid “bad” practices)  Test accessibility

15. Resources  Section 508: http://www.section508.gov/http://www.section508.gov/  WCAG 2.0: http://www.w3.org/TR/WCAG/http://www.w3.org/TR/WCAG/  (Web Content Accessibility Guidelines)  Other global legislation: http://www.w3.org/WAI/Policy/http://www.w3.org/WAI/Policy/  UIA Verify: http://www.codeplex.com/UIAutomationVerifyhttp://www.codeplex.com/UIAutomationVerify  AccChecker: http://www.codeplex.com/AccCheckhttp://www.codeplex.com/AccCheck  UI Spy: http://msdn.microsoft.com/en-us/library/ms727247.aspxhttp://msdn.microsoft.com/en-us/library/ms727247.aspx  AccExplorer: http://www.microsoft.com/downloads/details.aspx?familyid=3755 582A-A707-460A-BF21-1373316E13F0 http://www.microsoft.com/downloads/details.aspx?familyid=3755 582A-A707-460A-BF21-1373316E13F0  Accessible Media Project: http://www.codeplex.com/amphttp://www.codeplex.com/amp  Blog: http://blogs.msdn.com/markrideout/http://blogs.msdn.com/markrideout/  CoDe Accessibility Article: http://www.code- magazine.com/articleprint.aspx?quickid=0810062&printmode=truehttp://www.code- magazine.com/articleprint.aspx?quickid=0810062&printmode=true