Library tutorials & articles
Accessibility for Web Developers
Guideline 14
Guideline 14: Ensure that documents are clear and simple
The use of clear and simple language promotes effective communication. Trying to come across as articulate can be as difficult to read as poorly written grammar, especially if the language used isn't the visitor's primary language. Using a consistent page layout, and recognisable graphics ensures that information can be located quickly.
This guideline has 3 checkpoints, ranging in importance from Level "A" (must be addressed for the site to be accessible), to Level "AAA" (beneficial to ensure the accessibility of your site).
14.1
Use the clearest and simplest language appropriate for a site's content
This checkpoint is a priority 1 checkpoint. It must be satisfied for your site to be considered accessible. You should use the clearest and simplest language appropriate for your site's content to ensure it's accessible to people with reading and/or cognitive disabilities. Headings and link descriptions should be informative, clear, and accurate. Link phrases should be terse, and make sense when read out of context.
The topic of a section should be clearly stated at the beginning, as this helps people skim read. If the main point is in the middle of a paragraph, or the final paragraph of a large section, visitors will need to read a lot of content before finding what they are after.
Each paragraph should contain one idea, clearly stated at the start of the paragraph. Avoid using complex sentence structures, slang, and jargon. Try and choose words that are commonly used. Avoid redundant words, and ensure that any instructions are clear and easy to follow.
Bad Example
One must endeavour to ensure simplicity is stringently
upheld in order to facilitate comprehension.
Better Example
Keep it simple!
The Gunning-Fog index is one of many tests that can help determine how readable your content is. The following shows how to determine your Gunning-Fog index.
- Pick a sample containing at least 100 words.
- Calculate the average number of words you use per sentence.
- Calculate the percentage of difficult words in the sample (words with three or more syllables, excluding proper names, and verbs).
- Add the totals together, and multiply the sum by 0.4.
The result is your Gunning-Fog index, which is a rough measure of how many years of schooling it would take someone to understand the content. The lower the number, the more understandable the content will be to your visitors. If your index is higher than 12, the chances are you will start to lose some of your audience in the fog.
You can test your content online through the readability test at Juicy Studio.
14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page
This is a priority 3 checkpoint, which will be beneficial for the accessibility of your site. Images, sounds, and text can compliment each other, and ensure you have as wide an audience as possible. A picture paints a thousand words, and sound saves having to read them.
Images, animations, and movies will be well received by visitors who prefer visual content. For example, sighted deaf visitors may benefit from a sign-language movie. Music, spoken words, and sound effects will be well received by visitors who prefer audio content. Keep in mind that assistive technologies are able to produce synthesised speech and Braille from text or text equivalents. If you do use graphic and auditory presentations, they should be in keeping with the site, and not obtrusive.
14.3 Create a style of presentation that is consistent across pages
This is a priority 3 checkpoint, which will be beneficial for the accessibility of your site. Unless you have a consistent style across your site, visitors can become disorientated going from page to page. The main navigation should be located at the same position on each page. If you use sub-navigation systems, they should also be located at the same place on each page. Colours and text styles can provide important visual clues. You should use colours and style consistently, particularly with headings. CSS is excellent for ensuring you have a consistent style across the whole site.
Further Reading
Related articles
Related discussion
-
Header and Footer in Web page print
by fhajaj (4 replies)
-
help me to get simple requirement
by Slicksim (1 replies)
-
Gridview -> Template Field -> Button
by antti.simonen (1 replies)
-
Classic ASP : Page expires
by chezhian_in05 (0 replies)
-
ASP VS PHP
by paulfp (9 replies)
Related podcasts
-
ASP.NET Caching and Performance
Steve Smith, owner of ASP Alliance and Lake Quincy Media joins us today to teach us about some hidden gems in ASP.NET caching and performance. Steve’s expertise in this area comes from first-hand experience as Lake Quincy’s ad system serves over 60 requests per second and handles over 150 million...
Events coming up
-
Dec
8
Web Design World
Boston, United States
Join your colleagues and top experts in the Web field as Web Design World returns to Boston December 8-10, 2008 for three dynamic days of information, interaction, insight and inspiration.
My question is related to implementing Accessibility when using a datagrid, a datalist, XML, and/or a database. All the info has been advocated in many circles and I would like to comply using ASP.NET and XML.NET.
In many cases we are writing our ASP.net code to give access to data that is already in place and has been used for a considerable amount of time. The biggest problem is that many databases and XML files are already set in place and we cannot change the data ( or the powers that be are unwilling to do so). Likewise we are not in a position to add columns to the information in support of addressing Accessibility issues (for ex. a column for dynamic insertion of an ALT tag to explain images stored inside of the database, addition of supportive information (summary, caption, and scope) when tabular data is dynamically built from an XML data file as in
<table width="90%" border="0" cellpadding="4" summary="this summary">
<caption>
this caption
</caption>
<tr>
<th scope="col"> </th>
<th scope="col"> </th>
</tr>
<tr>
<td> </td>
<td> </td>
</tr>
</table>
AND / OR a dynamically built link that usually would be <a href="http://www.here.com" target="_blank">go here</a>
but really should be constructed as the code below for Accessibility reasons
<a href="http://www.here.com" tabindex="3" title="A location to enjoy" accesskey="1" target="_blank">go here</a>
So what can we do to increase Accessibility in these instances beyond adding to the XML or the database?
Another issues to address would be in dynamic paging of a datagrid where the use of numeric or alpha characters are used to paginate through the data.
This thread is for discussions of Accessibility for Web Developers.