Accessibility Update: Section 508 and WCAG in a Library 2.0 World
out of 91
Post on 07-May-2015
DESCRIPTIONPreconference session from the 2009 LITA National Forum, Salt Lake City. Accompanying case studies also available on Slideshare.
1.Accessibility Update: Section 508 and WCAG in a Library 2.0 WorldNina McHaleAssistant Professor, Web LibrarianUniversity of Colorado DenverLITA National ForumOctober 1-2, 20092. Our Goals: You Willachieve an understanding of the history and purpose of accessibility standardsknow how to validate code for web standards and accessibility standardsbecome familiar with screen reader software and how it worksbe able to evaluate for accessibility many types of web resources commonly used by libraries3. Todays AgendaAccessibility and usability definedIntroduction to web standardsSection 508WCAG 2.0Code validation(X)HTML, CSSValidating for accessibility4. Tomorrows AgendaScreen readers in actionVideo: How I Use a ScreenreaderJAWS, Window Eyes, and VoiceOverDemoCase StudiesLibrary web pagesLibrary catalogs and CMSsVendor databasesWeb 2.0 tools5. Getting to Know YouWho are you?Name, job title, organizationYour experience to date with web design/development/content management and accessibilityWhy are you here?What to you hope to gain from this session?6. Accessibility the ability to access the functionality, and possible benefit, of some system or entity.-Wikipedia, Accessibility7. Usability the extent to which a product (e.g., device, service, environment) can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.-Wikipedia, Accessibility8. Accessibility Fail9. Usability Fail10. Why is Accessibility an Issue?Because the increasingly graphic nature of the Web has made using it more difficult for people with visual disabilities to useBecause Web browsers are too forgiving of bad code(X)HTML doesnt have to be perfect to display correctly to a sighted personBecause library Web pages tend to be home-grown11. Accessibility: Why Does It Matter?The American Foundation for the Blind estimates that:10 million people in the US are blind or visually impaired1.3 million people are legally blindPeople with learning and physical disabilities use screen readers as wellLegal implications: AFB vs. TargetUniversal Design: writing good code is good practice, and makes it more accessible to all12. Excuses, ExcusesWere not legally obligated to be accessible.Its too hard to create accessible sites.We dont have (m)any users with disabilities.Our vendors dont; why should we?Screen reader technology will catch up.13. History of Accessibility Standards World Wide Web Consortium (W3C)Web Content Access Guidelines (WCAG)WCAG 1.0: published May 1999 WCAG 2.0: published December 2008Federal GovernmentSection 508First published in December 2000 as part of an amendment to to Rehabilitation ActEnforced June 2001Recommendations for update submitted April 200814. WCAG 2.0 and 508: Whats the Difference?WCAG 2.04 principles, 12 guidelinesHas 3 levels of conformance, A-AAA (formerly Priorities 1-3)Compliance is voluntarySection 508, Subpart B, 11.94.22 a-pA list of 16 checkpointsA subset of a much larger document, The Rehabilitation ActCompliance is mandatory for some15. WCAG 2.0: Whats New?List of 14 guidelines restructured into an outline of 4 principlesNot as specific as checkpoint format of WCAG 1.0Priorities 1-3 replaced with conformance levels A-AAA Note: well be reviewing Level A onlyMet with criticism from developers16. WCAG 2.0 Principles 1-2Principle 1: PerceivableInformation and user interface components must be presentable to users in ways they can perceive.Principle 2: OperableUser interface components and navigation must be operable.17. WCAG 2.0 Principles 3-4Principle 3: UnderstandableInformation and the operation of user interface must be understandable.Principle 4: RobustContent must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.18. Principle 1, Guideline 1.1Text alternativesProvide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. 19. 1.1.1: Non-text ContentAll non-text content that is presented to the user has a text alternative that serves the equivalent purpose.
View more >
An approach to Web Accessibility. Reminder WCAG 2.0.Web accessibility is formally defined by the World Wide Web Consortium (W3C), whose Web Content Accessibility.
Minnesota State Accessibility Guidelines Guidelines -Nov2013clean...Minnesota State Accessibility Guidelines . ... start with a template that has accessibility built in. ... • Section 508 VPAT (Word) • WCAG 2.0 VPAT ...
Name of Policy: Technology Accessibility Policy Number ... of Policy: Technology Accessibility Policy Number: ... Content Accessibility Guidelines version 2.0(a) (WCAG 2.0), ... Voluntary Product Accessibility Template
ATI's Web Content Accessibility Guidelines (WCAG) 2.0 ... purpose of the Voluntary Product Accessibility Template ... • A Section 508 andn WCAG 2.0 VPAT are required for all ... Leaving it blank or stating Software ...
The New Accessibility Guidelines: WCAG 2.0. What’s happening in the Graveyard Shift? Not covering everything in WCAG 2.0 Focusing on –some of the good.
Migrating from WCAG 1.0 to WCAG 2.0 – A comparative study based on Web Content Accessibility Guidelines in Taiwan
Web Content Accessibility Guidelines (WCAG) 2 This section is informative. Web Content Accessibility Guidelines (WCAG) 2.0 defines how to make Web content more. accessible to people with disabilities.
ATI's Section 508 Voluntary Product Accessibility Template ... s Section 508 Voluntary Product Accessibility Template ... •A Section 508 andn WCAG 2.0 VPAT are required for all ... Leaving it blank or stating ...
Web Content Accessibility Guidelines (WCAG) 2.0 This section is informative. Web Content Accessibility Guidelines (WCAG) 2.0 defines how to make Web content more. accessible to people with disabilities.