SlideShare una empresa de Scribd logo
1 de 91
Descargar para leer sin conexión
Accessibility Update: Section 508 and WCAG in a Library 2.0 World,[object Object],Nina McHale,[object Object],Assistant Professor, Web Librarian,[object Object],University of Colorado Denver,[object Object],LITA National Forum,[object Object],October 1-2, 2009,[object Object]
Our Goals: You Will…,[object Object],…achieve an understanding of the history and purpose of accessibility standards,[object Object],…know how to validate code for web standards and accessibility standards,[object Object],…become familiar with screen reader software and how it works,[object Object],…be able to evaluate for accessibility many types of web resources commonly used by libraries,[object Object]
Today’s Agenda,[object Object],Accessibility and usability defined,[object Object],Introduction to web standards,[object Object],Section 508,[object Object],WCAG 2.0,[object Object],Code validation,[object Object],(X)HTML, CSS,[object Object],Validating for accessibility,[object Object]
Tomorrow’s Agenda,[object Object],Screen readers in action,[object Object],Video: How I Use a Screenreader,[object Object],JAWS, Window Eyes, and VoiceOver,[object Object],Demo,[object Object],Case Studies,[object Object],Library web pages,[object Object],Library catalogs and CMSs,[object Object],Vendor databases,[object Object],Web 2.0 tools,[object Object]
Getting to Know You…	,[object Object],Who are you?,[object Object],Name, job title, organization,[object Object],Your experience to date with web design/development/content management and accessibility,[object Object],Why are you here?,[object Object],What to you hope to gain from this session?,[object Object]
Accessibility,[object Object],   “the ‘ability to access’ the functionality, and possible benefit, of some system or entity.”,[object Object],										-Wikipedia, “Accessibility”,[object Object]
Usability,[object Object],   “…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.”,[object Object],-Wikipedia, “Accessibility”,[object Object]
Accessibility Fail,[object Object]
Usability Fail,[object Object]
Why is Accessibility an Issue?,[object Object],Because the increasingly graphic nature of the Web has made using it more difficult for people with visual disabilities to use,[object Object],Because Web browsers are too forgiving of bad code,[object Object],(X)HTML doesn’t have to be perfect to display correctly to a sighted person,[object Object],Because library Web pages tend to be home-grown,[object Object]
Accessibility: Why Does It Matter?,[object Object],The American Foundation for the Blind estimates that:,[object Object],10 million people in the US are blind or visually impaired,[object Object],1.3 million people are legally blind,[object Object],People with learning and physical disabilities use screen readers as well,[object Object],Legal implications: AFB vs. Target,[object Object],Universal Design: writing good code is good practice, and makes it more accessible to all,[object Object]
Excuses, Excuses…,[object Object],“We’re not legally obligated to be accessible.”,[object Object],“It’s too hard to create accessible sites.”,[object Object],“We don’t have (m)any users with disabilities.”,[object Object],“Our vendors don’t; why should we?”,[object Object],“Screen reader technology will catch up.”,[object Object]
History of Accessibility Standards ,[object Object],World Wide Web Consortium (W3C),[object Object],Web Content Access Guidelines (WCAG),[object Object],WCAG 1.0: published May 1999 ,[object Object],WCAG 2.0: published December 2008,[object Object],Federal Government,[object Object],Section 508,[object Object],First published in December 2000 as part of an amendment to to Rehabilitation Act,[object Object],Enforced June 2001,[object Object],Recommendations for update submitted April 2008,[object Object]
WCAG 2.0 and 508: What’s the Difference?,[object Object],WCAG 2.0,[object Object],4 principles, 12 guidelines,[object Object],Has 3 levels of conformance, A-AAA (formerly Priorities 1-3),[object Object],Compliance is voluntary,[object Object],Section 508, Subpart B, §11.94.22 a-p,[object Object],A list of 16 checkpoints,[object Object],A subset of a much larger document, The Rehabilitation Act,[object Object],Compliance is mandatory for some,[object Object]
WCAG 2.0: What’s New?,[object Object],List of 14 guidelines restructured into an outline of 4 principles,[object Object],Not as specific as “checkpoint” format of WCAG 1.0,[object Object],Priorities 1-3 replaced with conformance levels A-AAA ,[object Object],Note: we’ll be reviewing Level A only,[object Object],Met with criticism from developers,[object Object]
WCAG 2.0 Principles 1-2,[object Object],Principle 1: Perceivable,[object Object],Information and user interface components must be presentable to users in ways they can perceive.,[object Object],Principle 2: Operable,[object Object],User interface components and navigation must be operable.,[object Object]
WCAG 2.0 Principles 3-4,[object Object],Principle 3: Understandable,[object Object],Information and the operation of user interface must be understandable.,[object Object],Principle 4: Robust,[object Object],Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.,[object Object]
Principle 1, Guideline 1.1,[object Object],Text alternatives,[object Object],Provide 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. ,[object Object]
1.1.1: Non-text Content,[object Object],[object Object],[object Object]
Principle 1, Guideline 1.2 ,[object Object],Time-based media,[object Object],Provide alternatives for time-based media.,[object Object]
1.2.1: Audio-only and Video-only (Prerecorded): ,[object Object],For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:,[object Object],Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.,[object Object],Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.,[object Object]
1.2.2: Captions (Prerecorded): ,[object Object],Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.,[object Object]
1.2.3:: Audio Description or Media Alternative (Prerecorded): ,[object Object],An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.,[object Object]
Examples, 1.2.1-1.2.3,[object Object],Provide transcripts or captions as appropriate for library podcasts, tutorials, videos, etc.,[object Object],Remember that your audience may include deaf/hard of hearing persons,[object Object],Tip: some tutorial software, including Camtasia and Captivate, can add captions,[object Object]
Principle 1, Guideline 1.3,[object Object],Adaptable,[object Object],Create content that can be presented in different ways (for example simpler layout) without losing information or structure.,[object Object]
1.3.1: Info and Relationships: ,[object Object],Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.,[object Object]
1.3.2: Meaningful Sequence:,[object Object],When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.,[object Object]
1.3.3: Sensory Characteristics:,[object Object],When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.,[object Object],Note: Guideline 1.4 will provide specific guidance on color,[object Object]
Examples 1.3.1-1.3.3,[object Object],Forms,[object Object],Remember, search boxes are forms!,[object Object],Tables,[object Object],Ensure that table data is read/presented in the order in which a sighted person would see it,[object Object],CSS and document structure,[object Object],Scanning content with a screen reader should be just as easy as for a sighted person,[object Object],Use of color,[object Object],“Click the green button to continue.”,[object Object]
Principle 1, Guideline 1.4,[object Object],Distinguishable,[object Object], Make it easier for users to see and hear content including separating foreground from background. ,[object Object]
1.4.1: Use of Color:,[object Object],Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element,[object Object]
1.4.2: Audio Control:,[object Object],If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.,[object Object]
Examples for 1.4.1-1.4.2,[object Object],Forms and color,[object Object],Not accessible: “Required fields are in red.”,[object Object],Accessible: “Required fields are marked by an asterisk.”,[object Object],Audio control,[object Object],Music that plays automatically with no means to stop it drowns out the screen reader,[object Object],All users should control their experience,[object Object],Don’t be MySpace!,[object Object]
Principle 2, Guideline 2.1,[object Object],Keyboard Accessible,[object Object],Make all functionality available from a keyboard.,[object Object]
2.1.1: Keyboard:,[object Object],All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.,[object Object]
2.1.2: No Keyboard Trap:,[object Object],If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.,[object Object]
Examples, 2.1.1-2.1.2,[object Object],Users should be able to operate everything and achieve full functionality with a keyboard—without a mouse.,[object Object],Try using your Library’s website without a mouse.,[object Object]
Principle 2, Guideline 2.2,[object Object],Enough Time,[object Object],Provide users enough time to read and use content,[object Object]
2.2.1: Timing Adjustable:,[object Object],(Summary) The user can:,[object Object],turn off the time limit;,[object Object],adjust the length of the limit (up to 10X); ,[object Object],receive warning of the limit and have 20 seconds to respond.,[object Object]
2.2.2: Pause, Stop, Hide:,[object Object],Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; ,[object Object],Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.,[object Object]
Examples, 2.2.1-2.2.2,[object Object],Does your catalog reset automatically using a meta refresh or other programming trick?,[object Object],Do your interactive tutorials, quizzes, etc., provide a non-visual means to pause and resume?,[object Object]
Principle 2, Guideline 2.3,[object Object],Seizures,[object Object],Do not design content in a way that is known to cause seizures.,[object Object]
2.3.1: Three Flashes or Below Threshold:,[object Object],Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.,[object Object]
Examples, 2.3.1,[object Object],C’mon, it’s not 1997 and <blink> has been deprecated for years!,[object Object],But seriously: does any video content contain flashing lights, such as gunfire or lightning?,[object Object],Blinking and flashing can be distracting for people with low vision or learning disabilities,[object Object]
Principle 2, Guideline 2.4,[object Object],Navigable ,[object Object],Provide ways to help users navigate, find content, and determine where they are. ,[object Object]
2.4.1: Bypass Blocks:,[object Object],A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.,[object Object]
2.4.2: Page Titled:,[object Object],Web pages have titles that describe topic or purpose.,[object Object]
2.4.3: Focus Order:,[object Object],If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.,[object Object]
2.4.4: Link Purpose (In Context):,[object Object],The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.,[object Object]
Examples, 2.4.1-2.4.4,[object Object],Skip navigation techniques (article links),[object Object],How do your templates or web editing/authoring software handle creating <title> content? How does it handle dynamic content?,[object Object],Document structure and use of headings,[object Object],Link labels:,[object Object],Not accessible: “Click here!”,[object Object],Accessible: “Click here for info about…”,[object Object]
Principle 3, Guideline 3.1,[object Object],Readable,[object Object],Make text content readable and understandable. ,[object Object]
3.1.1: Language of Page:,[object Object],The default human language of each Web page can be programmatically determined.,[object Object]
Example, 3.1.1,[object Object],Use the (X)HTML “lang” attribute wisely,[object Object],Screen readers and text-to-speech software can specify language,[object Object]
Principle 3, Guideline 3.2,[object Object],Predictable,[object Object],Make Web pages appear and operate in predictable ways.,[object Object]
3.2.1: On Focus:,[object Object],When any component receives focus, it does not initiate a change of context,[object Object]
3.2.2: On Input:,[object Object],Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.,[object Object]
Examples, 3.2.1-3.2.2,[object Object],When tabbing through navigation or other lists of choices, ensure that selecting an item doesn’t activate it,[object Object],Phone number fields in a form: if there are three separate fields to capture phone number data (area code, exchange, number) users should be alerted that focus will change after they enter area code, etc.,[object Object]
Principle 3, Guideline 3.3,[object Object],Input Assistance,[object Object],Help users avoid and correct mistakes. ,[object Object]
3.3.1: Error Identification:,[object Object],If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.,[object Object]
3.3.2: Labels or Instructions:,[object Object],Labels or instructions are provided when content requires user input,[object Object]
Examples, 3.3.1-3.3.2,[object Object],Form errors/omissions: make sure that they are described by text,[object Object],Where do you have forms in your web presence?,[object Object],Coding forms for accessibility:,[object Object],Jim Thatcher, “Accessible Forms”,[object Object],WebAIM, “Creating Accessible Forms”,[object Object],NCSU, “Creating Accessible Forms”,[object Object]
Principle 4, Guideline 4.1,[object Object],Compatible,[object Object],Maximize compatibility with current and future user agents, including assistive technologies.,[object Object]
4.1.1: Parsing:,[object Object],In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.,[object Object]
4.1.2: Name, Role, Value:,[object Object],For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.,[object Object]
Examples, 4.1.1-4.2.2,[object Object],Write good code and validate it—more on that shortly,[object Object],Applets and other content of that type should conform to accessibility of the language (i.e., Java),[object Object]
Validating Code,[object Object],Why validate?,[object Object],Validating code against web standards,[object Object],Validating web sites for accessibility,[object Object]
Validating for Web Standards,[object Object],W3C tools:,[object Object],HTML: validator.w3.org,[object Object],CSS: jigsaw.w3.org/css-validator,[object Object],Validate live sites or by file upload,[object Object]
Validating for Web Accessibility,[object Object],Bobby/WebXACT: no longer available,[object Object],Cynthia Says,[object Object],Generates thorough reports in 508 and WCAG Priorities 1, 2, and 3,[object Object],Not updated to reflect WCAG 2.0,[object Object],Web Accessibility Evaluation (WAVE) Tool,[object Object],Visual report interface,[object Object],Blog/community support,[object Object]
Day 1 Review and Wrap Up,[object Object],What’s the difference between accessibility and usability?,[object Object],Why do Section 508 and WCAG exist?,[object Object],Why is most of the web not accessible?,[object Object],Describe the concept of “skip navigation.”,[object Object],Why is document structure important?,[object Object],Why should you validate your code?,[object Object],Questions? Comments?,[object Object]
Day 2 Agenda,[object Object],Screen reader software,[object Object],Video: “How I use a Screen Reader”,[object Object],JAWS for Windows,[object Object],Window Eyes,[object Object],VoiceOverfor Mac,[object Object],JAWS Demo,[object Object],Case Studies,[object Object],Small group work,[object Object],Report one case back to all,[object Object]
Using a Computer as a Blind Person – JAWS Screen Reader,[object Object],http://www.youtube.com/watchv=a1uYlgLSKMk,[object Object]
Screen Reader Software,[object Object],Market leaders: JAWS and Window-Eyes,[object Object],enjoy a PC/Mac-like rivalry,[object Object],Common features: ,[object Object],braille output,[object Object],integration with popular services, i.e., iTunes,[object Object],voices in different genders, languages, etc.,[object Object]
JAWS: “Job Access with Speech”,[object Object],Vendor: Freedom Scientific,[object Object],Current version: 10,[object Object],For Windows,[object Object],Pricing: $1095 professional; $895 standard,[object Object],Per the end-user license agreement, using the free download demo for testing purposes is not permitted.,[object Object]
Window Eyes,[object Object],Vendor: GW Micro,[object Object],Current version: 7.1,[object Object],For Windows,[object Object],Pricing:,[object Object],Full version: $895,[object Object],SMA: $299.00,[object Object],No end user restrictions for testing purposes,[object Object]
VoiceOver for Mac ,[object Object],Integrated with OS X since 10.4,[object Object],Also works with iPod Shuffle, Nano, Touch, and iPhone 3GS,[object Object],Different voices and options/features,[object Object],www.apple.com/accessibility/voiceover/,[object Object]
JAWS Demo: What You’ll Hear,[object Object],The percentage of the page loaded announced,[object Object],The number of frames, links, headings, and forms on the web page being read announced,[object Object],The word “edit” when JAWS encounters a form/search box,[object Object],Now close your eyes…,[object Object]
Demo Links,[object Object],Less accessible page:,[object Object],library.auraria.edu/~nmchale/presentations/lita2009/lessaccessible.html,[object Object],More accessible page:,[object Object],library.auraria.edu/~nmchale/presentations/lita2009/moreaccessible.html,[object Object]
Drawbacks to using Screen Readers for Testing Your Sites,[object Object],They have a difficult learning curve,[object Object],They’re expensive,[object Object],Enter Fangs and WAVE!,[object Object],Accessibility evaluation tools,[object Object],Freely available,[object Object],Fangs: a FireFox add-on,[object Object],WAVE: a site where one can enter a URL or upload a file for evaluation,[object Object]
WAVE,[object Object],wave.webaim.org/,[object Object],Provides a visual report:,[object Object]
Fangs Screen Reader Emulator,[object Object],Produces a print transcript similar to the voice output of screen readers,[object Object],Download:,[object Object],sourceforge.net/projects/fangs,[object Object],To create a transcript for a web page:,[object Object],Download Fangs,[object Object],Open Firefox,[object Object],Browse to the Web site you wish to test,[object Object],Tools => Fangs,[object Object]
Fangs Demo,[object Object],What you get from Fangs:,[object Object],Output screen: a screen reader transcript of the current page,[object Object],Headings list: lists all h1-h6 items in the current page,[object Object],Links list: lists all links in the current page,[object Object]
Case Studies,[object Object],What you’ll get for each resource:,[object Object],Screen shot,[object Object],Fangs output screens,[object Object],Some hints,[object Object],What you’ll do:,[object Object],Review these materials for each case,[object Object],Evaluate the samples against WCAG 2.0,[object Object],Provide recommendations to improve accessibility,[object Object],Select the most interesting one to present to the group,[object Object]
What are we going to evaluate?,[object Object],Item 1: a home-grown web page/resource,[object Object],Item 2: a library-specific product that allows for varying levels of customization (i.e., catalogs),[object Object],Item 3: a library tool that is not customizable (i.e., databases) ,[object Object],Item 4: a Web 2.0 tool frequently used by libraries,[object Object]
What to Bring Back to the Group,[object Object],A rating for each resource,[object Object],1=resource unusable for screen readers,[object Object],2=usable, but difficult,[object Object],3=usable,[object Object],4=screen-reader friendly,[object Object],5=screen reader experience as identical as possible to sighted experience,[object Object],List of WCAG 2.0 guidelines followed,[object Object],List of WCAG 2.0 guidelines NOT followed,[object Object],Recommendations for improvement,[object Object]
Take a Deep Breath…,[object Object],Even sites that are meet Level AAA conformance are not accessible to all users with disabilities,[object Object],Partner with existing resources in your community to address accessibility issues,[object Object],Reach out to users with disabilities, including inviting them to participate in usability studies,[object Object]
Accessibility “Help” Pages,[object Object],LexisNexis,[object Object],Facebook,[object Object],Suggestions for Library Disability Help Pages,[object Object],Contact information for disability support,[object Object],List of disability services offered,[object Object],Building access info,[object Object],List of assistive technology offered,[object Object],-Rebecca Power and Chris LeBeau, “How Well Do Academic Library Web Sites Address the Needs of Database Users with Visual Disabilities?” The Reference Librarian, Volume 50, Issue 1, January 2009, pages 55-72 ,[object Object]
When I Get Back to My Library…,[object Object]
Wrapping Up,[object Object],What worked well for you? What not so much?,[object Object],How will you put what you’ve learned to use when you get back?,[object Object],What do you want to know more about?,[object Object],All links from this session: ,[object Object],delicious.com/ninermac/lita2009accessibility,[object Object]
A Final Thought,[object Object], “Sometimes I think sighted people have handicaps of their own. Vision can be very deceptive.” ,[object Object],			-Pat Laing, computer programmer and JAWS user,[object Object]
Questions? Comments?,[object Object],							Nina McHale,[object Object],nina.mchale@ucdenver.edu,[object Object],library.auraria.edu/~nmchale,[object Object],Facebook and Twitter: ninermac,[object Object]
Accessibility Update: Section 508 and WCAG in a Library 2.0 World

Más contenido relacionado

Similar a Accessibility Update: Section 508 and WCAG in a Library 2.0 World

Web Accessibility for Web Developers
Web Accessibility for Web DevelopersWeb Accessibility for Web Developers
Web Accessibility for Web DevelopersAlexander Loechel
 
Accessibility testing kailash 26_nov_ 2010
Accessibility testing kailash 26_nov_ 2010Accessibility testing kailash 26_nov_ 2010
Accessibility testing kailash 26_nov_ 2010Kailash More
 
Wipa Seminar WCAG 2.0
Wipa Seminar WCAG 2.0Wipa Seminar WCAG 2.0
Wipa Seminar WCAG 2.0Roger Hudson
 
Ideas 5 - Roger Hudson - Understanding WCAG 2.0
Ideas 5 - Roger Hudson - Understanding WCAG 2.0Ideas 5 - Roger Hudson - Understanding WCAG 2.0
Ideas 5 - Roger Hudson - Understanding WCAG 2.0awia
 
The quality & richness of E-Education
The quality & richness of E-EducationThe quality & richness of E-Education
The quality & richness of E-EducationSuraj Mehta
 
Boosting new media accessibility - Scott Hollier
Boosting new media accessibility - Scott HollierBoosting new media accessibility - Scott Hollier
Boosting new media accessibility - Scott HollierWeb Directions
 
Accessibility Overview - 508 and WCAG Compliance
Accessibility Overview - 508 and WCAG ComplianceAccessibility Overview - 508 and WCAG Compliance
Accessibility Overview - 508 and WCAG ComplianceFrank Walsh
 
Accessibility Workshop
Accessibility WorkshopAccessibility Workshop
Accessibility WorkshopLar Veale
 
Website Accessibility Workshop
Website Accessibility WorkshopWebsite Accessibility Workshop
Website Accessibility WorkshopDevin Olson
 
Web Site Accessibility: Identifying and Fixing Accessibility Problems in Clie...
Web Site Accessibility: Identifying and Fixing Accessibility Problems in Clie...Web Site Accessibility: Identifying and Fixing Accessibility Problems in Clie...
Web Site Accessibility: Identifying and Fixing Accessibility Problems in Clie...Porfirio Tramontana
 
SEO through Accessibility- How designing accessible websites leads to automat...
SEO through Accessibility- How designing accessible websites leads to automat...SEO through Accessibility- How designing accessible websites leads to automat...
SEO through Accessibility- How designing accessible websites leads to automat...Abhay Rautela
 
Bryan J. Hogan
Bryan J. HoganBryan J. Hogan
Bryan J. HoganVideoguy
 
Icaweb402 a jenninecarlin
Icaweb402 a jenninecarlinIcaweb402 a jenninecarlin
Icaweb402 a jenninecarlinJennine Carlin
 
Usability ≠ Accessibility. An intro to web accessibility for agencies.
Usability ≠ Accessibility. An intro to web accessibility for agencies.Usability ≠ Accessibility. An intro to web accessibility for agencies.
Usability ≠ Accessibility. An intro to web accessibility for agencies.Kate Horowitz
 
Seth Duffy Accessibility97035
Seth Duffy   Accessibility97035Seth Duffy   Accessibility97035
Seth Duffy Accessibility97035FNian
 

Similar a Accessibility Update: Section 508 and WCAG in a Library 2.0 World (20)

doumi94
doumi94doumi94
doumi94
 
Web Accessibility
Web AccessibilityWeb Accessibility
Web Accessibility
 
Microsoft Word - Sample Report
Microsoft Word - Sample ReportMicrosoft Word - Sample Report
Microsoft Word - Sample Report
 
Web Accessibility for Web Developers
Web Accessibility for Web DevelopersWeb Accessibility for Web Developers
Web Accessibility for Web Developers
 
Accessibility testing kailash 26_nov_ 2010
Accessibility testing kailash 26_nov_ 2010Accessibility testing kailash 26_nov_ 2010
Accessibility testing kailash 26_nov_ 2010
 
Wipa Seminar WCAG 2.0
Wipa Seminar WCAG 2.0Wipa Seminar WCAG 2.0
Wipa Seminar WCAG 2.0
 
Ideas 5 - Roger Hudson - Understanding WCAG 2.0
Ideas 5 - Roger Hudson - Understanding WCAG 2.0Ideas 5 - Roger Hudson - Understanding WCAG 2.0
Ideas 5 - Roger Hudson - Understanding WCAG 2.0
 
WCA
WCAWCA
WCA
 
Universal design for e learning final
Universal design for e learning finalUniversal design for e learning final
Universal design for e learning final
 
The quality & richness of E-Education
The quality & richness of E-EducationThe quality & richness of E-Education
The quality & richness of E-Education
 
Boosting new media accessibility - Scott Hollier
Boosting new media accessibility - Scott HollierBoosting new media accessibility - Scott Hollier
Boosting new media accessibility - Scott Hollier
 
Accessibility Overview - 508 and WCAG Compliance
Accessibility Overview - 508 and WCAG ComplianceAccessibility Overview - 508 and WCAG Compliance
Accessibility Overview - 508 and WCAG Compliance
 
Accessibility Workshop
Accessibility WorkshopAccessibility Workshop
Accessibility Workshop
 
Website Accessibility Workshop
Website Accessibility WorkshopWebsite Accessibility Workshop
Website Accessibility Workshop
 
Web Site Accessibility: Identifying and Fixing Accessibility Problems in Clie...
Web Site Accessibility: Identifying and Fixing Accessibility Problems in Clie...Web Site Accessibility: Identifying and Fixing Accessibility Problems in Clie...
Web Site Accessibility: Identifying and Fixing Accessibility Problems in Clie...
 
SEO through Accessibility- How designing accessible websites leads to automat...
SEO through Accessibility- How designing accessible websites leads to automat...SEO through Accessibility- How designing accessible websites leads to automat...
SEO through Accessibility- How designing accessible websites leads to automat...
 
Bryan J. Hogan
Bryan J. HoganBryan J. Hogan
Bryan J. Hogan
 
Icaweb402 a jenninecarlin
Icaweb402 a jenninecarlinIcaweb402 a jenninecarlin
Icaweb402 a jenninecarlin
 
Usability ≠ Accessibility. An intro to web accessibility for agencies.
Usability ≠ Accessibility. An intro to web accessibility for agencies.Usability ≠ Accessibility. An intro to web accessibility for agencies.
Usability ≠ Accessibility. An intro to web accessibility for agencies.
 
Seth Duffy Accessibility97035
Seth Duffy   Accessibility97035Seth Duffy   Accessibility97035
Seth Duffy Accessibility97035
 

Más de Nina McHale

Level Up Web: Modern Web Development and Management Practices for Libraries
Level Up Web: Modern Web Development and Management Practices for LibrariesLevel Up Web: Modern Web Development and Management Practices for Libraries
Level Up Web: Modern Web Development and Management Practices for LibrariesNina McHale
 
Drupal con portland library bof
Drupal con portland library bofDrupal con portland library bof
Drupal con portland library bofNina McHale
 
Mobilizing the User Experience
Mobilizing the User ExperienceMobilizing the User Experience
Mobilizing the User ExperienceNina McHale
 
What Public Library Users Want and How to
What Public Library Users Want and How to What Public Library Users Want and How to
What Public Library Users Want and How to Nina McHale
 
LITA Forum 2012 Web Analytics Preconference
LITA Forum 2012 Web Analytics PreconferenceLITA Forum 2012 Web Analytics Preconference
LITA Forum 2012 Web Analytics PreconferenceNina McHale
 
LITA Forum 2012 Web Analytics Strategy Preconference
LITA Forum 2012 Web Analytics Strategy PreconferenceLITA Forum 2012 Web Analytics Strategy Preconference
LITA Forum 2012 Web Analytics Strategy PreconferenceNina McHale
 
User survey results lc
User survey results lcUser survey results lc
User survey results lcNina McHale
 
Evaluating libraryresourcesamigos
Evaluating libraryresourcesamigosEvaluating libraryresourcesamigos
Evaluating libraryresourcesamigosNina McHale
 
Ten things i've learned about drupal
Ten things i've learned about drupalTen things i've learned about drupal
Ten things i've learned about drupalNina McHale
 
Survey results report
Survey results reportSurvey results report
Survey results reportNina McHale
 
Acrl ucs tech section il 2011 report
Acrl ucs tech section il 2011 reportAcrl ucs tech section il 2011 report
Acrl ucs tech section il 2011 reportNina McHale
 
Making the Case for CMS!
Making the Case for CMS!Making the Case for CMS!
Making the Case for CMS!Nina McHale
 
Building a Single User Experience
Building a Single User ExperienceBuilding a Single User Experience
Building a Single User ExperienceNina McHale
 
Easy In, Easy Out: Customizing Your Open Source Publishing Software
Easy In, Easy Out: Customizing Your Open Source Publishing SoftwareEasy In, Easy Out: Customizing Your Open Source Publishing Software
Easy In, Easy Out: Customizing Your Open Source Publishing SoftwareNina McHale
 
Missouri statelibrarymobile
Missouri statelibrarymobileMissouri statelibrarymobile
Missouri statelibrarymobileNina McHale
 
Getting Started with Drupal
Getting Started with DrupalGetting Started with Drupal
Getting Started with DrupalNina McHale
 

Más de Nina McHale (20)

Level Up Web: Modern Web Development and Management Practices for Libraries
Level Up Web: Modern Web Development and Management Practices for LibrariesLevel Up Web: Modern Web Development and Management Practices for Libraries
Level Up Web: Modern Web Development and Management Practices for Libraries
 
Drupal con portland library bof
Drupal con portland library bofDrupal con portland library bof
Drupal con portland library bof
 
Mobilizing the User Experience
Mobilizing the User ExperienceMobilizing the User Experience
Mobilizing the User Experience
 
Wa mw 2013
Wa mw 2013Wa mw 2013
Wa mw 2013
 
What Public Library Users Want and How to
What Public Library Users Want and How to What Public Library Users Want and How to
What Public Library Users Want and How to
 
LITA Forum 2012 Web Analytics Preconference
LITA Forum 2012 Web Analytics PreconferenceLITA Forum 2012 Web Analytics Preconference
LITA Forum 2012 Web Analytics Preconference
 
LITA Forum 2012 Web Analytics Strategy Preconference
LITA Forum 2012 Web Analytics Strategy PreconferenceLITA Forum 2012 Web Analytics Strategy Preconference
LITA Forum 2012 Web Analytics Strategy Preconference
 
User survey results lc
User survey results lcUser survey results lc
User survey results lc
 
Survey Results
Survey ResultsSurvey Results
Survey Results
 
Evaluating libraryresourcesamigos
Evaluating libraryresourcesamigosEvaluating libraryresourcesamigos
Evaluating libraryresourcesamigos
 
Ten things i've learned about drupal
Ten things i've learned about drupalTen things i've learned about drupal
Ten things i've learned about drupal
 
Drupal fail
Drupal failDrupal fail
Drupal fail
 
Survey results report
Survey results reportSurvey results report
Survey results report
 
Acrl ucs tech section il 2011 report
Acrl ucs tech section il 2011 reportAcrl ucs tech section il 2011 report
Acrl ucs tech section il 2011 report
 
Making the Case for CMS!
Making the Case for CMS!Making the Case for CMS!
Making the Case for CMS!
 
Building a Single User Experience
Building a Single User ExperienceBuilding a Single User Experience
Building a Single User Experience
 
Easy In, Easy Out: Customizing Your Open Source Publishing Software
Easy In, Easy Out: Customizing Your Open Source Publishing SoftwareEasy In, Easy Out: Customizing Your Open Source Publishing Software
Easy In, Easy Out: Customizing Your Open Source Publishing Software
 
Missouri statelibrarymobile
Missouri statelibrarymobileMissouri statelibrarymobile
Missouri statelibrarymobile
 
Getting Started with Drupal
Getting Started with DrupalGetting Started with Drupal
Getting Started with Drupal
 
Blog training
Blog trainingBlog training
Blog training
 

Accessibility Update: Section 508 and WCAG in a Library 2.0 World

  • 1.
  • 2.
  • 3.
  • 4.
  • 5.
  • 6.
  • 7.
  • 8.
  • 9.
  • 10.
  • 11.
  • 12.
  • 13.
  • 14.
  • 15.
  • 16.
  • 17.
  • 18.
  • 19.
  • 20.
  • 21.
  • 22.
  • 23.
  • 24.
  • 25.
  • 26.
  • 27.
  • 28.
  • 29.
  • 30.
  • 31.
  • 32.
  • 33.
  • 34.
  • 35.
  • 36.
  • 37.
  • 38.
  • 39.
  • 40.
  • 41.
  • 42.
  • 43.
  • 44.
  • 45.
  • 46.
  • 47.
  • 48.
  • 49.
  • 50.
  • 51.
  • 52.
  • 53.
  • 54.
  • 55.
  • 56.
  • 57.
  • 58.
  • 59.
  • 60.
  • 61.
  • 62.
  • 63.
  • 64.
  • 65.
  • 66.
  • 67.
  • 68.
  • 69.
  • 70.
  • 71.
  • 72.
  • 73.
  • 74.
  • 75.
  • 76.
  • 77.
  • 78.
  • 79.
  • 80.
  • 81.
  • 82.
  • 83.
  • 84.
  • 85.
  • 86.
  • 87.
  • 88.
  • 89.
  • 90.

Notas del editor

  1. When everyone was using Lynx (text-based browser) it was all good
  2. Legal obligation: “The scope of section 508 is limited to the Federal sector. It does not apply to the private sector, nor does it generally impose requirements on the recipients of Federal funds with the exception of activities carried out in a State under the Assistive Technology Act of 1998, as amended pursuant to section 4(d)(6)(G) of that act.” from http://www.access-board.gov/sec508/summary.htm
  3. Not part of Americans with Disabilities act (1990), which made it illegal to discriminate against people with disabilitiesWikipedia: “The U.S. Rehabilitation Act of 1973 prohibits discrimination on the basis of disability in programs conducted by Federal agencies, in programs receiving Federal financial assistance, in Federal employment, and in the employment practices of Federal contractors.”
  4. Priorities 1-3:Must, should, may
  5. Basic point here is to provide visual content in a way that a screen reader can render it. Content that is purely visual must be dealt with so that information can be gathered by a user with visual disabilitiesIntent: “The intent of this Success Criterion is to make information conveyed by non-text content accessible through the use of a text alternative. Text alternatives are a primary way for making information accessible because they can be rendered through any sensory modality (for example, visual, auditory or tactile) to match the needs of the user. Providing text alternatives allows the information to be rendered in a variety of ways by a variety of user agents.”
  6. Intent: The intent of this Success Criterion is to make information conveyed by non-text content accessible through the use of a text alternative. Text alternatives are a primary way for making information accessible because they can be rendered through any sensory modality (for example, visual, auditory or tactile) to match the needs of the user. Providing text alternatives allows the information to be rendered in a variety of ways by a variety of user agents. For example, a person who cannot see a picture can have the text alternative read aloud using synthesized speech. A person who cannot hear an audio file can have the text alternative displayed so that he or she can read it. In the future, text alternatives will also allow information to be more easily translated into sign language or into a simpler form of the same language.
  7. “The purpose of this guideline is to provide access to time-based and synchronized media. This includes media that is:audio-onlyvideo-only audio-video audio and/or video combined with interaction”
  8. The intent of this Success Criterion is to ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes. For example, the presentation format changes when the content is read by a screen reader or when a user style sheet is substituted for the style sheet provided by the author.Sighted users perceive structure through various visual cues — headings are often in a larger, bold font separated from paragraphs by blank lines; list items are preceded by a bullet and perhaps indented; paragraphs are separated by a blank line; items that share a common characteristic are organized into tabular rows and columns; form fields may be positioned as groups that share text labels; a different background color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them and so on.Auditory cues may be used as well. For example, a chime might indicate the beginning of a new section; a change in voice pitch or speech rate may be used to emphasize important information or to indicate quoted text; etc.When such relationships are perceivable to one set of users, those relationships can be made to be perceivable to all. One method of determining whether or not information has been properly provided to all users is to access the information serially in different modalities.If links to glossary items are implemented using anchor elements (or the proper link element for the technology in use) and identified using a different font face, a screen reader user will hear that the item is a link when the glossary term is encountered even though they may not receive information about the change in font face. An on-line catalog may indicate prices using a larger font colored red. A screen reader or person who cannot perceive red, still has the information about the price as long as it is preceded by the currency symbol.Some technologies do not provide a means to programmatically determine some types of information and relationships. In that case then there should be a text description of the information and relationships. For instance, &quot;all required fields are marked with an asterisk (*)&quot;. The text description should be near the information it is describing (when the page is linearized), such as in the parent element or in the adjacent element.There may also be cases where it may be a judgment call about what information should appear in text and what would need to be directly associated, and it may be most appropriate to duplicate some information (for instance, in an HTML table, providing the summary both in the paragraph before the table and in the summary attribute of the table itself). However, wherever possible it is necessary for the information to be programmatically determined rather than providing a text description before encountering the table.Note: It is not required that color values be programmatically determined. The information conveyed by color cannot be adequately presented simply by exposing the value. Therefore, Success Criterion 1.4.1 addresses the specific case of color, rather than Success Criterion 1.3.1.
  9. The intent of this Success Criterion is to enable a user agent to provide an alternative presentation of content while preserving the reading order needed to understand the meaning. It is important that it be possible to programmatically determine at least one sequence of the content that makes sense. Content that does not meet this Success Criterion may confuse or disorient users when assistive technology reads the content in the wrong order, or when alternate style sheets or other formatting changes are applied.A sequence is meaningful if the order of content in the sequence cannot be changed without affecting its meaning. For example, if a page contains two independent articles, the relative order of the articles may not affect their meaning, as long as they are not interleaved. In such a situation, the articles themselves may have meaningful sequence, but the container that contains the articles may not have a meaningful sequence.The semantics of some elements define whether or not their content is a meaningful sequence. For instance, in HTML, text is always a meaningful sequence. Tables and ordered lists are meaningful sequences, but unordered lists are not.The order of content in a sequence is not always meaningful. For example, the relative order of the main section of a Web page and a navigation section does not affect their meaning. They could occur in either order in the programmatically determined reading sequence. As another example, a magazine article contains several callout sidebars. The order of the article and the sidebars does not affect their meaning. In these cases there are number of different reading orders for a Web page that can satisfy the Success Criterion.
  10. The intent of this Success Criterion is to ensure that all users can access instructions for using the content, even when they cannot perceive shape or size or use information about spatial location or orientation. Some content relies on knowledge of the shape or position of objects that are not available from the structure of the content (for example, &quot;round button&quot; or &quot;button to the right&quot;). Some users with disabilities are not able to perceive shape or position due to the nature of the assistive technologies they use. This Success Criterion requires that additional information be provided to clarify anything that is dependent on this kind of information.Providing information using shape and/or location, however, is an effective method for many users including those with cognitive limitations. This provision should not discourage those types of cues as long as the information is also provided in other ways.In some languages, it is commonly understood that &quot;above&quot; refers to the content previous to that point in the content and &quot;below&quot; refers to the content after that point. In such languages, if the content being referenced is in the appropriate place in the reading order and the references are unambiguous, statements such as &quot;choose one of the links below&quot; or &quot;all of the above&quot; would conform to this Success Criterion.Specific Benefits of Success Criterion 1.3.3:People who are blind and people who have low vision may not be able to understand information if it is conveyed by shape and/or location. Providing additional information other than shape and/or location will allow them to understand the information conveyed by shape and/or alone.
  11. The intent of this Success Criterion is to ensure that all users can access information that is conveyed by color differences, that is, by the use of color where each color has a meaning assigned to it. If the information is conveyed through color differences in an image (or other non-text format), the color may not be seen by users with color deficiencies. In this case, providing the information conveyed with color through another visual means ensures users who cannot see color can still perceive the information.Color is an important asset in design of Web content, enhancing its aesthetic appeal, its usability, and its accessibility. However, some users have difficulty perceiving color. People with partial sight often experience limited color vision, and many older users do not see color well. In addition, people using text-only, limited-color or monochrome displays and browsers will be unable to access information that is presented only in color.Examples of information conveyed by color differences: “required fields are red&quot;, “error is shown in red&quot;, and “Mary&apos;s sales are in red, Tom&apos;s are in blue&quot;. Examples of indications of an action include: using color to indicate that a link will open in a new window or that a database entry has been updated successfully. An example of prompting a response would be: using highlighting on form fields to indicate that a required field had been left blank.Note: This should not in any way discourage the use of color on a page, or even color coding if it is redundant with other visual indication.
  12. Individuals who use screen reading software can find it hard to hear the speech output if there is other audio playing at the same time. This difficulty is exacerbated when the screen reader&apos;s speech output is software based (as most are today) and is controlled via the same volume control as the sound. Therefore, it is important that the user be able to turn off the background sound. Note: Having control of the volume includes being able to reduce its volume to zero.Note: Playing audio automatically when landing on a page may affect a screen reader user&apos;s ability to find the mechanism to stop it because they navigate by listening and automatically started sounds might interfere with that navigation. Therefore, we discourage the practice of automatically starting sounds (especially if they last more than 3 seconds), and encourage that the sound be started by an action initiated by the user after they reach the page, rather than requiring that the sound be stopped by an action of the user after they land on the page.
  13. The intent of this Success Criterion is to ensure that, wherever possible, content can be operated through a keyboard or keyboard interface (so an alternate keyboard can be used). When content can be operated through a keyboard or alternate keyboard, it is operable by people with no vision (who cannot use devices such as mice that require eye-hand coordination) as well as by people who must use alternate keyboards or input devices that act as keyboard emulators. Keyboard emulators include speech input software, sip-and-puff software, on-screen keyboards, scanning software and a variety of assistive technologies and alternate keyboards. Individuals with low vision also may have trouble tracking a pointer and find the use of software much easier (or only possible) if they can control it from the keyboard.Examples of &quot;specific timings for individual keystrokes&quot; include situations where a user would be required to repeat or execute multiple keystrokes within a short period of time or where a key must be held down for an extended period before the keystroke is registered.The phrase &quot;except where the underlying function requires input that depends on the path of the user&apos;s movement and not just the endpoints&quot; is included to separate those things that cannot reasonably be controlled from a keyboard.Most actions carried out by a pointing device can also be done from the keyboard (for example, clicking, selecting, moving, sizing). However, there is a small class of input that is done with a pointing device that cannot be done from the keyboard in any known fashion without requiring an inordinate number of keystrokes. Free hand drawing, watercolor painting, and flying a helicopter through an obstacle course are all examples of functions that require path dependent input. Drawing straight lines, regular geometric shapes, re-sizing windows and dragging objects to a location (when the path to that location is not relevant) do not require path dependent input.The use of MouseKeys would not satisfy this Success Criterion because it is not a keyboard equivalent to the application; it is a mouse equivalent (i.e., it looks like a mouse to the application).It is assumed that the design of user input features takes into account that operating system keyboard accessibility features may be in use. For example, modifier key locking may be turned on. Content continues to function in such an environment, not sending events that would collide with the modifier key lock to produce unexpected results.
  14. The intent of this Success Criterion is to ensure that that content does not &quot;trap&quot; keyboard focus within subsections of content on a Web page. This is a common problem when multiple formats are combined within a page and rendered using plug-ins or embedded applications.There may be times when the functionality of the Web page restricts the focus to a subsection of the content, as long as the user knows how to leave that state and &quot;untrap&quot; the focus.
  15. Grandpa McHale
  16. The intent of this Success Criterion is to ensure that users with disabilities are given adequate time to interact with Web content whenever possible. People with disabilities such as blindness, low vision, dexterity impairments, and cognitive limitations may require more time to read content or to perform functions such as filling out on-line forms. If Web functions are time-dependent, it will be difficult for some users to perform the required action before a time limit occurs. This may render the service inaccessible to them. Designing functions that are not time-dependent will help people with disabilities succeed at completing these functions. Providing options to disable time limits, customize the length of time limits, or request more time before a time limit occurs helps those users who require more time than expected to successfully complete tasks. These options are listed in the order that will be most helpful for the user. Disabling time limits is better than customizing the length of time limits, which is better than requesting more time before a time limit occurs.Any process that happens without user initiation after a set time or on a periodic basis is a time limit. This includes partial or full updates of content (for example, page refresh), changes to content, or the expiration of a window of opportunity for a user to react to a request for input.It also includes content that is advancing or updating at a rate beyond the user&apos;s ability to read and/or understand it. In other words, animated, moving or scrolling content introduces a time limit on a users ability to read content.In some cases, however, it is not possible to change the time limit (for example, for an auction or other real-time event) and exceptions are therefore provided for those cases.
  17. The intent of this Success Criterion is to avoid distracting users during their interaction with a Web page.&quot;Moving, blinking and scrolling&quot; refers to content in which the visible content conveys a sense of motion. Common examples include motion pictures, synchronized media presentations, animations, real-time games, and scrolling stock tickers. &quot;Auto-updating&quot; refers to content that updates or disappears based on a preset time interval. Common time-based content includes audio, automatically updated weather information, news, stock price updates, and auto-advancing presentations and messages. The requirements for moving, blinking and scrolling content and for auto-updating content are the same except that:authors have the option of providing the user with a means to control the frequency of updates when content is auto-updating andthere is no three second exception for auto-updating since it makes little sense to auto-update for just three seconds and then stopContent that moves or auto-updates can be a barrier to anyone who has trouble reading stationary text quickly as well as anyone who has trouble tracking moving objects. It can also cause problems for screen readers.Moving content can also be a severe distraction for some people. Certain groups, particularly those with attention deficit disorders, find blinking content distracting, making it difficult for them to concentrate on other parts of the Web page. Five seconds was chosen because it is long enough to get a user&apos;s attention, but not so long that a user cannot wait out the distraction if necessary to use the page.
  18. The intent of this Success Criterion is to allow people who navigate sequentially through content more direct access to the primary content of the Web page. Web pages and applications often have content that appears on other pages or screens. Examples of repeated blocks of content include but are not limited to navigation links, heading graphics, and advertising frames. Small repeated sections such as individual words, phrases or single links are not considered blocks for the purposes of this provision.This is in contrast to a sighted user&apos;s ability to ignore the repeated material either by focusing on the center of the screen (where main content usually appears) or a mouse user&apos;s ability to select a link with a single mouse click rather than encountering every link or form control that comes before the item they want.It is not the intent of this Success Criterion to require authors to provide methods that are redundant to functionality provided by the user agent. Most web browsers provide keyboard shortcuts to move the user focus to the top of the page, so if a set of navigation links is provided at the bottom of a web page providing a &quot;skip&quot; link may be unnecessary.
  19. A banking application lets a user inspect his bank accounts, view past statements, and perform transactions. The Web application dynamically generates titles for each Web page, e.g., &quot;Bank XYZ, accounts for John Smith&quot; &quot;Bank XYZ, December 2005 statement for Account 1234-5678&quot;.
  20. The intent of this Success Criterion is to ensure that when users navigate sequentially through content, they encounter information in an order that is consistent with the meaning of the content and can be operated from the keyboard. This reduces confusion by letting users form a consistent mental model of the content. There may be different orders that reflect logical relationships in the content. For example, move through components in a table one row at a time or one column at a time both reflect the logical relationships in the content. Either order may satisfy this Success Criterion.The way that sequential navigation order is determined in Web content is defined by the technology of the content. For example, simple HTML defines sequential navigation via the notion of tabbing order. Dynamic HTML may modify the navigation sequence using scripting along with the addition of a tabindex attribute to allow focus to additional elements. If no scripting or tabindex attributes are used, the navigation order is the order that components appear in the content stream. (See HTML 4.01 Specification, section 17.11, &quot;Giving focus to an element&quot;).An example of keyboard navigation that is not the sequential navigation addressed by this Success Criterion is using arrow key navigation to traverse a tree component. The user can use the up and down arrow keys to move from tree node to tree node. Pressing the left arrow key may expand a node, then using the down arrow key, will move into the newly expanded nodes. This navigation sequence follows the expected sequence for a tree control - as additional items get expanded or collapsed, they are added or removed from the navigation sequence.The focus order may not be identical to the programmatically determined reading order (see Success Criterion 1.3.2) as long as the user can still understand and operate the Web page. Since there may be several possible logical reading orders for the content, the focus order may match any of them. However, when the order of a particular presentation differs from the programmatically determined reading order, users of one of these presentations may find it difficult to understand or operate the Web page. Authors should carefully consider all these users as they design their Web pages.For example, a screen reader user interacts with the programmatically determined reading order, while a sighted keyboard user interacts with the visual presentation of the Web page. Care should be taken so that the focus order makes sense to both of these sets of users and does not appear to either of them to jump around randomly.
  21. * This Success Criterion helps users with disabilities by making interactive content more predictable. Unexpected changes of context can be so disorienting for users with visual disabilities or cognitive limitations that they are unable to use the content. * Individuals who are unable to detect changes of context are less likely to become disoriented while navigating a site. For example:o Individuals who are blind or have low vision may have difficulty knowing when a visual context change has occurred, such as a new window popping up. In this case, warning users of context changes in advance minimizes confusion when the user discovers that the back button no longer behaves as expected. * Some individuals with low vision, with reading and intellectual disabilities, and others who have difficulty interpreting visual cues may benefit from additional cues in order to detect changes of context.
  22. The intent of this Success Criterion is to ensure that users are aware that an error has occurred and can determine what is wrong. The error message should be as specific as possible. In the case of an unsuccessful form submission, re-displaying the form and indicating the fields in error is insufficient for some users to perceive that an error has occurred. Screen reader users, for example, will not know there was an error until they encounter one of the indicators. They may abandon the form altogether before encountering the error indicator, thinking that the page simply is not functional.The identification and description of an error can be combined with programmatic information that user agents or assistive technologies can use to identify an error and provide error information to the user. For example, certain technologies can specify that the user&apos;s input must not fall outside a specific range, or that a form field is required. Currently, few technologies support this kind of programmatic information, but the Success Criterion does not require, nor prevent it.It is perfectly acceptable to indicate the error in other ways such as image, color etc, in addition to the text description.
  23. The intent of this Success Criterion is to help users avoid making mistakes when their input is required. To help avoid mistakes it is good user interface design to provide simple instructions and cues for entering information. Some users with disabilities may be more likely to make mistakes than users without disabilities or recovery from mistakes may be more difficult, making mistake avoidance an important strategy for users with disabilities. People with disabilities rely on well documented forms and procedures to interact with a page. Blind users need to know exactly what information should be entered into form fields and what the available choices are. Simple instructions visually connected to form controls can assist users with cognitive disabilities or those accessing a page using a screen magnifier.
  24. Forms in library web pages: comments, OPAC (suggest a book, search, check patron info)
  25. Validation=checking something to see if it meets established standards and criteria
  26. Find ways to provide pathways for users with disabilities to get what they need.