So WCAG2 - version 2 of the Web Content Accessibility Guidelines as set out by the W3C’s Web Accessibility Initiative - has been released as a Candidate Recommendation. What does that mean for Australia? There are many issues that were addressed in WCAG1 which have been left up to policy makers and developers in WCAG2. This session will highlight these issues and talk about what kind of impact they will have on your development and on your audience. From testability, to cognitive disabilities, we’ll go into the nitty gritty differences between WCAG1 and WCAG2 and what you will need to know to make sure that your site isn’t a potential target for litigation. In addition to development principles, we’ll address the current state of play in Australia; what the Australian Human Rights Commission (AHRC) are doing and what each state has decided to do with WCAG2.
Citation preview
1. WCAG2 Gian Wild - Monash University @gian
www.gianwild.com.au
2. What do you need to do now? 3. Principles Guidelines Success
Criterion Techniques WCAG2 Techniques UnderstandingWCAG2 4.
Conformance levels 5. 5 conformance requirements 6. Accessibility
supported 7. Top Ten Changes from WCAG1 to WCAG2 8. 10. CAPTCHA 9.
9. Captions and audio descriptions 10. 8. Audio control 11. 7.
Exceptions 12. 6. Colour contrast 13. 5. Sensory characteristics
14. 4. On Focus / On Input 15. 3. Timing 16. 2. Pause / Stop / Hide
17. 1. Keyboard operability 18. Top TenThings you might not notice
in WCAG2 19. 10. Group of images and ALT 20. 9. Combine link and
image when one and the same 21. 8. LONGDESC must be referred to in
ALT 22. 7. Preferred to use an image of a glyph than an ASCII
character 23. 6. Can stop the blink on refresh 24. 5. Changing
presentation of text must be described in text 25. 4. Changing
decorative images must be keyboard controllable 26. 3. ONKEYPRESS
should be avoided 27. 2. All data tables must have captions and
summaries 28. 1. TITLE can be used instead of LABEL FOR 29.
Questions? Gian Wild www.gianwild.com.au
