Your SlideShare is downloading. ×
Gov 2.0 Conference 2011 Denise Wood & Scott Hollier
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Gov 2.0 Conference 2011 Denise Wood & Scott Hollier


Published on

Published in: Design, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. ENSURING THEACCESSIBILITYOF WEB 2.0 INGOV 2.0Dr Scott HollierDr Denise Wood
  • 2. MEDIA ACCESSAUSTRALIA• Not-for-profit organisation addressing access issues in: • TV • Cinema • DVD • Education • Digital and Online Media• Access issues include captioning, audio description, computer- related and Internet-related access issuesSlide
  • 3. UNIVERSITY OFSOUTH AUSTRALIA(UNISA)• UniSA is the largest university in South Australia, with 37,000 students and 2,400 staff across six city and regional campuses.• Commitment to providing equitable access to higher education for all sections of the Australian community.• UniSA hosts Australias National Centre for Student Equity in Higher Education.• Has implemented a Web accessibility policy and employs auditing practices to ensure compliance.Slide
  • 4. WHO ARE WE?• Dr Scott Hollier: • Project Manager & W3C AC Representative • PhD looking at online accessibility • Legally blind, personal interest in accessibility• Dr Denise Wood: • Senior Lecturer and Researcher (media) • Expertise in Web 2.0 and inclusive education • Project leader of research focusing on accessible designSlide
  • 5. INTRODUCTION• Brief history of access: benefits and barriers• How people with disabilities go online• WCAG 2.0 and the NTS• Document accessibility: best practice• Social mediaSlide
  • 6. BRIEF HISTORY OFACCESS• For the mainstream population, Internet was viewed primarily as an information and communication resource• For people with disabilities, Internet was viewed as a gateway to independenceSlide
  • 7. ACCESS ISSUES• Broadband: 72% Internet in home generally, 48% for people with disabilities• Web accessibility still biggest issues• Social media accessibility issues• Captions: limited but growing (YouTube)• Audio description: very little online• Cloud computing: accessibility issues, but improving (Google Docs update)Slide
  • 8. USER EXPERIENCE• People with disabilities generally use assistive technologies to help use a computer• Assistive Technology is the practical implementation of technology to support and help people with disabilities• Old model: specialist AT costs $1000-$2000• New model: OS now contains many of these tools, and free open-source also viableSlide
  • 9. POPULAR OSFEATURESWindows XP/Vista/7:•Great support except for blind users•Solution: free NVDA screen readerMac:•Great accessibility toolsiOS (iPhone, iPad):•Also great accessibility, similar to Mac featuresGoogle Android:•Not there yet, but evolvingCloud:WebAnywhere: wa.cs.washington.eduSlide
  • 10. DEMONSTRATION• Windows 7 Zoom• NVDASlide
  • 11. WCAG 2.0OVERVIEW• Web Content Accessibility Guidelines (WCAG) 1.0 released in 1999 to help make AT work with Web• WCAG 2.0 released in December 2008 to be more technology-neutral• Three compliance levels: ‘A’, ‘AA’, ‘AAA’• Based on four POUR design principles: Perceivable, Operable, Understandable and RobustSlide
  • 12. WCAG 2.0OVERVIEWPerceivable:• Provide text alternatives for non-text content.• Provide captions and alternatives for audio and video content.• Make content adaptable; and make it available to assistive technologies.• Use sufficient contrast to make things easy to see and hear.Slide
  • 13. WCAG 2.0OVERVIEWOperable:• Make all functionality keyboard accessible.• Give users enough time to read and use content.• Do not use content that causes seizures.• Help users navigate and find content.Slide
  • 14. WCAG 2.0OVERVIEWUnderstandable:• Make text readable and understandable.• Make content appear and operate in predictable ways.• Help users avoid and correct mistakes.Robust:• Maximize compatibility with current and future technologies.Slide
  • 15. FEDERALGOVERNMENTACCESSIBILITY POLICY• National Transition Strategy (NTS) • Level ‘A’ by end of 2012 • Level ‘AA’ by end of 2014• Ties in with DDA 1992 requirements, supported by AHRC• Also requirement of UNCRPDSlide
  • 16. STATE/TERRITORYACCESSIBILITYPOLICY STATE/TERRITORY WCAG VERSION MINIMUM RECOMMENDED WA 2.0 A AA SA 2.0 A - NSW 2.0 AA - Victoria 2.0 A AA or AAA Queensland 2.0 AA* (no 1.2 - AD) - Tasmania 2.0 A AA or AAA ACT 2.0 A - NT 1.0 AA -Slide
  • 17. AUDITING WEBSITESFOR ACCESSIBILITY• Automated software that checks for WCAG compliance• Tools can’t check everything, still good to have user testing• Free tools: TAW, WAVE, aChecker, accessibility toolbars and extensions• Commercial tools: Sortsite, CSE html validatorSlide
  • 18. INDUSTRYPROGRAM• Professional Certificate in Web Accessibility Compliance is an industry focused online program.• Aim of the program is for participants to develop expertise in the principles and techniques of web accessibility in compliance with the W3C Web Content Accessibility Guidelines (WCAG 2.0).• Participants develop an understanding of the principles of usability and accessibility, policy and legislative frameworks, and knowledge and applied skill in implementing W3C WCAG 2.0.Slide
  • 19. GOOD DESIGN ANDBAD DESIGN INGOVERNMENTGood:•Seniors (Federal government) Webaxe Podcast and blog on practicalweb design accessibility tips
  • 20. PDF CREATION• AGIMO and VA study found PDFs to be largely inaccessible• Best practice: • Follow Adobe’s PDF accessibility guidelines • If PDF is generated from Word document, use Word 2010’s accessibility checker first then make PDF • Always provide an accessible alternative, eg Word document (saved as 2003 .doc) • Never create a PDF from a scan•Slide
  • 21. SOCIAL MEDIAACCESSIBILITYISSUES• AbilityNet audit found: • Lack of alternative text for images • Keyboard accessibility limitations • CAPTCHA systems that are not accessible • Lack of captions or transcripts for user created video • Use of fixed font size for text • Functions that rely entirely on JavaScriptSlide
  • 22. SOCIAL MEDIASOLUTIONS• Workaround: provide links to accessible alternatives such as : • Accessible YouTube players • Easy Chirp accessible Twitter • Facely HD accessible Facebook iPhone appSlide
  • 23. CURRENTRESEARCH• MAA received ACCAN grant to provide resources on social media (release due in early 2012)• UniSA has received Telstra grant to investigate accessibility of mobile technologies.Slide
  • 24. THE FUTURE• NBN holds great promise for services, needs to be accessible• Cloud accessibility• Global Public Inclusive Infrastructure (GPII)• Mainstream mobile technologiesSlide
  • 25. FURTHERINFORMATIONAdvice is free!•E-mail:••Telephone: (08) 9311 8230 or(08) 8302 4642•Website:•Twitter: @mediaaccessaus•@denise_woodSlide