WAI Initiative on accessibility
description
Transcript of WAI Initiative on accessibility
Oreste Signore- WAI/1 Amman, 12-13 December 2006
WAI Initiative on accessibility
Ministerial NEtwoRk for Valorising Activities in digitisation
Oreste Signore- WAI/2 Amman, 12-13 December 2006
Quality of a web siteThe criteria for a quality cultural web
communication are based on two pillars:
Accessibility (WCAG/W3C)Usability (ISO 9241-11) basic principles
The key concept of quality web site means to pay attention to the users and their requirements.
Oreste Signore- WAI/3 Amman, 12-13 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 9126-1:1992)
Oreste Signore- WAI/4 Amman, 12-13 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, 12-13 December 2006
Web for EveryoneAccessibility:
«The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect»
Web for Everyoneavailable to all people, whatever their hardware, software, network infrastructure, native language, culture, geographical location, or physical or mental ability
Oreste Signore- WAI/6 Amman, 12-13 December 2006
Dimensions of accessibilityConnecting timeAvailabilityCompatibility of browserAccessibility of disabilities
Oreste Signore- WAI/7 Amman, 12-13 December 2006
Elements of connection
Oreste Signore- WAI/8 Amman, 12-13 December 2006
Context of usersMany users may be operating in contexts
very different from your own :They may not be able to see, hear, moveThey 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, 12-13 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, 12-13 December 2006
Definition of disabilityThe 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, 12-13 December 2006
Different disabilities
Oreste Signore- WAI/12 Amman, 12-13 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, 12-13 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, 12-13 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 coloursfor users affected by photosensitive epilepsyfor users with learning difficulties or language
difficulties
Oreste Signore- WAI/15 Amman, 12-13 December 2006
Advantages
Oreste Signore- WAI/16 Amman, 12-13 December 2006
Web Accessibility InitiativeThe 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 http://www.w3.org/WAI/
Oreste Signore- WAI/17 Amman, 12-13 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, 12-13 December 2006
Web Content Accessibility Guidelines
were developed by the Web Content Accessibility Guidelines Working Group (WCAG WG);
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, 12-13 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).
Oreste Signore- WAI/20 Amman, 12-13 December 2006
Resources for WCAG There are extensive implementation support
resources for WCAG 1.0, including: WCAG 1.0 Checklist WCAG 1.0 Techniques WCAG 1.0 Frequently Asked Questions (FAQ)
WCAG 1.0 Conformance Logos WCAG 1.0 Translations
WCAG 1.0 Fact Sheet WCAG 1.0 Curriculum QuickTips for Accessible Web Sites Evaluating Web Sites for Accessibility Implementation Planning for Web Accessibility Planning Web Accessibility Training
Oreste Signore- WAI/21 Amman, 12-13 December 2006
WCAG 1.0: conformance levelThree priorities:
Priority 1 (A-compliant): Criteria a web developer must satisfyBasic 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 satisfyImproves access to web documents
Oreste Signore- WAI/22 Amman, 12-13 December 2006
WCAG 1.0: Level of conformanceLevel 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, 12-13 December 2006
Synthesis of WCAG 1.0 guidelines1. 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, 12-13 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, 12-13 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, 12-13 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, 12-13 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:
Imagesgraphical representations of text (including symbols)image map regionsanimations (e.g., animated GIFs)applets and programmatic objectsascii art, frames, scripts, images used as list bullets, spacers, graphical buttonssounds (played with or without user interaction)stand-alone audio files, audio tracks of video, and video.
Oreste Signore- WAI/28 Amman, 12-13 December 2006
Example 1: images
Oreste Signore- WAI/29 Amman, 12-13 December 2006
Example 1: images
Oreste Signore- WAI/30 Amman, 12-13 December 2006
Example 2: colorEnsure 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, 12-13 December 2006
Example 3: multimediaUntil 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, 12-13 December 2006
Exemple 4: code validationCreate documents that validate to published
formal grammars. Use for example W3C validator. Important show DOCTYPE.
[Priority 2]
Oreste Signore- WAI/33 Amman, 12-13 December 2006
Example 5: relative unitsUse relative units (% or em) rather than
absolute units in:markup language attribute valuesstyle sheet property values
[Priority 2]
Oreste Signore- WAI/34 Amman, 12-13 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
(<meta name="DC.Creator" content="Oreste Signore" /> ) Content type
(<meta name="DC.Subject" content= “islamic art" /> ) etc.
[Priority 2]
Oreste Signore- WAI/35 Amman, 12-13 December 2006
WCAG 2.0: principle 1Content 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, 12-13 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, 12-13 December 2006
WCAG 2.0: principle 3Content and controls must be
understandable. Make text content readable and understandable. Make the placement and functionality of content
predictable.
Oreste Signore- WAI/38 Amman, 12-13 December 2006
WCAG 2.0: principle 4Content 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, 12-13 December 2006
WCAG 2.0: some conceptsBaseline
The set of technologies that an author assumes are supported and turned on in accessible user agents
ConformanceA and AA for minimum or enhanced accessibility
level AAA achieves additional accessibility
enhancementsAAA requires that at least 50% of level 3 success
criteria are satisfied
Oreste Signore- WAI/40 Amman, 12-13 December 2006
WCAG 1.0 vs WCAG 2.0WCAG 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, 12-13 December 2006
Thank you for your attention!
Questions? References
utilityLinks.html http://www.minervaeurope.or
g http://www.minervaeurope.or
g/MEDCULT/home.html
Oreste Signore [email protected]