Back to the original French page Read this page in Italian by Google Translation Read this page in Portuguese by Google Translation Read this page in English by Google Translation Read this page in German by Google Translation Read this page in Spanish by Google Translation Read this page in Arabic by Google Translation Read this page in Hebrew by Google Translation

Disabled people and the Web: list of issues and solutions Web development

Go to Beginning of content without using the bar Consultation and Sharing How to use the bar Consultation and Sharing Listen to the main content of this page
Print Print the main content of this page Send Email the main content of this page Share Share this page on TwitThis Share this page on Facebook Share this page on Wikio Share this page on Google Share this page on LinkedIn Share this page on Digg Share this page on del.icio.us Share this page on Netvibes

Warning: The original version of this document is Considering the User Perspective: A Summary of Design Issues . This French translation was done by Ideose as part of an agreement between WebAIM and Ideose .

Note: See page documents on web accessibility for a list of all translated documents. Other resources on web accessibility are also listed in the portal accessible digital .

Blindness

Key concepts related blindness
Issues Solutions
The images, photos, graphics can not be seen. Provide text alternatives for the attribute alt and if necessary, longer and more detailed descriptions (either on the same page or via a link to another page).
Users often listen to the web page. Allow users to switch the navigation menus, long lists, drawings ASCII or other content that may be difficult or unnecessary to listen.
Users often jump from link to link using the Tab key. Make explicit links out of context (links "Click here" are problematic).
Users generally do not use a mouse. Do not write scripts that require only the use of a mouse. Provide alternatives for the keyboard (use onFocus instead of onMouseover ).
It can be difficult for users to know where they are when they listen to the contents of table cells. Provide in-row and column (tag th ). Make it understandable tables listening - especially those who have merged cells - when they are read line by line from left to right.
Complex tables and graphs which usually displayed visually are not usable. Provide summaries and / or text alternatives, if possible on the same page or to link to another page as an alternative.
The frames can not be "seen" as a whole. they must be visited independently, which can lead to disorient the user. Do not use frames unless you are forced. If you use frames, provide titles to frames that inform the user of their natures (examples: "Menu Navigation", "Main content").
The colors can not be interpreted. Do not use only color to convey information.
Users expect that all relationships have a destination. Do not write scripts in links that do not have real destinations (example: href="javascript: function(cela)" ).
Screen readers read Web content in the literal order of appearance in the code. Check the CSS and layout tables are read correctly visually complex and in the code.
Users can not see the videos. Provide an audio description of the events of videos that can not be understood only through dialogues (it takes a narrator who describes the actions in the videos for which there is no dialogue).

Daltonism

Key concepts for color blindness
Issues Solutions
Similar contrasts of colors are often indistinguishable (reds and wersts example).
  • Make sure that sufficient contrast.
  • Do not convey information only by color (either edit the image, or provide an additional means of obtaining the same information. Often the most appropriate way is to provide an explanation in the text itself).

Low Vision

Key Concepts for Low Vision
Issues Solutions
Users often use software screen magnifiers. To reduce the area with horizontal scrolling, use relative units rather than absolute values ​​(eg, use of percentages for the widths of tables instead of pixels).
The texts in the images can not enlarge without the use of specific software and appear pixilated when they are enlarged.
  • Limit or remove the text in images.
  • Use an anti-aliasing to make text readable.
Users may want to set their own fonts and colors of wallpaper. Allow users to make their own settings using text wherever possible in text and not images.

Hearing impairment

Key concepts related hearing impairment
Issues Solutions
The sound is unusable.
  • Provide text transcripts for audio clips.
  • Put synchronized captions and text transcripts for video clips.

Motor disability

Key concepts for motor disability
Issues Solutions
Users may not be able to use the mouse.
  • Make sure all features are controlled from the keyboard (try tabbing from link to link).
  • Make sure the tab order is logical.
Users may not properly control the mouse or keyboard. Make sure your pages allow errors (eg, "Are you sure you want to delete this file"). Do not create small links or moving parts.
Users may be tired of using assistive technologies. Provide a method for passing long lists of links or content along.
Users can use software control by voice. Software control by voice can replicate mouse movements, but not as effectively as they can replicate the functionality of the keyboard. Therefore, make sure that all features are available from the keyboard.
Users may tire using assistive technologies. Provide a method for passing lists of links or content too long.

Cognitive impairment

The key concepts related cognitive impairment
Issues Solutions
Users can be hampered by complex layouts and navigation systems inconsistents through the website.
  • Simplify the layout as much as possible.
  • Keep the navigation system also consists as possible on the website.
Users may have difficulty concentrating or understanding the long paragraphs of text.
  • When appropriate, group textual information with paragraph headings.
  • Organize information into coherent parts.
One method of presenting web content may be insufficient.
  • When appropriate, add images or other formats to text and vice versa.

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University

Copyright 1999-2009 WebAIM

Top of Page