Disability statistics Approximately, there are about 78 million people with disabilities Source: http://codi.buffalo.edu/graph_based/.demographics/.statistics.htm There would be reasonably good number of people with disabilities use the Computers and Internet, because › There is a rapid development in the area of assistive technology › There is AT for every disability
People with disabilities benefit from Offers more independence Internet Need not to worry about inaccessible infrastructure and inaccessible transport Get things done right from home
What’s the issue? 97% of websites are inaccessible! Source: 456BEREAST – Posted in December 2006http://www.456bereastreet.com/archive/200612/97_of_websites_still_inaccessible/UN Global Audit of Web Accessibility conducted a survey on Web Accessibility!
Accessibility is not just for people withdisabilities but also…• Low band width users• Senior citizens• Search engines• Mobile users
Some of the common misconceptions… Accessibility is an additional effort Accessibility is just for visually impaired users Accessibility is an expensive task Need to provide a separate text version of the website
Solution… Consider accessibility right at the initial stage of the project Web Content Accessibility Guidelines (WCAG) 2.0 – http://w3.org/tr/wcag20/ Accessible Rich Internet Applications (ARIA) - http://www.w3.org/WAI/intro/aria.php Authoring Tool Accessibility Guidelines (ATAG) - http://www.w3.org/WAI/intro/atag.php
Web Content Accessibility Guidelines (WCAG) 2.0
Definitions Principle 1: Perceivable › Information and user interface components must be presentable to users in ways they can perceive. Principle 2: Operable › User interface components and navigation must be operable. Principle 3: Understandable › Information and the operation of user interface must be understandable Principle 4: Robust › Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Guideline 1: Perceivable – contd., Sufficient Color Contrast
Guideline 2: Operable Keyboard access – all information and functionality should be available to access via keyboard including: › Links › Headings › Form fields › Lists › Tables
Principle 3: Understandable Use of Natural Language – unless a specific terminology is required Predictable – User should be able to predict the result upon his action Input assistance – provide adequate help for user to interact with forms etc.
Principle 4: Robust Maximize Compatibility with current and future user agents including assistive technologies Provide name, role and value to all the elements
Html 5 and accessibility Best resource: http://html5accessibilit y.com
YUI and Accessibility We have a lot of accessible controls in YUI 3 such as TabView, Menu, Calendar and so on… We have used ARIA to make the widgets accessible See the blog with videos at http://yuiblog.com/blog/category/accessibility
Automated Testing WAVE – http://wave.webaim.org/toolbar Web Developer Kit - https://addons.mozilla.org/en-US/firefox/addon/60 Color Contrast Analyzer - http://visionaustralia.org/info.aspx?page=628
Accessibility Testing – Manual http://twiki.corp.yahoo.com/view/Accessibility/AccessibilityTwiki#qa_corner › Easy Testing with NVDA › Reporting Accessibility Issues in Bugzilla and more… Screen Readers › NVDA – http://www.nvda-project.org › NVDA with necessary settings from Yahoo! Accessibility Team - http://twiki.corp.yahoo.com/view/Accessibility/AccessibilityTrainingClass#install-instructions
Accessibility Testing – Mobile iPhone, iPad and iPod touch › VoiceOver – screen reader that helps users with vision impairment › Zoom – for low vision users › Mono Audio – closed captioning and TTY for people who are hard of hearing › Text prediction – for people who have difficulty in typing Symbian OS: › Provides built in screen reader support › Need to use third party software like Talks or Mobile Speak for other functionality