guidelines for accessibility of Web content - Web Accessibility Initiative ( WAI)
The WAI is an internal organ to the W3C which aims to provide a set of guidelines that a site is developed in an accessible and visible to a growing number of people. The WAI guidelines are an excellent reference for web designers who want to ensure a good level of accessibility. Following the guidelines of the WAI is then possible to determine what tools and methods can resolve the issues relating to:
- people with physical mobility, therefore unable to properly use the keyboard;
- people with vision problems that can be difficult to select or see certain colors;
- people who do not have hardware / software for new generation.
The core accessibility that emerges from these guidelines to ensure an elegant transformation that makes the content understandable and navigable. Accessibility therefore means " transform gracefully" means a written page in a certain way with certain content changes according to the needs of the user being able to make content understandable and navigable. An accessible site, if properly implemented, can be very similar to a non-accessible. Ensure a high degree of accessibility means in fact make the same information is accessible in different ways. To encourage people with limitations of any kind (physical or technological) should be taken of devices that designers (web designers and programmers) should apply, trying to make compatible the html with the programs (validators) and specific support and assisted softwares (screen readers, Braille keyboard, etc...)
The WAI guidelines are divided into four sections:
- WCAG: Web Content Accessibility Guidelines 1.0 [the Italian version is the responsibility of the Italian librarians ( http://www.aib.it/aib / cwai / WAI-trad.htm )].
explain in detail how to make a site accessible to disabled people, both physically and cognitively.
- ATAG : Authoring Tool Accessibility Guidelines 1.0Sono aimed at software developers and applications for the creation of sites with pages actually available.
- UAAG : User Agent Accessibility Guidelines 1.0Rivolte also software designers, they explain how to make their products compatible multimedia applications and not to create problems with assistive technologies for disabled persons.
- XML: Extensible Markup Language GuidelinesPer developers of XML applications, explain how to ensure compatibility between this language and parameters of accessibility.
Another important section of the documents is that of the WAI checklist, where the above guidelines are divided according to their priorities:
Priority 1: Web content developer must satisfy this checkpoint, it is impossible access. [Level A]
Priority 2: Web content developer should satisfy this checkpoint, otherwise the access difficulties for some users. [AA level]
Priority 3: Web content developer may take into account this point of control to improve access. [Level AAA]
WCAG are divided into fourteen guidelines, each of which certain topics are treated according to category and control points. In each control point describes the problem should be addressed and gives tips on how to resolve it.
Here are some key points of the WAI guidelines.
level A guide linne are dealing with:
compatibility with various browsers
The website, to be seen by everyone equally, must be compatible with most browsers (eg Netscape, Mozilla , Explorer, Opera), but this compatibility is especially extended to the special browsers, those used by disabled people, such as screen readers.
IMAGES
is important to find technical solutions that make the images accessible site with messages auditory or special devices to enable a "graceful transformation of pages.
EFFECTS Special effects (flashing messages, violent colors, moving pictures) should be restricted and used so as not to cause psychological distress to those who may have seizures or nervous.
TEXTS
I colored text should contain an option that makes them accessible even to those who can not see certain colors (eg color-blind individuals who can not see the color red) The characters should have a proper size, or provide the user the possibility to enlarge them.
At level AA:
VIDEO
You should make sure that the monitor has a color combination, including the background and the foreground, so as to generate sufficient contrast so that the website can be seen by those who have trouble seeing certain colors, or having the screen black and white.
INFORMATION The information should be structured so as to make them easily accessible to all users that belong to the target site.
Level AAA:
Content Accessibility
is important to carefully define the structure of information, providing a graphic or audio support so that the page can be perceived and understood by even the most disabled users.
THE IDENTIFICATION OF THE MAIN LANGUAGE
The identification of language main is important because the Web is aimed at people who speak different languages. We always ask you to identify the "natural language and a main document and make it available in the languages \u200b\u200bmost used by the target audience.
is important to clarify that this does not necessarily mean you will not make a website aesthetically pleasing or special restrictions. It will be for web designers combine their creativity with functionality. Indeed Building the accessibility of a site means to combine technical expertise skills in ergonomics, design and interaction design.
The Chamber of Deputies approved a bill requiring to public and providers of public services to meet accessibility criteria in the implementation of its Web sites Law 9 January 2004, n. 4: Measures to facilitate access for disabled people to information: http://www.camera.it/parlam/leggi/04004l.htm
0 comments:
Post a Comment