1. ARIA + HTML5 Steve Faulkner & Hans Hillen

2. DIVING IN TO SOME HTML5 Details/summary Dialog Spin button slider ARIA rules HTML/ARIA validation Tools

3. HTML5 Getting simple

4. HTM5 DEMO – DETAILS/SUMMARY label Some content simple

5. HTM5 DEMO – DETAILS/SUMMARY Supports!

6. HTM5 DEMO – DETAILS/SUMMARY What we get

7. HTM5 DEMO – DETAILS/SUMMARY What we get

8. HTML5 DEMO – DETAILS/SUMMARY Filling Gaps

9. HTM5 DEMO – DETAILS/SUMMARY label Some content

10. HTM5 DEMO – DETAILS/SUMMARYDEMO – DETAILS/SUMMARY

11. HTM5 DEMO – DIALOG Creating a modal dialog that works with keyboard and prevents users from accessing ‘disabled’ content is the holy grail….modal dialog

12. HTM5 DEMO – DIALOGDEMO – DIALOG What we get for free Focus moves to modal dialog when it is displayed Focus stays in modal dialog until it is dismissed Content not in the modal dialog is really disabled ESC key dismisses the dialog = role=dialog

13. HTM5 DEMO – DIALOGDEMO – DIALOG What we need to add Accessible name to dialog Currently when the dialog is dismissed focus moves to the when it needs to move to control that triggered dialog display Can be polyfilled using scripting

14. HTM5 DEMO – DIALOGDEMO – DIALOG The good oil on implementing custom dialogs Juicy Studio - Custom-Built Dialogs The Incredible Accessible Modal Dialog WAI-ARIA design pattern – modal dialog

15. HTM5 DEMO – INPUT TYPE=NUMBERINPUT TYPE=NUMBER What we get Correct role and value information Keyboard operable

16. HTM5 DEMO – INPUT TYPE=RANGEINPUT TYPE=RANGE

17. HTM5 DEMO – INPUT TYPE=RANGEINPUT TYPE=RANGE What we get for free EVERYTHING \o/

18. ARIA There are conformance rules: ARIA in HTML

19. HTML 5 SPECIFICATION

20. ARIA VALIDATION Use of ARIA in HTML<5 is non conforming and probably always will be. It doesn’t make any difference, it still works The easiest method is to use the HTML5 DOCTYPE with ARIA markup and validate using the W3C Nu Markup Checker.HTML5 DOCTYPEW3C Nu Markup

21. http://validator.w3.org/nu/

22. 1 ST RULE OF ARIA USE If you can use a native HTML element or attribute with the semantics and behaviour you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so.

23. 1 ST RULE OF ARIA USE Under what circumstances may this not be possible? If the visual design constraints rule out the use of a particular native element, because the element cannot be styled as required. If the feature is not currently available in HTML.not currently available in HTML If the feature is available in HTML but it is not implemented or it is implemented, but accessibility support is not. accessibility support

24. CUSTOM CONTROL ACCESSIBLE DEVELOPMENT CHECKLIST: Custom Control Design Considerations design considerationdescriptionYes/No focusable Can you get to the control via the keyboard? Refer to Providing Keyboard Focus Providing Keyboard Focus operable Can you use the control with the keyboard? Refer to Keyboard Navigation Keyboard Navigation expected operation Can you use the standard keys for the control type to operate it. Refer to ARIA Widget Design PatternsARIA Widget Design Patterns clear indication of focus Can you easily see it when the control has focus? Refer to Visible Focus (WCAG2) Visible Focus label The control has a text label that is exposed as an accessible name in accessibility APIsaccessible nameaccessibility APIs role The control has an appropriate role exposed in accessibility APIs accessibility APIs states and properties The control has any UI states and properties that it has exposed in accessibility APIsaccessibility APIs color contrast The control label/description/icon is perceivable/usable for low vision users (Use a color contrast checker.)color contrast checker high contrast mode The control is perceivable/usable when High Contrast Mode is enabled (e.g. Windows HC mode)Windows HC mode

25. 2 ND RULE OF ARIA USE Do not change native semantics, unless you really have to. For example: Developer wants to build a heading that's a button. Do not do this: heading button Do this: heading button Or better, do this: heading button Note: it is OK to use native HTML elements, that have similar semantics to ARIA roles used, for fallback. For example using HTML list elements for the skeleton of an ARIA enabled, scripted tree widget.list elementstree widget

26. 3 RD RULE OF ARIA USE All interactive ARIA controls must be usable with the keyboard. If you create a widget that a user can click or tap or drag or drop or slide or scroll a user must also be able navigate to the widget and perform an equivalent action using the keyboard. All interactive widgets must be scripted to respond to standard key strokes or key stroke combinations where applicable. For example if using role=button the element must be able to recieve focus and a user just be able to activate the action associated with the element using both the enter and the space key. Refer to the keyboard and structural navigation and design patterns sections of the WAI-ARIA 1.0 Authoring Practiceskeyboard and structural navigationdesign patternsWAI-ARIA 1.0 Authoring Practices

27. 4 TH RULE OF ARIA USE Do not use role="presentation" or aria-hidden="true" on a focusable element. Using either of these on a focusable element will result in some users focusing on 'nothing'. Do not do this: press me Do not do this: press me

28. FirefoxInternet ExplorerSafariChrome Windows, LinuxWindowsOSX + IOS Android + IOS + Chrome OS Zoom Keyboard CSS Zoom Keyboard CSS Zoom Keyboard Touch Zoom Keyboard Touch ACCESSIBILITY TESTING TOOLS Browsers + Keyboard

29. FirefoxInternet ExplorerSafariChrome Windows OSX + IOS Android + IOS + Chrome OS shift+alt+print screen shift+alt+print screen Universal Access IOS OSX Contrast Extension ACCESSIBILITY TESTING TOOLS Browsers + High Contrast Mode

30. FirefoxInternet ExplorerSafariChrome Windows, LinuxWindowsOSX + IOS Android + IOS + Chrome OS Web Developer DOM inspector Firebug Developer tools (F12) Developer tools (OSX) Developer tools (OSX + Chrome OS) ACCESSIBILITY TESTING TOOLS Developer tools

31. ACCESSIBILITY TESTING TOOLS Firefox – DOM InspectorDOM Inspector

32. ACCESSIBILITY TESTING TOOLS Internet Explorer – Web Accessibility ToolbarWeb Accessibility Toolbar

33. ACCESSIBILITY TESTING TOOLS aViewer

34. ACCESSIBILITY TESTING TOOLS NVDANVDA – A free open source screen reader for Windows NVDA Screen Reader command key quick referencecommand key quick reference

35. TOOLS Aviewer (free desktop application for windows ) Aviewer Dom Inspector (free Firefox extension) Dom Inspector Inspect.exe (free desktop application for windows available as part of the Windows SDK) Inspect.exe Accprobe (free open source cross platform app) Accprobe Accessibility Inspector (free Mac app) Accessibility Inspector Java ferret (free cross platform app) Java ferret Accerciser (free gnome desktop app) Accerciser

36. IF YOU ONLY LEAVE WITH ONE TAKE AWAY

37. THANK YOU www.twitter.com/stevefaulkner www.paciellogroup.com/blog www.html5accessibility.com sfaulkner@paciellogroup.com