The document discusses web accessibility, focusing on the importance of making web content usable for individuals with disabilities. It outlines the Web Content Accessibility Guidelines (WCAG) 2.0 and offers principles such as perceivable, operable, understandable, and robust websites, alongside assistive technologies and accessibility testing methods. The World Wide Web Consortium (W3C) and its Web Accessibility Initiative (WAI) are highlighted as key organizations in developing these guidelines and promoting global participation.

1. Web Accessibility25-26 September, 2009-Srinivasu

2. AgendaWhat’s Disability?World Wide Web Consortium (W3C)W3Cs Web Accessibility Initiative (WAI)Web Content Accessibility Guidelines (WCAG) 2.0 IntroductionAssistive TechnologiesBuilding Accessible WebsitesGuideline 1 – PerceivableGuideline 2 – OperableGuideline 3 – UnderstandableGuideline 4 – RobustAccessibility Testing

3. What’s DisabilitySituational DisabilityReaching late to venue… Traffic in cityOops! My mouse stopped working, what do I do?Text is too small on this webpage, how do I read this?Functional DisabilityVisually impairedMobility impairedHard of hearingLearning disabilityAutism, Cerebral Palsy

4. World Wide Web Consortium (W3C)Develops interoperable technologiesSpecificationsGuidelinesSoftwareToolsWhy would they do it?To lead web to its potential and for consistency on web…

5. W3C’s WAI (Web Accessibility Initiative)WAI develops...Guidelines widely considered as the international standard for Web accessibility Support materials to help understand and implement Web accessibility WAI welcomes...Participation from around the world Volunteers to review, implement, and promote guidelines Dedicated participants in working groups

6. Web Content Accessibility Guidelines (WCAG) 2.0WCAG 2.0 has evolved over years based on feedback and recommendation.It defines how to make web content more accessible.Currently WCAG 2.0 is official recommendation http://www.w3.org/tr/wcag20

7. Assistive TechnologiesScreen Magnifier Screen ReaderSpeech RecognitionRefreshable BrailleText BrowsersLarge keyboardMouse substitute such as a joystick, a trackball, on-screen keyboard.Scanning SoftwareSpeech SynthesisSome Pictures

8. Building Accessible WebsitesLaying Accessibility FoundationTable-less layouts – easy to manage, avoid problems for screen readersStructured mark-up – Need for Search Engines, better access to assistive technologiesValid code – Assistive Technologies completely rely on your code, if you mess-up, those users will hate you

9. Guideline 1: PerceptionNon-text contentImages – provide alt / long desc attributeCAPTCHA – provide alternate in audio CAPTCHA or use CAPTCHA based on logical questions

10. Guideline 1: Perceivable – contd., Audio / Visual Content – provide closed captionsAdaptability – should be fleixible. User should be able to use their own style sheetsContrast – ensure that foreground and background will have sufficient contrast

11. Guideline 2: OperableKeyboard access – all information and functionality should be available to access via keyboard including:LinksHeadingsForm fieldsListsTables

12. Guideline 2: Operable – contd.,Enough time – User should have sufficient time to read and interact with content. If content is time-based, same should be notified prior to the session and user should be given an option to extend time limit unless time limit is mandatory.Seizures – seizures should generally be avoided as far as possibleNavigable – Web page should be easily navigable by any input device including assistive technologies

13. Accessible Rich Internet Applications (ARIA)ARIA is WAI Recommendation http://www.w3.org/WAI/intro/aria.phpWAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.

14. Guideline 3: UnderstandableUse of Natural Language – unless a specific terminology is requiredPredictable – User should be able to predict the result upon his actionInput assistance – provide adequate help for user to interact with forms etc.

15. Guideline 4: RobustCompatibility with latest technologies and support for assistive technologiesAdd Accessible Rich Internet Applications (ARIA) support for RIA such as AJAX based applicationsAlertLandmark etc…

16. Accessibility Testing +Manual Testing(Eg: Screen Reader)Automated Tools (Eg: Wave/ FAE)=Accessibility Testing

17. Accessibility Testing - AutomatedWAVE – http://wave.webaim.org/toolbarFirefox Accessibility extensionAdd-ons of Mozilla Firefox https://addons.mozilla.org/en-US/firefox/search?q=accessibility&cat=all

18. Accessibility Testing – ManualScreen ReadersNVDA – http://www.nvda-project.orgJAWS for Windows – http://www.freedomscientific.comScreen MagnifiersZoomTextXtra – http://www.aisquared.comDolphin Supernova – http://www.yourdolphin.comAlternate Input devices – Track ball and switch – http://www.ablenetinc.comDragon Naturally Speaking http://www.nuance.comTalks – a screen reader for mobile S60 phones http://www.nuance.com/talks/

19. Thank You