ECA 228 Internet/Intranet Design I Accessibility.

Slides:



Advertisements
Similar presentations
Adapting Technology Changing Lives Web accessibility Web accessibility and Disability A Practical introduction Robin Christopherson and Curt Holst AbilityNet.
Advertisements

Web Accessibility Web Services Office of Communications.
Introduction to Web Accessibility. What is Web Accessibility Web accessibility means that people with disabilities can use the Web Disabilities including.
1 Accessibility CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology April 16, 2007.
Web Content Accessibility Guidelines (WCAG) Overview Copyright © World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de.
Designing a Multimedia System Information (Content) Design Structural/Navigational Design Human Computer Interaction (Interactivity Issues)
CM143 - Web Week 11 Accessibility Priority Checkpoints.
Web Accessibility Issues. Why Consider Access Issues ? Discrimination Numbers of disabled students in HE likely to increase Sites designed for the disabled.
IV. “Regular” Web Pages: HTML A Web Accessibility Primer: Usability for Everyone Office of Web Communications.
Americans with Disabilities Act Ms. Sam Wainford.
Copenhagen, 6 June 2006 Modern Web standards in CHM portals Mădălina Sauca Finsiel Romania.
Universal Design & Web Accessibility Iain Murray Kerry Hoath Iain Murray Kerry Hoath.
Electronic Communication and Web Accessibility Workshop.
Debi Orton, Co-Chair NYS Forum IT Accessibility Committee.
Chapter 12: AccessibilityCopyright © 2004 by Prentice Hall Issues Involving Vision Range Total blindness Impaired vision Color blindness Photosensitive.
Making IT Accessible Iain Murray School of Electrical & Computer Engineering Curtin University of Technology
Assistive Technology and Web Accessibility University of Hawaii Information Technology Services Jon Nakasone.
© Simeon Keates 2008 Usability with Project Lecture 7 – 30/09/09 Dr. Simeon Keates.
Accessibility – 1h. Why produce web sites for people with a disability? Moral Reasons Business – A growing market that gets bigger as the population ages.
Week 2 Web Site Design Principles. 2 Design for the Computer Medium Craft the look and feel Make your design portable Design for low bandwidth Plan for.
Web Accessibility Bernie D. Davenport & A. Craig Dixon September 26, 2007.
Is Your Website Accessible? Stephanie M. Brown School of Health, Physical Education, and Recreation Indiana University.
Planning an Accessible Website: Beyond Alt Tags Stephanie M. Randolph School of Health, Physical Education, and Recreation Indiana University.
The Internet Writer’s Handbook 2/e Web Accessibility Writing for the Web.
COMM1PCOMM1P Alan Woolrych Accessibility 9 COMM1P9COMM1P9 SCET MSc EC/ECA © Alan Woolrych 2001 Introduction Accessibility “Making Content Available to.
Technology for Students with Special Needs E.Brown Forward.
Oreste Signore- WAI/1 Amman, December 2006 WAI Initiative on accessibility Ministerial NEtwoRk for Valorising Activities in digitisation.
Web Accessiblity Carol Gordon SIU Medical Library.
1 © Netskills Quality Internet Training, University of Newcastle Web Page Design © Netskills, Quality Internet Training University.
Design and Construction of Accessible Web Sites Michael Burks Chairman Internet Society SIG For Internet Accessibility for People with Disabilities June.
Is Your Site Accessible? Web Site Testing for Accessibility Presented by: The NYS Forum IT Accessibility Committee The NYS Forum Webmasters Guild Northeast.
Emily Gibson The College of New Jersey An Evaluation of Current Software Tools* Evaluation & Repair Software.
Website Accessibility. What is Website Accessibility? Making information on the internet usable and understandable for EVERYONE, including those with.
An Overview 1 Pamela Harrod, DMS 546/446 Presentation, March 17, 2008.
Section 508 requirements for Federal Website Design Jon Brundage MDCFUG 4/10/01.
Daniel Njuguna – IT Officer/ Adaptive Technology Trainer Kenya Society For The Blind Accessibility in ICT’s.
Evolution of Web Accessibility Meenakshi Sripal COMS E6125.
Overview of the web accessibility guidelines at RMIT: W3C's WAI Level A Conformance Praneeth Putlur Rajiv Pandya Rohit Sharma.
Planning an Accessible Website: Beyond Alt Tags Stephanie M. Randolph School of Health, Physical Education, and Recreation Indiana University.
Making Web Pages Accessible Chapter 9 Learn how to… List guidelines and standards for making Web sites accessible. List HTML coding practices to make.
WEB ACCESSIBILITY. WHAT IS IT? Web accessibility means that people with disabilities can use the Web. Web accessibility encompasses all disabilities that.
Group 3: Art Gallery Monica Almendarez Content/Project Manager Willliam Egle Technology Manager Christina Pié Usability/ADA Compliance Manager Mirjana.
Date or reference Web Accessibility - an introduction Patrick H. Lauke ISI presentation - 22/11/2004.
Accessibility and the web Lecturer: Judy Kay References: Readings - W3C - Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0
Fundamentals of Graphic Communication 3.5 Accessible Design.
Accessibility : Designing the Interface and Navigation The Non-Designer’s Web Book Chapter 7 Robin Williams and John Tollett Presented by Sherie Loika.
Technical Communication A Practical Approach Chapter 14: Web Pages and Writing for the Web William Sanborn Pfeiffer Kaye Adkins.
Is Your Site Accessible? Validating Your Web Site.
Accessibility Mohammed Alabdulkareem
A centre of expertise in digital information managementwww.ukoln.ac.uk Accessibility and Usability For Web Sites: An Introduction to Web Accessibility.
Sara Di Giorgio Giza, 3 April 2006 WAI Initiative on accessibility Ministerial NEtwoRk for Valorising Activities in digitisation.
1 GENASYS.usm.maine.edu PT3 Catalyst Grant GENASYS University of Southern Maine 301C Bailey Hall 37 College Avenue, Gorham, ME Generating Assistive.
 Accessibility & Information Architecture Presented by Liz Molleur INF385E April 5 th, 2009.
The User Experience “Keeping Web Accessibility In Mind” Video available online at:
Accessibility Basics on creating accessible websites Accessibility Seth Duffey presentation for MAG Telecommunications.
1 Making an Accessible Web Site Sec 508 Standards – How Tos Evelyn Li University of Wisconsin-Fox Valley.
Web Accessibility. Why accessibility? "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect."
Making the Web Accessible to Impaired Users
These standards will serve us well in any technical communication job.
Introduction to Web Accessibility
Creating ADA Compliant Resources
Web Content Accessibility Beata M. Ofianewska (DG COMM) 7 December 2006 December 2006 COMM C2.
Website Accessibility
Web Accessibility An Introduction.
International University of Japan
Course Web Technology Guus Schreiber
Web Standards and Accessible Design.
Demystifying Web Content Accessibility Guidelines
Accessibility Evaluation
Accessibility.
Presentation transcript:

ECA 228 Internet/Intranet Design I Accessibility

ECA 228 Internet/Intranet Design I accessibility issues some users – can’t see, hear, or move the way we do – may not mentally process information easily – may have difficulty reading – may not be able to use keyboard or mouse – may have a text-only screen, or very small screen – may have a voice browser

ECA 228 Internet/Intranet Design I accessibility issues cont … making your site accessible to users with disabilities may benefit all users – EG, your choice to use stylesheets to control style across your site may benefit a user with low vision, but may actually decrease download time for all users by law, some sites must be accessible to more than just sighted, hearing users

ECA 228 Internet/Intranet Design I Web Accessibility Initiative WAI attempts to make the web more accessible to everyone 5 primary areas 1. Technology 2. Guidelines 3. Tools 4. Education and Outreach 5. Research and Development

ECA 228 Internet/Intranet Design I guidelines Guidelines address 2 general themes: Graceful Transformation – separate structure from presentation – provide text alternatives, such as the alt attribute in tags – create documents that work even if users cannot see or hear – include information that serves the same purpose as audio or video – create documents that do not rely on one type of hardware, eg, large monitors

ECA 228 Internet/Intranet Design I guidelines cont … Making Content Understandable and Navigable – make language clear and simple – provide understandable mechanisms for navigating through site – some users cannot use image maps, frames, graphics – some users may lose contextual information when they can view only a portion of the page put important information above fold eg, magnified images only display one word at a time Braille readers

ECA 228 Internet/Intranet Design I guidelines cont … checkpoints – each guideline may contain one or more checkpoints explanations of how the guideline applies in real-world scenario – each checkpoint is assigned a priority level

ECA 228 Internet/Intranet Design I priority levels Level 1 – site must satisfy this checkpoint, otherwise it will be impossible for some groups to access information Level 2 – site should satisfy this checkpoint – significant barriers may be removed Level3 – site may address this checkpoint – will improve overall accessibility

ECA 228 Internet/Intranet Design I conformance A document may be rated on its compliance to the 3 priority levels 3 levels of conformance standards 1. LEVEL A: all Priority 1 checkpoints are satisfied 2. LEVEL Double-A: all Priority 1 and 2 checkpoints are satisfied 3. LEVEL Triple_A: all Priority 1, 2, and 3 checkpoints are satisfied Know Your Audience

ECA 228 Internet/Intranet Design I Guideline 1 – if a user cannot use images, movies, sounds, etc, provide equivalent information – guidelines do not suggest avoiding using the above, but providing a text equivalent – text equivalents may be used as synthesized speech, Braille, visually displayed text Provide equivalent alternatives to auditory and visual content.

ECA 228 Internet/Intranet Design I Guideline 1 cont … – text equivalent must serve the same function or purpose as an image – EG, the purpose of image of earth from outer space decoration alt = “photograph of earth from outer space” illustration of world geography alt = “the polar caps can clearly be seen from outer space” link to information about the earth alt = “click this link for more information about the earth”

ECA 228 Internet/Intranet Design I Guideline 1 cont … – if the text conveys the same purpose for a user with a disability as the image does for other users, it can be considered equivalent – consider using non-text equivalents (pictures, video, audio) for users who have difficulty reading – Checkpoints: Provide text equivalent for every non-text element, including images, applets, ascii art, animations, buttons, image map regions, etc

ECA 228 Internet/Intranet Design I Guideline 2 – ensure that that text and graphics are understandable when viewed without color – foreground and background should not be too close to the same hue – some users may not be able to differentiate colors – Checkpoints: Make sure any information conveyed with color is also conveyed other ways as well Don't rely on color alone.

ECA 228 Internet/Intranet Design I Guideline 3 – markup documents with proper structural elements – control presentation with style sheets rather than presentational elements – invalid HTML hinders accessibility – using a table to lay out a page may cause problems – do not use presentational markup to convey structure Use markup and style sheets and do so properly.

ECA 228 Internet/Intranet Design I Guideline 4 – identify predominant natural language of the document using meta tags – Checkpoints: Identify changes in the natural language of a documents text. EG, if you include a non-English word in an English document, identify the language with the lang attribute. Clarify natural language usage.

ECA 228 Internet/Intranet Design I Guideline 5 – tables should be used to mark up tabular data, not to lay out a page – Checkpoints: For data tables having 2 or more logical levels of rows or columns ( header cells, body, footer) use markup to designate those levels ( thead, tbody, tfoot ) Identify row and column headers Create tables that transform gracefully.

ECA 228 Internet/Intranet Design I Guideline 5 cont … – some screen readers reads table cells straight across – will be read as Abraham Lincoln's Gettysburg Address, delivered 19 November, 1863 Four score and seven years ago our fathers brought forth upon this continent a new nation … Abraham Lincoln's Gettysburg Four score and seven years ago Address, delivered 19 November, our fathers brought forth upon 1863 this continent a new nation …

ECA 228 Internet/Intranet Design I Guideline 6 – ensure that pages are accessible even when newer technologies are not supported or are turned off – Checkpoints: Organize the structure of your document so that it still makes sense even if style sheets are not working as you expect Ensure that pages are usable even when scripts, applets, and other objects are turned off Ensure that pages featuring new technologies transform gracefully.

ECA 228 Internet/Intranet Design I Guideline 7 – ensure that moving, blinking, scrolling, or auto-updating objects or pages may be paused or stopped – Checkpoints: Avoid causing the screen to flicker – some people with epilepsy can have seizures triggered by flickering or flashing in the 4 to 59 flashes per second range Ensure user control of time-sensitive content changes.

ECA 228 Internet/Intranet Design I Guideline 8 – when you have an embedded object that has its own interface, make sure that interface as well is accessible – Checkpoints: Make programmatic elements such as scripts and applets compatible with assistive technologies Ensure direct accessibility of embedded user interfaces.

ECA 228 Internet/Intranet Design I Guideline 9 – use features that enable activation of page elements via a variety of input devices – don’t rely only on one device (mouse, keyboard, etc) to navigate through site – Checkpoints: Provide client-side image maps rather than server-side image maps Design for device-independence.

ECA 228 Internet/Intranet Design I Guideline 10 – Use interim accessibility solutions so that assistive technologies and older browsers will operate correctly – interim means that the W3 considers these issues at the moment, but expect these will not be a problem in the future, when web technologies come out with certain anticipated features Use interim solutions.

ECA 228 Internet/Intranet Design I Guideline 11 – use W3C technologies (according to specification) and follow accessibility guidelines – W3C technologies include built-in accessibility features – avoid non-W3C and non-standard features ( proprietary code ) Use W3C technologies and guidelines.

ECA 228 Internet/Intranet Design I Guideline 12 – group elements and provide contextual information about the relationship between elements – complex relationships between parts of a page may be difficult for people with disabilities to interpret – Checkpoints: Title each frame to facilitate identification and navigation Provide context and orientation information.

ECA 228 Internet/Intranet Design I Guideline 13 – provide clear and consistent navigation mechanisms to increase the likelihood that a person will find what they are looking for at a site orientation information navigation bars site map Provide clear navigation mechanisms.

ECA 228 Internet/Intranet Design I Guideline 14 – ensure that documents are clear and simple so they may be more easily understood – consistent page layout, recognizable graphics, and easy to understand language benefits all users – Checkpoints: Use the clearest and simplest language appropriate for a site’s content Ensure that documents are clear and simple.

ECA 228 Internet/Intranet Design I validation to check for accessibility, use: – automated tools – human review invite individuals with disabilities to review the document invite both experienced and novice users get feedback from users with a wide range of disabilities – hearing impaired – visually impaired – motor impairments

ECA 228 Internet/Intranet Design I validation methods use automated validation tools validate syntax of HTML validate style sheets view document in text-only browser view document in several browsers, old and new view document in screen reader, with magnification, on a small display, etc

ECA 228 Internet/Intranet Design I validation methods cont … use spelling and grammar checking – speech synthesizers may not be able to decipher misspelled words – grammar problems may make document incomprehensible review the document for clarity and simplicity – ask a human editor to review document – identify cultural barriers

ECA 228 Internet/Intranet Design I Bobby comprehensive web accessibility software tool – identifies barriers to accessibility enter a url to check one page at a time – generates a report listing violations of Priority 1, 2, and 3 issues – generates a list of user checks Bobby is available for purchase