Oreste Signore- WAI/1 Amman, 12-13 December 2006 WAI Initiative on accessibility Ministerial NEtwoRk for Valorising Activities in digitisation.

Slides:



Advertisements
Similar presentations
Web Accessibility Talyah Aviran Head of UI team. 2 What is Accessibility? What is accessibility to the Web and why is it important? Impact of the Web.
Advertisements

Web Accessibility Web Services Office of Communications.
2/23/ Enterprise Web Accessibility Standards Version 2.0 WebMASSters Presentation 2/23/2005.
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.
The W3C Web Accessibility Initiative (WAI) Inclusive learning through technology Damien French.
Web Accessibility Issues. Why Consider Access Issues ? Discrimination Numbers of disabled students in HE likely to increase Sites designed for the disabled.
Web Page Design University of Wollongong IACT303 – INTI 2005 World Wide Networking.
Introduction to WCAG, ATAG and UAAG Jan Richards, Project Manager Inclusive Design Research Centre OCAD University
Dhananjay Bhole, Coordinator, Accessibility Research Group, Department of Education and Extension, University of Pune.
Kathy Gips Will Miller New England ADA & Accessible IT Center voice/tty Funded by the National Institute on Disability.
Web Accessibility John Rochford UMMS Shriver Center Director, INDEX Program Rich Caloggero WGBH National Center for Accessible Media MIT Adaptive Technology.
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.
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.
ECA 228 Internet/Intranet Design I Accessibility.
The Internet Writer’s Handbook 2/e Web Accessibility Writing for the Web.
Week 7.  Definition, policies, standards  Continuum of abilities.
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.
Web Accessiblity Carol Gordon SIU Medical Library.
Design and Construction of Accessible Web Sites Michael Burks Chairman Internet Society SIG For Internet Accessibility for People with Disabilities June.
1 Usability and accessibility of educational web sites Nigel Bevan University of York UK eTEN Tenuta support action.
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.
Status as of 9 August 2007  Rough concept draft only, much of it is incomplete  There are Notes for some slides, and none yet for others Note: This document.
Software Usability Course notes for CSI University of Ottawa Section 7: Accessibility - Usability for the Disabled Timothy C. Lethbridge
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.
WEB ACCESSIBILITY. WHAT IS IT? Web accessibility means that people with disabilities can use the Web. Web accessibility encompasses all disabilities that.
WEB ACCESSIBILITY Presentation December 2009 Plovdiv Bulgaria Sébastien LARDEUX, IT Montéclair Institute.
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.
Oreste Signore- Quality/1 Amman, December 2006 Standards for quality of cultural websites Ministerial NEtwoRk for Valorising Activities in digitisation.
Accessibility : Designing the Interface and Navigation The Non-Designer’s Web Book Chapter 7 Robin Williams and John Tollett Presented by Sherie Loika.
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.
Web Content Accessibility Leila Styer Washington State University CAHNRS/Computer Resource Unit rev. November 2006.
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 videos accessible – Mandatory guidelines
Information Architecture and Design I
Introduction to Web Accessibility
Web Content Accessibility Beata M. Ofianewska (DG COMM) 7 December 2006 December 2006 COMM C2.
Website Accessibility
Web Accessibility An Introduction.
Lakeshore Public Schools
International University of Japan
Information Architecture and Design I
Web Standards and Accessible Design.
Software Usability Course notes for CSI University of Ottawa
Demystifying Web Content Accessibility Guidelines
Accessible Design Top 10 List
Accessibility.
Presentation transcript:

Oreste Signore- WAI/1 Amman, December 2006 WAI Initiative on accessibility Ministerial NEtwoRk for Valorising Activities in digitisation

Oreste Signore- WAI/2 Amman, December 2006 Quality of a web site  The criteria for a quality cultural web communication are based on two pillars:  Accessibility (WCAG/W3C)  Usability (ISO ) basic principles  The key concept of quality web site means to pay attention to the users and their requirements.

Oreste Signore- WAI/3 Amman, December 2006 Quality: definitions (1)  Usability:  «The capability of the software product to enable specified users to achieve specified goals with effectiveness, productivity, safety and satisfaction in specified contexts of use.» (ISO/IEC :1992)

Oreste Signore- WAI/4 Amman, December 2006 Quality: definitions (2)  Accessibility:  «A Web site is considered to be accessible when the informational content, navigational modes and all the interactive features present are accessible to all users, regardless of disabilities and independently of technology used to access the site and of the context in which they are working whilst accessing the site» (ISO TS 16071:2002)

Oreste Signore- WAI/5 Amman, December 2006 Web for Everyone  Accessibility:  «The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect»  Web for Everyone available to all people, whatever their hardware, software, network infrastructure, native language, culture, geographical location, or physical or mental ability

Oreste Signore- WAI/6 Amman, December 2006 Dimensions of accessibility  Connecting time  Availability  Compatibility of browser  Accessibility of disabilities

Oreste Signore- WAI/7 Amman, December 2006 Elements of connection

Oreste Signore- WAI/8 Amman, December 2006 Context of users  Many users may be operating in contexts very different from your own :  They may not be able to see, hear, move  They may have difficulty reading or comprehending text.  They may not have or be able to use a keyboard or mouse.  They may have a text-only screen, a small screen, or a slow Internet connection.  They may not speak or understand fluently the language in which the document is written.

Oreste Signore- WAI/9 Amman, December 2006 Context of users (cont.)  They may be in a situation where their eyes, ears, or hands are busy or interfered with (e.g., driving to work, working in a loud environment, etc.).  They may have an early version of a browser, a different browser entirely, a voice browser, or a different operating system.  Content developers must consider these different situations during page design

Oreste Signore- WAI/10 Amman, December 2006 Definition of disability  The WHO World Health Organisation in 2001:  refers to “human functions” in general and not simply to disability.  Moves away from the consequences of a “disfunction” to components of “health”, grouping them together under the heading of “health domain”  Participation, not exclusion

Oreste Signore- WAI/11 Amman, December 2006 Different disabilities

Oreste Signore- WAI/12 Amman, December 2006 How do disabled people use the Web?  Throught “enabling” technology. This can be hardware or software which:  effect “equivalent” conversion of the information from one sense organ to another. Some examples are: from the computer monitor (sight) to touch (Braille bar for visually-impaired users), from the computer monitor (sight) to sound (vocal synthesis for visually-impaired users), from sound (audio documents) to sight (text documents) (vocal recognition for motor-disabled and deaf users);

Oreste Signore- WAI/13 Amman, December 2006 How do disabled people use the Web? (2)  permit different ways of using certain tools, for example: special mouse (for motor-disabled); special keyboard (for motor-disabled); compensate for disability of a sensory faculty, for example: enlarging the text on the computer monitor (for the visually impaired)

Oreste Signore- WAI/14 Amman, December 2006 How do disabled people use the Web? (3)  Specific tools are available to compensate for other types of disability :  for users with difficulty in distinguishing colours  for users affected by photosensitive epilepsy  for users with learning difficulties or language difficulties

Oreste Signore- WAI/15 Amman, December 2006 Advantages

Oreste Signore- WAI/16 Amman, December 2006 Web Accessibility Initiative  The World Wide Web Consortium (W3C) has promoted the Web Accessibility Initiative (WAI).  The objective is to produce strategies, guidelines, resources to make the Web accessible to people with disabilities

Oreste Signore- WAI/17 Amman, December 2006 Web Accessibility Initiative  WAI deals with Web accessibility in the lay sense; that is, not only as far as regards contents, but also in terms of the tools used to realise the Web pages, the browser and, more generically, technologies for Web access.  Accessibility is a process involving many actors (people, developers, user agents). Hence:  WCAG  ATAG  UAAG

Oreste Signore- WAI/18 Amman, December 2006 Web Content Accessibility Guidelines  were developed by the Web Content Accessibility Guidelines Working Group (WCAG WG);Web Content Accessibility Guidelines Working Group  became a W3C Recommendation 5 May 1999;  explain how to make accessible Web sites;  contain general guidelines;  have three priority levels of normative checkpoints;  have extensive supporting resources

Oreste Signore- WAI/19 Amman, December 2006 Web Content Accessibility Guidelines (2)  It explains how to make Web content accessible to people with disabilities. Web "content" generally refers to the information in a Web page or Web application, including text, images, forms, sounds, and such.  WCAG 1.0 has 14 guidelines that are general principles of accessible design. Each guideline has one or more checkpoints that explain how the guideline applies in a specific area (65 in total). WCAG 1.0

Oreste Signore- WAI/20 Amman, December 2006 Resources for WCAG  There are extensive implementation support resources for WCAG 1.0, including:  WCAG 1.0 Checklist WCAG 1.0 Checklist  WCAG 1.0 Techniques WCAG 1.0 Techniques  WCAG 1.0 Frequently Asked Questions (FAQ) WCAG 1.0 Conformance Logos WCAG 1.0 Frequently Asked Questions (FAQ) WCAG 1.0 Conformance Logos  WCAG 1.0 Translations WCAG 1.0 Fact Sheet WCAG 1.0 Translations WCAG 1.0 Fact Sheet  WCAG 1.0 Curriculum WCAG 1.0 Curriculum  QuickTips for Accessible Web Sites QuickTips for Accessible Web Sites  Evaluating Web Sites for Accessibility Evaluating Web Sites for Accessibility  Implementation Planning for Web Accessibility Implementation Planning for Web Accessibility  Planning Web Accessibility Training Planning Web Accessibility Training

Oreste Signore- WAI/21 Amman, December 2006 WCAG 1.0: conformance level  Three priorities:  Priority 1 (A-compliant): Criteria a web developer must satisfy Basic requirement for some groups to be able to access web documents  Priority 2 (AA-compliant): Criteria a web developer should satisfy Removes significant barriers to accessing web documents  Priority 3 (AAA-compliant): Criteria a web developer may satisfy Improves access to web documents

Oreste Signore- WAI/22 Amman, December 2006 WCAG 1.0: Level of conformance  Level A:  all priority 1 checkpoints are satisfied  Level AA:  all priority 1 and 2 checkpoints are satisfied  Level AAA:  all priority 1, 2 and 3 checkpoints are satisfied

Oreste Signore- WAI/23 Amman, December 2006 Synthesis of WCAG 1.0 guidelines 1.Provide equivalent alternatives to auditory and visual content. Non-text element includes: images, graphical representations of text (including symbols), image map region 2.Don't rely on color alone. Ensure that all information conveyed with color is also available without color. 3.Use markup and style sheets and do so properly. Use style sheets to control layout and presentation. Use relative rather than absolute units in markup language attribute values and style sheet property values. 4.Clarify natural language usage. Clearly identify changes in the natural language of a document's text and any text equivalents

Oreste Signore- WAI/24 Amman, December 2006 Synthesis of WCAG 1.0 guidelines (cont.) 5.Create tables that transform gracefully. Ensure that tables have necessary markup to betransformed by accessible browsers and other user agents. 6.Ensure that pages featuring new technologies transform gracefully. Ensure that pagesare accessible even when newer technologies are not supported or are turned off. 7.Ensure user control of time-sensitive content changes. Ensure that moving, blinking, scrolling, or auto-updating objects or pages may be paused or stopped.

Oreste Signore- WAI/25 Amman, December 2006 Synthesis of WCAG 1.0 guidelines (cont.) 8.Ensure direct accessibility of embedded user interfaces Ensure that the user interface follows principles of accessible design: device-independent access to functionality, keyboard operability, self-voicing, etc. 9.Design for device-independence Use features that enable activation of page elements via a variety of input devices. 10.Use interim solutions so that assistive technologies and older browsers will operate correctly. 11.Use W3C technologies and guidelines according to specification. Where it is not possible to use a W3C technology, or doing so results in material that does not transform gracefully, provide an alternative version of the content that is accessible.

Oreste Signore- WAI/26 Amman, December 2006 Synthesis of WCAG 1.0 guidelines (cont.) 12.Provide context and orientation information. Provide context and orientation information to help users understand complex pages or elements. 13.Provide clear navigation mechanisms. Provide clear and consistent navigation mechanisms -- orientation information, navigation bars, a site map, etc. -- to increase the likelihood that a person will find what they are looking for at a site. 14.Ensure that documents are clear and simple so they may be more easily understood.

Oreste Signore- WAI/27 Amman, December 2006 Example 1: images  Provide a text equivalent for every non-text element  (e.g. via «alt», «longdesc», or in element content)  This includes: Images graphical representations of text (including symbols) image map regions animations (e.g., animated GIFs) applets and programmatic objects ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons sounds (played with or without user interaction) stand-alone audio files, audio tracks of video, and video.

Oreste Signore- WAI/28 Amman, December 2006 Example 1: images

Oreste Signore- WAI/29 Amman, December 2006 Example 1: images

Oreste Signore- WAI/30 Amman, December 2006 Example 2: color  Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text]

Oreste Signore- WAI/31 Amman, December 2006 Example 3: multimedia  Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. [Priority 1]

Oreste Signore- WAI/32 Amman, December 2006 Exemple 4: code validation  Create documents that validate to published formal grammars. Use for example W3C validator. Important show DOCTYPE. [Priority 2]

Oreste Signore- WAI/33 Amman, December 2006 Example 5: relative units  Use relative units (% or em) rather than absolute units in:  markup language attribute values  style sheet property values [Priority 2]

Oreste Signore- WAI/34 Amman, December 2006 Example 6: metadata  Provide metadata to add semantic information to pages and sites. For example, use DUBLIN CORE to indicate the  Document author ( )  Content type ( )  etc. [Priority 2]

Oreste Signore- WAI/35 Amman, December 2006 WCAG 2.0: principle 1  Content must be perceivable.  Provide text alternatives for all non-text content  Provide synchronized alternatives for multimedia  Ensure that information and structure can be separated from presentation  Make it easy to distinguish foreground information from its background

Oreste Signore- WAI/36 Amman, December 2006 WCAG 2.0: principle 2  Interface components in the content must be operable.  Make all functionality operable via a keyboard interface  Allow users to control time limits on their reading or interaction  Allow users to avoid content that could cause seizures due to photosensitivity  Provide mechanisms to help users find content, orient themselves within it, and navigate through it  Help users avoid mistakes and make it easy to correct mistakes that do occur

Oreste Signore- WAI/37 Amman, December 2006 WCAG 2.0: principle 3  Content and controls must be understandable.  Make text content readable and understandable.  Make the placement and functionality of content predictable.

Oreste Signore- WAI/38 Amman, December 2006 WCAG 2.0: principle 4  Content should be robust enough to work with current and future user agents (including assistive technologies)  Support compatibility with current and future user agents (including assistive technologies)  Ensure that content is accessible or provide an accessible alternative

Oreste Signore- WAI/39 Amman, December 2006 WCAG 2.0: some concepts  Baseline  The set of technologies that an author assumes are supported and turned on in accessible user agents  Conformance  A and AA for minimum or enhanced accessibility level  AAA achieves additional accessibility enhancements  AAA requires that at least 50% of level 3 success criteria are satisfied

Oreste Signore- WAI/40 Amman, December 2006 WCAG 1.0 vs WCAG 2.0  WCAG 2.0 applicable to a variety of situations and technologies, including those that not yet exist  Checkpoints in WCAG 1.0 seemed to be of different importance (priority level)  All WCAG 2.0 success criteria are essential for some people

Oreste Signore- WAI/41 Amman, December 2006 Thank you for your attention!  Questions?  References  utilityLinks.html utilityLinks.html   /MEDCULT/home.html /MEDCULT/home.html  Oreste Signore 