Alternative Home ButtonCIT 235 logo
School
  • CIT 230
  • CIT 235
Bio
  • Mike and Brit's Blog
  • Our Family
Current Projects
  • Hoggan's Rock Solid Gear
    Test Site
  • PHP Motors
Portfolio
  • BurgWear
  • Nature's Nook
  • The Auto Spa Plus

You Are Here: Home > School's Main Page > CIT 235 Main Page > WDS Main Page> WDS 2

WDS 2

Readable: Make text content readable and understandable.

Guideline 3.1

The main idea behind a web page being readable is to make your content make sense to those who read it and help those users with disabilities read and understand your content with assistive technology.

"People with disabilities experience text in many different ways. For some the experience is visual; for some it is auditory; for some it is tactile; for still others it is both visual and auditory. Some users experience great difficulty in recognizing written words yet understand extremely complex and sophisticated documents when the text is read aloud, or when key processes and ideas are illustrated visually."

There are many different techniques that can be implememented that are not competely necessary to the 2.0 standards but are nonetheless great to make your content more accessible to more people. Here are just an handful of techniques to implement.

  • Using the clearest and simplest language appropriate for the content
  • Avoiding chunks of italic text
  • Avoiding overuse of different styles on individual pages and in sites
  • Making links visually distinct
  • Making any reference to a location in a Web page into a link to that location

The guidelines for this success criterion are listed bellow:

Language of Page

This criterion helps those who rely on screen readers that turn text into speech, people who rely on captions, and people who have cognitive or language disabilities who use software, just name a few.

  • Technique: Identify the default language of a document by providing the lang and/or xml:lang attribute on the html element.

Language of Parts

This criterion helps to render multiple languages in an appropriate manner so that assistive technologies will be able to help users with the transition.

  • Technique: Identify the changes in language at any time in the document by using the lang or the xml:lang attribute.

Unusual Words

This criterion helps to have a method to identify definitions and meanings to words or phrases that may used in unsual ways, like with jargon or slang.

  • Technique: Create a link with the text to a definition or explanation in the same page or on the site.

Abbreviations

This criterion helps to have a method to identify acronyms or abbreviations when used in text.

  • Technique: Create a link with the text to a definition or explanation in the same page or on the site that explains the abbreviation or acronym.

Reading Level

This criterion helps to provide ways to aid the understanding of complex or difficult texts.

  • Technique: Make your content understandable where a youth could understand it or provide a spoken version of the text.

Pronunciation

This criterion has a great example of desert as in "abandoned" and desert as in "arid", if the proper pronunciation cannot be determined from the context of the sentence, then a mechanism determining the proper pronunciation would be required.

  • Technique: Provide pronunciation right after the word or link to proper pronunciations.

There is alot to implement when it comes to this criterion but linking to appropriate diffiniations, spelling out abbreviations, and providing pronunciation of mistaken words will be worked on from her on out. I have yet to have anything that needs immidate attention. I am planning on making my site or parts of my site with spanish text so language of parts and page are going to impelement once I build in this feature.

Back

Last Updated on April 4, 2009 3:56 PM

© 2008, Mike Hoggan, All rights reserved
Contact Me | Terms | Privacy | Colophon | CIT 230 | CIT 235 | Mike and Brit's Blog
Our Family | Hoggan's Rugged Gear Test Site | BurgWear | Nature's Nook | The Auto Spa Plus

Valid CSS! Valid XHTML 1.0 Strict