![]() |
![]() |
|
|
|
On-Line Teaching – Improving Accessibility |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
| Challenges | Solutions |
| Users may not be able to use the mouse. | Make sure that all functions are available from the keyboard (try tabbing from link to link). Make sure that the tab order is logical. |
| Users may become fatigued when using ‘puff-and-sip’ or similar adaptive technologies. | Provide a method for skipping over long lists of redundant links or other lengthy content. |
| Users may be using voice activated software. | Voice activated software generally cannot replicate mouse movement as effectively as it can replicate keyboard usage, so make sure that all functions are available from the keyboard. |
Vision Impairment
Blindness
Individuals who are blind often use computers equipped with screen reader software
and speech synthesizers. With a synthesized voice, this system reads whatever
text appears on the computer screen. They may use a browser that only reads
text presented on the World Wide Web or they may use a multimedia browser
with the graphics-loading feature turned off. This type of system cannot
interpret graphics. For example, a speech synthesiser may simply say “image
map” at the place where an image map would be displayed to someone
using the full features of a multimedia Web browser.
| Challenges | Solutions |
| Images, photos, graphics are unusable. | Provide text descriptions in the ‘alt’ attribute and, if necessary, longer explanations (either on the same page or with a link to another page). |
| Users often listen to the Web pages. | Create links that allow users to skip over navigational menus, long lists of items and other things that might be difficult or tedious to listen to. |
| Users often jump from link to link using the TAB key. | Make sure that links make sense out of context (“click here” is problematic). |
| Users generally do not use a mouse | Don’t write scripts that require mouse usage. Supply keyboard alternatives. |
| It may be difficult for users to tell where they are when listening to data table cell contents. | Provide column and row headers for data tables. Avoid spanned rows or columns in data tables, if at all possible. |
Complex data tables and graphs that are usually interpreted visually are unusable. |
Provide summaries and/or text descriptions, preferably on the same page, or link to another page as an alternative. |
| Frames cannot be “seen” all at once. They must be accessed separately, leading to disorientation. | Don’t use frames unless you have to. If you use them, provide frame titles that communicate their purpose (e.g. “navigational frame”, “main content”). |
| Colours are unusable. | Do not rely on colour alone to convey meaning. |
| Users expect links to take them somewhere. | Don’t write scripts in links that don’t have true destinations associated with them. |
| Screen readers read Web content in the literal order that it appears in the code. | Ensure that complex CSS or table layouts read correctly visually AND in the code. |
| Individuals cannot see the events in videos. | Provide audio descriptions of events in videos that cannot be interpreted by audio alone (e.g. have a narrator describe actions in videos for which there is no dialogue). |
Low vision
Students who are not blind but have limited vision may use special
software to enlarge screen images. They view only a small portion of
a standard screen page at a time. Consequently, web pages that are
cluttered and page layouts that are not consistent from page to page
can make navigating web sites and understanding content difficult.
People who are colour blind encounter barriers erected by coursework
that requires that they be able to distinguish one colour from another
to navigate the site or understand the web content.
| Challenges | Solutions |
| Users often use screen enlargers. | To reduce the amount of horizontal scrolling, use relative rather than absolute units (e.g. use percentages for page widths, instead of pixels). |
| Text in graphics does not enlarge without special software, and looks pixelated when enlarged. | Limit or eliminate text within graphics. Use anti-aliasing to make text crisp and readable. |
Colour blindness
| Challenges | Solutions |
| Colours of similar contrast are often indistinguishable. | Make sure that there is sufficient contrast. Don’t use colour alone to convey meaning (supplement colour with text, for example). |
Cognitive/Learning Disabilities
Some specific learning/cognitive disabilities impact on the ability
to read, write and/or process information.
Some students with these
types of disabilities use screen enlargement systems or text to speech
systems similar to those used by people with vision impairment to
help them read text on a computer screen.
Students with some learning/cognitive
disabilities have difficulty understanding web sites when the information
is cluttered and the screen layout changes from one page to the next.
| Challenges | Solutions |
| Users may become confused at complex layouts or inconsistent navigational schemes. | Simplify the layout as much as possible. Keep the navigational schemes as consistent as possible. |
| Users may have difficulty focusing on or comprehending lengthy sections of text. | Where appropriate, group textual information under logical headings. Organise information in manageable “chunks”. |
| One method of input may not be sufficient. | Where appropriate, supplement text with illustrations or other media, and vice versa. |
Hearing Impairment/Deafness
Most internet resources do not require the ability to hear and are,
therefore, accessible to people who are deaf or hearing impaired. However,
when web sites include audio output without providing text captioning
or transcription, individuals with hearing impairments cannot access
the content.
The audio content of videotapes that are not captioned
is also inaccessible to individuals who are deaf.
| Challenges | Solutions |
| Audio is unusable | Provide transcripts for audio clips. Provide synchronous captioning for video clips. |
Sources:
Tables copyright © 2005 Web AIM http://webaim.org/techniques/userperspective and reproduced with kind permission.
(Iinformation on Access Challenges and Proposed Solutions is adapted, with permission, from information located at: http://www.aace.org “Distance Learning Universal Design, Universal Access” article by Sheryl Burgstahler and Paul Bohman’s article “Considering the user perspective: a summary of design issues” 2002 located in http://www.webaim.org/techniques/userperspective/?templatetype=3)
(source: http://dartmouth.edu/~shorton/ )
Bobby: Accessibility validation
http://www.cast.org/bobby
Lynx Viewer; Lynx simulator
http://www.delorie.com/web/lynxview.html
UsableNet: Web site testing service
http://www.usablenet.com
W3C HTML Validation Service
http://validator.w3.org/
W3C CSS Validation Service
http://jigsaw.w3.org/css-validator/
Chemistry
http://www.xml-cml.org/information/position.html
Languages
http://www.w3.org/International
Mathematics
http://www.w3org/Math
Accessible Design guidelines
http://www.dartmouth.edu/~webteach/resources/download.html
Accessible PDF documents
http://www.adobe.com/products/acrobat/solutionsacc.html
How to Create Accessible Adobe PDF Files Booklet
http://access.adobe.com/booklet.html
IBM Accessibility Center
http://www-3.ibm.com/able/
Microsoft Accessibility
http://www.microsoft.com/enable
Rich Media Resource Center
http://ncam.wgbh.org/richmedia/
Usable Net: Accessibility & Usability
http://www.usablenet.com/accessibility_usability/index.htm
WebABLE
http://www.webable.com/
Web Accessibility Initiative (WAI)
http://www.w3.org/WAI/Resources/
Web content accessibility guidelines 1.0
http://www.w3c.org/tr/wai-webcontent/wai-pageauth.html
Home Page Reader: PC Voicing Browser
http://www-3.ibm.com/able/hprtrial3.html
Magpie: Captioning and describing software
http://ncam.wgbh.org/webaccess/magpie/index.html
www.webaim.org
http://www.umuc.edu/ade/wia/intro.html
http://www.doit.wisc.edu/accessiblity/myths.asp
Blackboard Accessibility
http://asuonline.asu.edu/support/accessibilityFAQ.pdf
Sources:
Tables copyright 2005 Web AIM http://webaim.org/techniques/userperspective