The document discusses HTML5 and WAI ARIA, including current and future features. Key points include: 1) WAI ARIA allows adding accessibility information to any element using attributes. It can be used with HTML, XHTML, SVG and others. 2) HTML5 will include new semantic elements like <nav> and <article> to provide structural information, though they are not yet supported widely. 3) WAI ARIA roles like landmarks can currently chunk pages into perceivable regions to aid navigation. 4) The <canvas> element poses challenges for accessibility without alternatives provided outside the element. ARIA and HTML5 integration defines their relationship going forward.

1. HTML 5 & WAI ARIA Steve Faulkner TPG [email_address] Accessibility 2.0, September 22, 2009

17. HTML5 Canvas element It’s a black hole <canvas> </canvas> On browsers that support canvas – you can’t access to the fallback content

18. HTML5 Canvas element “ When authors use the canvas element, they must also provide content that, when presented to the user, conveys essentially the same function or purpose as the bitmap canvas. This content may be placed as content of the canvas element. The contents of the canvas element, if any, are the element's fallback content.” Source: http://dev.w3.org/html5/spec/the-canvas-element.html#the-canvas-element BAD advice – don’t do it. Make fallback available outside of the canvas element!

19. HTML5 Canvas element Canvas based graph depicting amount of emails, issues and bugs to be processed over time.

20. HTML5 Canvas element The data is provided in tabular format inside the <canvas> element. BUT nobody using a canvas supporting browser can access it unless they ‘view source’

21. HTML5 Canvas element Maybe we will have better luck viewing it in IE , a browser that does not support canvas...

25. ARIA NOW

26. ARIA NOW

27. ARIA NOW